A Controlled Vocabulary for Knowledge and Data Ron Schuldt, Chair The Open Group UDEF Project May 2009
Wiki - Controlled Vocabularies “Controlled vocabularies provide a way to organize knowledge for subsequent retrieval. They are used in subject indexing schemes, subject headings, thesauri and taxonomies. Controlled vocabulary schemes mandate the use of predefined, authorized terms that have been preselected by the designer of the vocabulary, in contrast to natural language vocabularies, where there is no restriction on the vocabulary. ” The above provides a good description of the function that the UDEF offers to any enterprise since the UDEF is open and is extensible and can transcend any domain or function of any enterprise.
The Problem The following is a quote from “Launch into Aerospace: Industry’s Response to the Workforce Challenge” – see http: //www. aia-aerospace. org/assets/workforce_report_1_sept 08. pdf “The aerospace community risks the loss of intellectual capital and will be unable to meet the forecasted needs for business. ” “From the top of every organization, industry must embrace the systemic changes required to rebuild the foundation of America’s aerospace workforce. ” The following is a quote from The Aerospace Industries Association Draft Guidelines for Electronic Knowledge Management “One key element of the knowledge management process is to ensure that tacit knowledge is captured in explicit form and made available to the workforce in a timely and effective manner. ”
LMpedia – An Internal Wiki Vision LMpedia is an encyclopedia of Lockheed Martin knowledge written collaboratively by its employees. The innovation: Deliver to Lockheed Martin the success of the Internet phenomenon of wiki-based mass collaboration. Expected Value l Be a principal place where employees go to learn about Lockheed Martin topics – enabled with a Google-like search appliance l Be a customer reference for social media applications l Promote information sharing, discovery, and learning across the LM enterprise l Enable expertise location as a by-product l Enable the formation of effective virtual teams
Executive Goal “With regard to information flow, particularly sensitive information, we need to add a new element to our familiar practices, expanding ‘the need to know’ to include ‘the need to share. ’” Robert J. Stevens Chairman, President and Chief Executive Officer Lockheed Martin Corporation
LMpedia – Example Use of UDEF-Based Taxonomy Pilot Phase Taxonomy Business Development Communities / Groups Customers Disambiguation Article Internal Products / Services LM Organizations Non-Categorized People Practices Program Management Programs Sites Suppliers Technologies Terms / Definitions UDEF-Based Taxonomy Business Development Disambiguation Article External Organizations LM Business Units LM Functional Organizations LM Communities / Groups LM External Programs LM Internal Programs LM External Products/Services LM Internal Products/Services LM Documents LM Customers LM Suppliers LM Locations / Facilities LM Best Practices LM Terms / Definitions Other (Non-Categorized) Program Management Technologies
Data Modelers and UDEF Twenty Two Lockheed Data Modelers Received In-depth UDEF Training April 22 -24 2009 Conducted three consecutive days during lunch hour. Sample of Feedback Quote Extracts l I am currently the Data Modeling lead for the LMP 2 P program along with the conversion lead for converting legacy vendors into SAP. I only wish we would have known about this prior to our conversion! l Thanks for offering this course. It is very beneficial for all of us. l Most of the work I am doing is internal EBS but I think if I was working an ‘outside’ project (especially with a government agency), I would try & incorporate this logic into the model. Probably via the user-defined properties to generate Attribute Name/Column Name/UDEF Name cross-reference reports for specific audiences. Thanks for teaching me something!
UDEF Value Proposition Typical Interface Build Tasks UDEF Value API 1 API 2 l Analyze and document the Reduces dependency on system expert Sys 1 Sys 2 business requirements. l Analyze and document the data interfaces (design time) u Compare data dictionaries u Identify gaps u Identify disparate forms of Sys 1 Data Names Allows automated compare transformations as required at run time u Transform those data that require it Order ID Date Ship 9_1. 32. 6 Ship Dt i. 0_1. 1. 71. 4 Accept Point Business Id 3_6. 35. 8 Company Code Ship From Bus ID 3_6. 35. 8 Ship From Code a. a. v. 3_6. 35. 8 Ship To Code PO Line Num Step toward automated transform d. t. 2_13. 35. 8 Ship To ID Reduce design time labor PO Num Accept Loc representation l Perform data UDEF ID Sys 2 Data Names d. t. 2_1. 17. 8 Order Line Part Num 9_9. 35. 8 Prod Number Part Descr 9_9. 14 Prod Descr Part Ser 9_1. 1. 31. 8 Prod Ser Ship Qty 9_10. 11 Qty Ship Part UOM 9_1. 18. 4 Prod Unit Part Price 9_1. 2. 1 Prod Unit Price UID 9_54. 8 Part UID
Скачать презентацию A Controlled Vocabulary for Knowledge and Data
747b1d29c03fcb0530ad4bbfa4d53406.ppt