Zen Bubble

1
Zen Bubble

• Delta Group Presentation
• Jemily Chang
• David Chen
• Yueh-Lin Chen
• Jon Geraghty
• Pam Kilborn-Miller
• IMT 589 - Winter 2006

2
What is Bubble Tea?

• 1985, Taiwan
• Bubble Tea, also known as Boba Tea, consists of a
  mixture of iced or hot sweetened tea, milk, and
  possibly other flavorings.
• Flavors Passion fruit, Taro, Mint, Plum,

3
Scope

• Zen Bubble Tea Corporation
• Number of Employees 2,500
• Franchise Locations Major cities in North
  America and Asia
• Products Bubble tea and accessories

4
Problem Statement

• Zen Bubble is growing rapidly, especially in Asia
  and major metropolitan areas in North America
• The product development department frequently
  releases new recipes
• Management training programs are in high demand
• All personnel need fast access to company
  information, such as product and training
  announcements

5
Zen Bubble Solution

• Intranet portal
• Metadata schema facilitates access to the
  following information
• The Company
• Employees
• Franchises
• Supplier information
• Training program

6
Personas

• New Employee
• New Franchise Owner
• HR Administrator

7
The Zen Bubble Schema
8
Goals

• Facilitate the training for employees to meet
  business and career advancement needs
• Provide access to both online and printed
  documentation, such as curriculum materials, new
  recipes and product promotion materials

9
Challenges

• Return on investment
• Reusability
• Extensibility
• Ease of use

10
Approach

• Combined all the evaluation criteria
• Established scope, goal and scenario
• Bottom up vs. Top down
• Derived elements from role group criteria
• Consulted SchemaLogic
• Set up classes and sub-classes
• Clustered reusable elements
• Key considerations
• Necessity
• Redundancy
• Cost
• Extensibility
• Iterative process

11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
Zen Bubble Schema

• 8 classes
• BusinessEntity, ContentDescription, Contact,
  Documentation, Geography, Person, Product,
  TrainingProgram
• 9 sub-classes
• FranchiseStore, Supplier
• Recipe, Careerpath, Event, TrainingMaterial
• Employee, Instructor
• Beverage
• 58 elements, 38 reusable

15
(No Transcript)
16
Classes and Sub-classes
Franchise Store
Supplier
Employee
Instructor
Beverage
Career Path
Event
Recipe
Training Material
17
Reusable Classes
Franchise Store
Supplier
Employee
Instructor
Beverage
Career Path
Event
Recipe
Training Material
18
Reusable Elements
Element Class / Subclass
Identifier Documentation Person-Employee Training Program Business Entity Product
Ingredient.name Business Entity-Supplier Documentation-Recipe Product-Beverage
PositionTitle Documentation-CareerPath Person-Employee
Product.name BusinessEntity-FranchiseStore BusinessEntity-Supplier Product Documentation-Recipe
Relation.reference Documentation-Event BusinessEntity
Rights.accessrRight ContentDescription Person-Employee
Unit Person-Employee Documentation
19
Special Features

• Leverage machine processing to reduce labor costs
  
• Controlled vocabularies that are easy to use

20
Special Features

• Use elements to match people with documents for
  tighter security
• - Element for content
• - Element for people
• Documentation class is designed for print and
  online documentation only and serves as a company
  library

21
Persona

• I am a new employee
• I need to know
• Employee benefits
• Career path to be a manager
• Training programs and materials

22
Elements Evaluation Criteria
Person-Employee
Benefit
CourseFinished (S2)
PayRate (S2)
PositionTitle (S1, S2, H5)
Rights.accessRight (C7, E3, H1, H6, I2, I4)
Rights.role (C7, S2, H5, H6, I3)

ContentDescription
Date.issued (C5, S1, E1, E4, H2)
DC.Creator (C4, E1, E3, I5)
DC.Description (C4, E4, E5, E6)
DC.Publisher (H7, I5)
DC.Subject (C2, C6, S1, S2, S6, E1, E2, E6)
DC.Type (C2, S1, S2, E4, E5, I1)
Rights.accessRight ( C7, E3, H1, H6, I2, I4)
Title (E1)

Documentation
ContentDescription
Identifier (E2)
Unit (S2, H5, C6)
Documentation-CareerPath
CourseRequired (S2)
PositionTitle (S1, S2, H5)
23

• Elements Evaluation Criteria

TrainingProgram
Geography
TrainingMaterial
ContentDescription
Relation.isRequiredBy (S2)
Instructionalmethod (S2)
Coverage (C2, S1)
Identifier (E2)
Documentation
ContentDescription
Identifier (E2)
Unit (S2, H5, C6)
Documentation-TrainingMaterial
Language.subtitle
Language.verbal
ContentDescription
Date.issued (C5, S1, E1, E4, H2)
DC.Creator (C4, E1, E3, I5)
DC.Description (C4, E4, E5, E6)
DC.Publisher (H7, I5)
DC.Subject (C2, C6, S1, S2, S6, E1, E2, E6)
DC.Type (C2, S1, S2, E4, E5, I1)
Rights.accessRight ( C7, E3, H1, H6, I2, I4)
Rights.accessGroup (S2, H5, H6, I3)
Title (E1)

