1. Social/Political Issues IMT 589 January 28, 2006

2. 1/28/2006IMT589- Applied and Structural Metadata2 Three Areas of Interest Non-Technical Relation to business needs Development process Management process Technical Delivery mechanisms Protection of assets Technical Support Provides assistance and resources for users Manages the overall metadata solution

3. 1/28/2006IMT589- Applied and Structural Metadata3 People Issues Important part of any project Even more so with metadata Language barriers Interest barriers Understanding barriers Time/resource barriers Without buy-in, failure is guaranteed Best approach is building from a small base, with something people need as example

4. 1/28/2006IMT589- Applied and Structural Metadata4 An Example from Microsoft Multiple attempts within Microsoft to build taxonomies for managing information Duplicated effort and reinvention was wasting time and money Business owners knew their vocabulary needs, but did not know how to implement Information Services could offer design and management expertise in this area

5. 1/28/2006IMT589- Applied and Structural Metadata5 Taxonomy Relationships The Microsoft Taxonomy MS Preferred Taxonomy/ Preferred Terminology Services Taxonomy Missouri CSG-KM Taxonomy Product Group Taxonomy SAP/ Feedstore HR/EMD Web Taxonomy ITGWeb Taxonomy FinWeb Taxonomy

6. 1/28/2006IMT589- Applied and Structural Metadata6 The Approach Realized that distributed owners needed a flexible solution Separation of management and ownership of vocabularies was key Needed to have core set of attributes (tags), with latitude for variation Needed to accommodate core and non- core vocabularies

7. 1/28/2006IMT589- Applied and Structural Metadata7 The Landscape CONTENT Sales Information Product InformationFinance InformationIT Information IS InformationHR Information ROW METADATA SEARCH END USER MS Taxonomy/ Vocabularies CSG TaxonomyIS Taxonomy Product TaxonomyOther MSWeb Search InfoWeb Search FinWeb Search ITGWeb Search Other Field UserGeneric User Publishing ToolsAuto Tagging Search ExpansionMetadata Specific

8. 1/28/2006IMT589- Applied and Structural Metadata8 Business Model Partner Information Services Service Level Agreement Contracts for deliverables from Information Services (search, taxonomy, navigation, consulting) Defines deliverables, timelines, response times, scope of work Provides services per SLAs, manages resources and tools necessary for delivery, coordinates across groups to define standards

9. 1/28/2006IMT589- Applied and Structural Metadata9 Roles and Responsibilities Sponsors Ensure participation Business Owners Drive requirements Knowledge Architecture Board Communicate and Validate Information Services Architect, build and manage service

10. 1/28/2006IMT589- Applied and Structural Metadata10 Roles and Responsibilities Sponsors Ensure commitment of business owners to Knowledge Architecture project Champion Knowledge Architecture project as key Microsoft initiative Have final say on vocabulary ownership

11. 1/28/2006IMT589- Applied and Structural Metadata11 Roles and Responsibilities Business Owners Set business requirements for taxonomy ensure appropriate level of representation on Knowledge Architecture Board Provide business requirements for implementation Work through Information Services in areas requiring cross-functional collaboration Provide feedback on success of Information Services efforts

12. 1/28/2006IMT589- Applied and Structural Metadata12 Roles and Responsibilities Knowledge Architecture Board Composed of program managers, product managers, and developers from business groups Approves overall plan for core vocabulary collection and management Responsible for making sure core vocabularies are being managed effectively Ensures vocabularies meet Business Owners’ requirements Assists in User Education and Usability Testing Keeps Business Owners informed of progress

13. 1/28/2006IMT589- Applied and Structural Metadata13 Roles and Responsibilities Information Services Leads Knowledge Architecture approach Creates infrastructure and develops toolkits to support Knowledge Architecture Documents work for MS developers Manages and/or hosts core vocabularies and metadata Coordinates between vocabulary owners where common vocabulary is appropriate Provides a single access point for Microsoft vocabularies, whether hosted by Information Services or not. Collects and makes available IR solutions built using the MS vocabulary and metadata sets Reports back to Sponsors and Business Owners on business impact of deliverables

14. 1/28/2006IMT589- Applied and Structural Metadata14 Organization Structure Inward Facing Outward Facing