Witches Brew Final Presentation

Witches Brew Final Presentation

WOE is Audrey Alexander, Gitika Gupta, John Ison, Madhuri Pinnamaneni, & Kathy

RichardsonIMT 589, Winter 2006

March 11, 2006 IMT 589 "Witches Brew" Team Zeta

2

Welcome to "Witches Brew" Inc. Home of "Wicked Good Coffee"!

• Established originally in Salem, Massachusetts, 1692.

• Domestic micro cap company ($50-300 million capitalization)

• ~2,000 employees• 4 Geographic Regions,

36 cafes opened nationwide as of 2006


3

Enterprise Metadata Primary Goals

• The schema is designed to facilitate the creation and exchange of information within and the context of Witches Brew enterprise. Specifically a strategy focusing on implementing a enterprise metadata schema would:– Reduce information costs– Provide an ability to manage information across the

enterprise– Support domestic market growth and allow for

eventual global growth.– Create an information interface allowing Witches

Brew to communicate with its vendors and clientele.


4

Metadata Beneficiaries

• Company Portal – Intranet, extranet, internet websites “WitchesWEB”

• Content Management System team– CMS system “Black Cat”

• HR team– HR IT system “Book of Souls”

• Enterprise Resource Planning – ERP system “Eye of Newt”

• Customer Relationship Management– CRM system “Cauldron”


5

Approach

• Criteria for role groups

• Aggregated criteria• Element creation• Validation• Grouping • Content classes• Refine schema


6

The Schema Model

• Function drives design– “Flat” provides loose coupling

and flexibility– “Faceted” – promotes

categorization across the enterprise

– “Hierarchical” – supports rich controlled vocabularies

“Faceted” “Hierarchical”

“Flat”

WitchesBrew

Schema


7

Schema Taxonomy

Class: Control

Content Item

Organization

Person

Product

Process

Relationship


8

Schema Classes

Control

+DC.Created+DC.Identifier+WB.Version.Schema

Person

+WB.Name.First+WB.Name.Last+WB.Role+WB.Email+WB.Encryption

Content Item

+DC.Subject+DC.Source-...

Product

+WB.Category+WB.Name.Product

Process

+WB.Name.Process+WB.ActionType

Organization

+WB.Name.Organization+WB.Role

Relationship

+WB.PrimaryObject+WB.SecondaryObject-...


9

Schema Elements

• Two source namespaces• Dublin Core (DC)

– DC.Audience– DC.Format– DC.Type

• Witches Brew (WB)– WB.Category– WB.Role– WB.Product– WB.Encryption


10

Schema Authority Control• Controlled Vocabularies

• Specifications– RFC – Request for Comment– ISO – International Standards Organization

• Domain– Active Directory (AD)– Access Control List (ACL)

Action Type Product

Audience Region

Category Role

Process Subject


11

Search & Navigation Process & Issues

• Process– Searching and browsing performed in the context of each

Information System silos.– Individuals and systems within Information System silos use

their own language to describe common items.

• Issues• Lost Information - spread across four Information System silos.

– Customer Management (CRM)– Enterprise Resource Planning (ERP)– Human Resources (HR)– Content Management System (CMS)

• Chaos – lack of a common language as key vocabularies are not synchronized nor controlled.


12

Search & Navigation Updates

• What’s changing?• Creation of a faceted taxonomy to support browsing categories

– Person– Product– Content (Item)– Organization– Process

• Vocabulary is being standardized across the enterprise throughauthority control

• What’s not changing?• Legacy systems


13

Search & Navigation Benefits

• Information can now be browsed across the four information silos– Customer Management (CRM)– Enterprise Resource Planning (ERP)– Human Resources (HR)– Content Management System (CMS)

• Common language assists searching


14

End User Process & Issues

• Process – End users rely on intranet

• workgroup website for project related information• company internal websites

• Issues– Accessing company information easily– Accessing personal information securely– Finding contacts within the company easily– Looking up customer information – Accessing corporate resources


15

End User Updates

• What’s changing?– Searching information– Browsing information– Protecting personal information– Viewing current and authentic information– Sharing information

• What’s not changing?– Access to the information they need


16

End User Benefits

• Ability to use the portal as a one-stop place for all information

• Confidence in search results and browsing capabilities

• Ease of use

• Satisfying user experience


17

HR Process & Issues

• Process– Primarily protects data about individuals in the company

– Manages the employee records system for the company

– Authority over all human resources information

– Authority over the source of record for information related to people within the company

• Issues – Security

– Privacy

– Primacy

– Timeliness

– Accuracy


18

HR Updates

• What’s changing?– Rights access granted to appropriate individuals and

managers – Standardized data supports aggregation of

information– Timeliness and accuracy of employee data available

to other systems much easier to control• What’s not changing?

– HR IT still controls access to employee information through HR applications

– Maintains security and privacy of individual information


19

HR Benefits

• Exposes needed HR information and documents for all employees easily

• Reinforces security and privacy issues for employees

• Ensures timeliness and accuracy of employee data to other systems

• Ensures controlled access


20

CMS Process & Issues

• Process– Well established content publishing and

approval process– CMS system (“Black Cat”)

• Issues– Synchronizing people, products, publications– Keeping track of staffing changes– Sharing content with internal audiences


21

CMS Updates

• What’s changing?– Product, people, publications managed at enterprise

level– Workflow “building blocks” standardized– We will need to add more data about rights,

encryption, and accessibility standards to our content

• What’s not changing?– We keep our CMS and production methods– Same internal workflows (editing, quality control)


22

CMS Benefits

• No more product name nightmares

• Reduces duplicate data entry (people, products, etc.)

• Metadata that we manage is only what is directly applicable to us

• Ability to use workflow enterprise-wide


23

Integration Process & Issues

• Process– Currently there is no process– Created new Integration Team under IT

• Issues– Rapid Growth– Lots of “information silos”– Balancing everyone else’s needs and issues

to achieve a common goal


24

BusinessBusinessProcessesProcesses

WWW

Integration of People, Content Integration of People, Content

and Processes at Internet Speedand Processes at Internet Speed

PeoplePeople ContentContent

Witches Council


25

Integration Framework

HR

WitchesWEBPortal

Intranet Internet


26

Integration Updates

• What’s changing?– Form Witches Council – Create Enterprise Metadata Schema– Address 5 areas: Project Administration, Content,

Security, Change Control, Display & Accessibility – Engage stakeholders to agree on common goals – Facilitate collaboration and communication– Introduce new processes and system (SchemaLogic)

• What’s not changing?– Stakeholders still retain primary control & ownership

over their information


27

Integration Benefits

• Provides strong framework for managing and delivering appropriate information to end users

• Standardizes shared information

• Supports future growth of WitchesWEB for internal and external users


28

Obstacles

• May all your problems be technical—Jim Gray, Microsoft Corp, 1998 Turing Award

winner

• Common understanding of terminology

• Running in circles makes one dizzy!

• Competing interests

• Ourselves –


29

Lessons Learned

• Metadata is hard

• Keep it simple, justify complexity

• Focus on what you need/use now

• Be thrifty with your “wish list”

• Return to the requirements as you iterate

• Think about what the technology can support


30

Resources

• A few of our resources….– Tannenbaum and Bedford

approaches– Scenarios & Evaluation

Criteria– Dublin Core & Stu Weibel– IMT 530– Affinity diagramming!

QUESTIONS?

Witches Brew Final Presentation

Documents

witches brew team zetawelcome

witches brew team zeta

role wb

identifier wb

primaryobject wb

email wb

roleorganization wb

category wb