PROJECT 123 Business Case March 30, 2001. Page 1 Authors: Saltlane Table of Contents Executive Summary Background Scope Approach Resource Requirements.

Slides:



Advertisements
Similar presentations
THE BUSINESS PLAN The Business Plan Chp. 5 ITB.
Advertisements

Creating a Winning E-Business Second Edition
UMC for Consulting & Services. UMC UMC for Consulting & Services UMC Profile UMC Profile UMC Range of Consulting Services UMC Range of Consulting Services.
2.09 Describe entrepreneurial planning considerations
Course: e-Governance Project Lifecycle Day 1
Enterprise Resource Planning
1 Dr. Djamal Ziani SAP Project Management. 2 ASAP Accelerated SAP (ASAP) is SAP's standard implementation methodology. It contains the Roadmap, a step-by-step.
SUMMER 2005 JUNE Preparing an Organizational Change Management Plan Org Change Management Activities by Project Phase.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 6 Initiating and Planning Systems Development Projects 6.1.
University of Southern California Enterprise Wide Information Systems Instructor: Richard W. Vawter.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Software Project Transition Planning
Modern Systems Analysis and Design Third Edition
Centers for IBM e-Business Innovation :: Chicago © 2005 IBM Corporation IBM Project October 2005.
Entrepreneurs discover an entrepreneurial opportunity when they find a compelling solution to an unsolved problem or unsatisfied need.
Managing Projects
Creating a Winning E-Business Second Edition
Feasibility and Business Planning
Introduction to Business
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
U.S. Department of Agriculture eGovernment Program Select Level Business Cases Overview of Business Case Sections.
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
Continuous Improvement Story Cover Page The cover page is the title page Rapid Process Improvement Story Template O Graphics are optional This CI Story.
The Main Idea Once an entrepreneur discovers a good business opportunity, the next step is to do market research. Market research helps to determine.
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
Finance Vic Rainsford Vice President Planning & Analysis Jim Palmer Sr. Mgr. Planning & Analysis.
The Value Driven Approach
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
Chapter 7 Enterprise Resource Planning (ERP). Objectives After studying the chapter, students should be able to.. Explain definition of Enterprise Resource.
Chapter 5. Why is Planning Important Need to plan because: Investors, guide for owners and managers, direction and motivation for employees, provide an.
Integration integration of all the information flowing through a company – financial and accounting, human resource information, supply chain information,
Chapter 8 Process Implementation Reference: Tan, A. (2007). Business Process Reengineering in Asia: A Practical Approach, Pearson Education, Singapore.
© 2003 Six Sigma Academy0 The Roles of Six Sigma Champion Workshop.
Info-Tech Research Group1 Manage IT Budgets & Cost World Class Operations - Impact Workshop.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Anytime, Anywhere Access Benefits Functionality Work Order Administration Dispatch Work Order Work Order Details New Work Order Additional Functionality.
HO CHI MINH CITY NATIONAL UNIVERSITY HO CHI MINH CITY UNIVERSITY OF TECHNOLOGY SYSTEM ANALYSIS AND DESIGN LECTURER: Nguyen Thanh Tung.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Enterprise Processes and Systems MIS 2000 Instructor: Bob Travica Updated 2016 Class 16.
Jitasa Overview.
Enterprise Processes and Systems
Systems Analysis and Design in a Changing World, 4th Edition
Modern Systems Analysis and Design Third Edition
Chapter 6 Initiating and Planning Systems Development Projects
Entrepreneurship Basic Structure
Identify the Risk of Not Doing BA
Responsibilities & Tasks Week 2
Business System Development
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Description of Revision
Chapter 4 Systems Planning and Selection
Quality Management Systems – Requirements
By Jeff Burklo, Director
Introduction to Projects
2.09 Describe entrepreneurial planning considerations
Project Management Process Groups
Indianapolis Life. Insurance Company. The Balanced Scorecard
Lecture 6 Initiating and Planning Systems Development Projects
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
Modern Systems Analysis and Design Third Edition
Read to Learn Describe how to prepare for your own business. Discuss the parts of a business plan.
Read to Learn Describe how to prepare for your own business. Discuss the parts of a business plan.
Executive Project Kickoff
{Project Name} Organizational Chart, Roles and Responsibilities
Chapter 6 Initiating and Planning Systems Development Projects
Contact center INNOVATION
Presentation transcript:

PROJECT 123 Business Case March 30, 2001

Page 1 Authors: Saltlane Table of Contents Executive Summary Background Scope Approach Resource Requirements Costs and Benefits Assumptions Conclusion

Page 2 Authors: Saltlane Situation Summary Company1 has carried out a Package Software Evaluation and selected XYZ as the solution for its enterprise application needs. In order to mitigate project risk as well as providing the project with a kick- start, this short scoping study project will define the work to be done, the phasing of it and define the organizational structure company1 that needs to be realized in XYZ system. Recommendation > Hierarchy workshop to establish Company1 organizational structure > Utilization of “AFrame” methodology to define scope > Development of phase program to identify implementation approach and sequence. Investment The investment in the proposed study is estimated at 5K to 6K. In the following, you will find an outline of the scope, the approach we will take, the deliverables you should expect, and the costs to complete this scoping study project. Executive Summary

Page 3 Authors: Saltlane Background - Need for Scoping Study Establishing the scope of a project is one of the most critical steps in order to mitigate the risk of any IT project. The project scope should be a written statement giving a description of what functionality, legal entities and business units are in and also OUT of scope and should be signed off by the steering committee. Establishing a well-defined scope: >Sets accurate expectations. >Defines the quantity of work to be done. >Sets the boundaries for the work that is to be done. The project scope includes the following areas: >Number of business units (size, geography, complexity) >Level of commonality planned across business units >List of processes in and out of scope >Level of organizational change (structure, relationships) >Company locations or number of sites >Line of business or product lines included and excluded in the scope. The scope also describes the functional areas to be covered by the Project and the degree of standardization (chart of accounts, cost center organization, master data, globally standardized business processes, etc.) as well as the freedom left for local modifications and add-ons.