24
Persona

• I am a new franchise owner
• I need to know how to
• Get started!
• Find suppliers
• Contact other franchise owners
• Access revenue reports

25
Elements Evaluation Criteria
BusinessEntity
Contact
Geography
Business.name (H5, H8)
BusinessEntity-Supplier
Contact.position (S1)
Product.name (S2)
Ingredient.name (S2)
ContentDescription
Date.issued (C5, S1, E1, E4, H2)
DC.Creator (C4, E1, E3, I5)
DC.Description (C4, E4, E5, E6)
DC.Publisher (H7, I5)
DC.Subject (C2, C6, S1, S2, S6, E1, E2, E6)
DC.Type (C2, S1, S2, E4, E5, I1)
Rights.accessRight ( C7, E3, H1, H6, I2, I4)
Title (E1)

Geography
Geography.city (S1,S2)
Geography.country (S1, S2)
Geography.zipCode (S1)
Contact
Contact.address (S1)
Contact.email (E3)
Contact.name
Contact.phoneNumber
Documentation
ContentDescription
Identifier (E2, H4)
26
Persona

• I am a HR administrator
• I need to
• Arrange training courses for new recipes
• List of assistant managers
• List of metropolitan areas with more than 5
  stores
• Find management candidates from North America for
  an open position
• Find training programs in Seattle

27
Elements Evaluation Criteria
BusinessEntity
Contact
Geography
Business.name
Person
Contact
Person.firstname
Person.lastname
Person-Employee

CourseFinished (S2)
Identifier (E2, H4)
PositionTitle (S1, S2, H5)
Status.employee (S2)
Unit (S2, H5)

Documentation-CareerPath
CourseRequired (S2)
PositionTitle (S1, S2, H5)
Geography
Geography.city (S1,S2)
Geography.country (S1, S2)
Geography.zipCode (S1)
Contact
Contact.address (S1)
Contact.email (E3)
Contact.name
Contact.phoneNumber
28
Elements Evaluation Criteria
Geography
Geography.city (S1,S2)
Geography.country (S1, S2)
Geography.zipCode (S1)
ContentDescription
DC.Contributor (I5)
DC.Creator (C4, E1, E3, I5)
DC.Description (C4, E4, E5, E6)
DC.Publisher (H7, I5)
DC.Subject (C2, C6, S1, S2, S6, E1, E2, E6)
DC.Type (C2, S1, S2, E4, E5, I1)
Rights.accessRight ( C7, E3, H1, H6, I2, I4)
Title (E1)

TrainingProgram
Geography
TrainingMaterial
ContentDescription
Relation.isRequiredBy (S2)
Instructionalmethod (S2)
Coverage (C2, S1)
Identifier (E2)
29
(No Transcript)
30
Return on Investment

• Each element has its own ROI
• Focus on training will grow revenue
• Increase efficiency
• Information on demand
• Extensibility
• Decrease cost
• Machine processing vs. human processing
• Easy tagging
• 38 out of 58 elements are reusable

31
Criteria not addressed by schema

• End user (5, 7)
• Search and Navigation (4, 7)
• Integration (9, 10)

32
Obstacles

• What roadblocks did you run into?
• Difficult to create a schema for an organization
  that does not exist
• Misunderstanding of the root class idea
• The librarian tendency to go into great detail
• Were there any areas you couldnt address
  effectively?
• Lack of experience in business operations

33
Obstacles

• People
• Metadata experienced
• Metadata novices
• Technical issue
• SchemaLogic

34
Lessons Learned

• Chasing our tails
• Content vs. element
• Classes
• YOU HAVE TO STEP BACK!
• Mission impossible
• No schema can encompass everything
• No element can be used across all classes
• Project team
• Need comprehensive knowledge

35
Lessons Learned

• Criteria
• Which is most important?
• The purpose of metadata is to facilitate the
  information accessibility not to drive the user
  crazy
• Librarians announcement
• Weve always used schemas designed by other
  people.
• NOW, ITS OUR TURN!!!!!!

36
SchemaLogic Experience

• Good
• Introduced the concept of reusability
• Opportunity to review the elements, classes, and
  their relationships
• Ability to define the data type helped us think
  about its value
• Combining all the control vocabularies removes
  gaps and overlap
• Bad
• System is not stable
• Response time is slow
• Can not display the classes and the elements
  together
• Can not delete classes

37
Resources

• PC Chan and Sammie Chang
• Metadata
• Dublin Core Metadata Initiative
• Government Information Locator Service
• Gateway Education Material
• Business
• Bubble Tea Supply http//www.bubbletea.com/
• Boba Direct, Inc. http//www.bobadirect.com/
• Class readings and textbook

38
(No Transcript)