Project Outline for Gates Corp

Project Purpose

(General project purpose statement, 1-4 sentences in length.)

The purpose of this project is to review the current state of master data management for Gates Corporation and recommend a global standard process, tools, and organization that drives, data quality, data standardization, and cross system consistency of Gates Master Data.

History

(Identify relevant history that may pertain to the project—e.g. sources of pain which led to this project’s creation, previous or related work, financial impact of not doing project, etc.)

Gates Corporation is the world's largest manufacturer of industrial and automotive belts and hoses. Gates manufactures and distributes common belt and hose products to common customers in 20+ countries around the world. Many of these locations are supported by different ERP systems. Gates has 28 different systems across its many locations. In order to properly service Gates global customer base, having insight into the global operations is imperative. Gates also needs to improve its decision making process to be supported by reliable information. Gates is spending money today to clean data, and to build systems around the lack of consistency of data that could be eliminated by have common consistent master data.

Project Objectives

(Define measurable items that will be accomplished from the project. Bullet list format is fine.)

A common process, organization, and tools globally to manage master data that provides

  • Consistent master data across systems (common key attributes) to support global initiatives like Business Intelligence and Customer Relationship Management
  • Repeatable process that drives quality while remaining responsive to local needs
  • Developed service level agreements tracking data quality, service performance, and policy adherence
  • Improve information accessibility through common consistent data
  • Global organization supporting the common master data management processes

Project Scope

(Describe the boundaries of the project, defining in- and out-of-scope elements. In-scope elements define the sum total of all of project products, their requirements, and/or features. Bullet list format is fine.)

  • In Scope:
  • All Gates entities
  • All Gates locations
  • Product master data
  • Customer master data
  • All entities, hierarchies and attributes for products and customers
  • Both creation and maintenance
  • Out of scope
  • Vendor master data
  • Material master data
  • BOM’s
  • Routes
  • Cost Centers
  • Accounts

Deliverables

(Describe in reasonable detail the tangible work products that are the outcome of the project work. Bullet list format is fine.)

  • Current state process maps
  • Future state global process map
  • Recommendation for needed support organization
  • Recommended tools for management of process
  • Business case for implementing recommended tools, organization, and processes
  • Project plan for implementation of recommendation

Project Approach

(Identify an overall feel for order of activity execution and any key dependencies. Bullet list format is fine.)

  1. Map current state setup and maintenance processes for most common systems, Oracle-NA, BPCS-EU, FourthShift-Asia, Oracle on Demand- Asia
  2. Identify common elements across systems
  3. Identify and define standards for identified elements
  4. Create common process for master data management
  5. Create recommendation for Organization, Process, and tools needed to support the global process
  6. Create Service Level Agreement for implemented recommendation
  7. Create business case for change

Critical Milestones and Event Dates

(Identify key timeline elements, which should map to scope, approach, and deliverables. Bullet list format is fine.)

  • Project Planning – February
  • Data Collection – February – March
  • Future stated definitions – April
  • Presentation of recommendation - May

Roles & Responsibilities

(Outline roles and responsibilities for the student teams, the company, and specific company representatives if possible. Bullet list format is fine.)

  • Gates
  • Master Data Business Analyst
  • Current state master data maintenance personnel
  • Sponsor – Steve Tomlinson VP BPMO
  • CU Student Team
  • Project Manager
  • Business Analysts
  • Data collection
  • Process mapping
  • Future state definition
  • Finance Analyst – Business Case

Quality Considerations

(Describe any special considerations regarding work product quality—e.g. the final product will be used or evaluated by senior company executives)

Final product will be presented by the team to an executive team that will include the CFO, business presidents, and operations leaders.

Assumptions

(Identify critical planning assumptions that may or will have an impact to project scope, time, quality, or satisfaction.)

  • Non-Denver based interactions will be handled over teleconference. Calls with Asia, Europe, and the Middle East will need to be handled at non-traditional work hours due to time difference.
  • If a trip is needed, coordination will happen through Gates Sponsor
  • Students have the freedom to make the best recommendation based on their view point to meet the needs of Gates for master data management
  • Gates is flexible with the time students are in the office and will accommodate remote work from Boulder campus when needed

University of Colorado – LeedsSchool of Business

Project Outline Document

1