Page 4 Authors: Saltlane Project Scope >The overall functional scope of this project is to identify the organizational and accounting structure of Comany1 to be implemented in XYZ, to identify the business processes and modules required to meet Company1 business requirements, and to provide a road map (phase plan) of how Company1 will get there. >The scope of the activities within this project consists of the following: >XYZ Hierarchy workshop >High level Requirements to identify project scope (business process and module) >Project phase planning

Page 5 Authors: Saltlane Deploy Pilot Training Solution Ready Build Solution Approach and Methodology Saltlane use the AFrame method. This s a proven approach for rapid development and requirements assessment. Saltlane AFrame Methodology Establish team, roles, and tools Quick look at scope and benefits Plan the project Prepare the Business Case Architecture design Test planning Implement End-user support Baseline Solution Planning Options Evaluation Opportunity Assessment Capture business requirements Evaluate options Build Solution UAT

Page 6 Authors: Saltlane Required Personnel Company1 >Project Manager (PM) >Business Process Owner (BPO) >Key Business Personnel Saltlane >Project Manager (PM) >XYZ Functional Consultant

Page 7 Authors: Saltlane Detail of Work WorkshopDuration Hierarchy Workshop3 Days Finance Workshop2 Days Sales Workshop1 Day Purchasing and Production Workshop 1 Day Phase Planning2 Days Global COA Workshop1 Day The exact sequence of these workshops will be decided given company 1 personnel availability.

Page 8 Authors: Saltlane Investment for scoping study project Estimates cited in this section are based upon the scope, approach and assumptions described in this document. Our fee for this work is based on our established hourly billing rates for the assigned staff and the hours required for the project. We have determined the time and pricing for your project as follows: Estimated Days Estimated Cost Services Rate DatesEstimated Investment $ 17,600 - $20,800 $ 18,720 - $ 21,600 $ 7,200 - $ 8,640 $ 4,320 - $ 5,760 Estimated travel expenses (if applicable): 10% - 15% Travel and expenses will be charged additionally and separately. The figure above only represents an estimate. Saltlane, as a firm, works under a time and materials policy. Company1 will be billed weekly based on the actual hours worked by our consultants. The estimates will be adjusted accordingly if the scope of the project expands or the work is completed in less time. The included estimates are based on the scope stated in this proposal. Any changes would be jointly agreed upon in writing. The figures quoted do not include any travel costs or expenses that may be necessary Days Days 5-6 Days 3-4 Days $ 56,480 - $ 68,320 Project Management $200/Hour Financials and Controlling$180/Hour Materials Management$180/Hour Production Planning$180/Hour Sales and Distribution$180/Hour Profitability Analysis$180/Hour

Page 9 Authors: Saltlane Benefits Tangible, short term Tangible, long term Increased revenue New revenue streams through new products General cost reductions Reduction of cycle time Reduction of inventory costs Increase of sales revenue Increased contribution Improved service levels Increased inventory turnover Improved on-time delivery Increased revenue New revenue streams through new products General cost reductions Reduction of cycle time Reduction of inventory costs Increase of sales revenue Increased contribution Improved service levels Increased inventory turnover Improved on-time delivery Reduction of product defects Reduced planning cycles Reduction of finance closing cycle Shortened order availability check Shortened time for invoice generation Standardisation of data and processes Internal company paradigm changes Reduction of product defects Reduced planning cycles Reduction of finance closing cycle Shortened order availability check Shortened time for invoice generation Standardisation of data and processes Internal company paradigm changes Intangible, short term Intangible, long term Elimination of doubled work processes Improved data accuracy Increased speed of data exchange Increased quotation activities Improved accuracy of projections Centralised billing Improved quality Increased speed of delivery Increased distribution readiness Elimination of doubled work processes Improved data accuracy Increased speed of data exchange Increased quotation activities Improved accuracy of projections Centralised billing Improved quality Increased speed of delivery Increased distribution readiness Improved customer service Increased first call response Reduction of customer complaints Improved motivation of employees Change towards innovation culture Increased product customisation Alignment of management and employees according to business objectives Increased staff/team creativity Improved corporate image in market Improved customer service Increased first call response Reduction of customer complaints Improved motivation of employees Change towards innovation culture Increased product customisation Alignment of management and employees according to business objectives Increased staff/team creativity Improved corporate image in market

Page 10 Authors: Saltlane Key Assumptions >Company 1 will assist the Saltlane Project Manager in coordinating and scheduling project meetings and workshops. >Identified team members will be available in a timely fashion. >Each key participant, chosen for these workshops, will attend all the workshop sessions. >Saltlane will not be responsible for any project delays that may result from issues with the infrastructure, hardware and third-party software used on the project. >All deliverables will be produced in English. >Location of the workshops will be at an agreed location. >A Global CFO has been identified by Company 1 >The Global CFO understands the company local accounting and legal accounting requirements for all Company 1 sites.

Page 11 Authors: Saltlane Conclusion >Company 1 has a mission to establish a visionary business system that is global, open, scalable, secure, and easily accessible, requiring minimal maintenance and human intervention to allow management control and monitoring of the growing business. >Saltlane would like to help realize that vision. We would like to be your XYZ implementation partner. The requirements of this project lie at the heart of our core competencies; cost effective XYZ implementation with an emphasis on business process integrity. As a first step towards this vision, Saltlane suggest that this short scoping study be undertaken. >We look forward to a successful project.