Knowledge Management WG Meeting - The Knowledge Imperative: Key to Transformation

1. Knowledge Management WG MeetingThe Knowledge Imperative: Key to TransformationKM Business Case Successes and Potential Way Ahead for a KM Line of Business "Business Case". Brand Niemann, U.S. EPA, SICoP Chair, and KMWG Board Secretariat April 20th, 1 – 3 p.m., Atrium Ballroom B In conjunction with the 7th Annual Knowledge Management Conference and Exhibition April 19-21, 2006 Ronald Reagan Building Washington, DC

2. The Essence • Governance: KM WG Board provides a CoP of CoPs for SIG, Agency, and NGO KM-related activities. • Business Process: KM becomes a Line of Business within the new OMB E-Government –Federal Enterprise Architecture’s Federal Transition Framework (FTF). • Architecture: DRM 2.0 + Semantic Metadata = Knowledge Reference Model (KRM): • In Collaboration with the AIC’s new Data Architecture Subcommittee and the SICoP Semantic Wiki and Information Management WG. • Implementation: Wikis and Semantic Wikis. • See Wikis and Blogs, Panel 1-5: Knowledge in Action, Knowledge Management Conference, D. Calvin Andrus, Ph.D., Chief Technology Officer, Center for Mission Innovation, CIA. Something happens from people just working, but also need a Knowledge Repository underneath the Wiki to mine and to link to and from it (see next slide).

3. New IC Emerges Through Links Source: Wikis and Blogs, Panel 1-5: Knowledge in Action, 7th Annual Knowledge Management Conference, D. Calvin Andrus, Ph.D., Chief Technology Officer, Center for Mission Innovation, CIA, slide 22.

4. Introduction • My roles: • Enterprise Architect, EPA Office of the Chief Information Officer and Assistant Administrator for Environmental Information. • Architecture & Infrastructure Committee, Federal CIO Council – SOA CoP. • Chair, Semantic Interoperability Community of Practice (SICoP), KM WG, Best Practices Committee, Federal CIO Council. • Secretariat, KM WG Board (see next slide). • Help the SIGs and do Personal KM.

5. Wiki http://colab.cim3.net/cgi-bin/wiki.pl?KnowledgeManagementWorkingGroup

6. SICoP • The Semantic Interoperability Community of Practice (SICoP) has made considerable progress towards implementations of semantic technologies and web standards in the U.S. government with a series of white papers, conferences, and pilot projects. • White Papers: February 16, 2005, Introducing Semantic Technologies and the Vision of the Semantic Web ("DRM of the Future") and January 6, 2006, Semantic Wave 2006: Executive Guide to the Business Value of Semantic Technologies. • Conferences: February 9-10, 2006, 4th Semantic Interoperability for E-Government Conference. • Pilot Projects: Semantic Interoperability Architecture and Data Reference Model 2.0 Implementation (Making it Real). See http://colab.cim3.net/cgi-bin/wiki.pl?SICoP

7. SICoP • DRM 2.0: Vendor Implementations (5 so far), Recognitions from OMB and the Federal CIO Council Leadership, Press Coverage, State Adoption (3 so far), Industry Adoption (Lockheed Martin, etc.), and Relationship Building: • “You should be proud of the way that DRM 2.0 turned out and how it has been accepted by the data community. The open, collaborative development process sets it apart, and gives us a high standard for our other efforts across government.” • Richard Burk, Chief Architect and Director, Federal Enterprise Architecture Program, OMB, 12/22/2005.

8. DRM 2.0 Note: This begins to address KM! Source: Expanding E-Government, Improved Service Delivery for the American People Using Information Technology, December 2005, pages 2-3. http://www.whitehouse.gov/omb/budintegration/expanding_egov_2005.pdf

9. Semantic Metadata Source: DRM 2.0 Implementation Guide, page 6, October 17, 2005, 19 pp. See next slide for explanation.

10. SWIM • The point of this graph is that Increasing Metadata (from glossaries to ontologies) is highly correlated with Increasing Search Capability (from discovery to reasoning). • So DRM 2.0 + Semantic Metadata = Knowledge Reference Model (KRM). • DRM 2.0 Implementation Evolves to the SICoP Semantic Wikis and Information Management (SWIM) WG: • Antoinette Arsic, MITRE, and Mills Davis, Project10X, Co-Leads: • See http://colab.cim3.net/cgi-bin/wiki.pl?SICoP/SemanticWikisandInformationManagementWG • Semantic Wiki Review (15-20 projects circa April 2006): • Mills Davis, Project 10X, Co-Lead: • See http://colab.cim3.net/file/work/SICoP/SWIM/SemanticWikiReview.ppt

11. SWIM Source: Mills Davis, Semantic Wikis for Collaboration, Information Sharing, and Knowledge Management, Delphi Conference: ii2006 Information Intelligence Summit, Phoenix, Arizona, April 10-13, 2006, Phoenix, Arizona http://www.delphigroup.com/events/ii2006/speakers.htm#2458Davis http://colab.cim3.net/file/work/SICoP/SWIM/MDavis04122006.pdf

12. SWIM • Proposed Knowledge Management Community of Practice Architecture, Process, and Reference Model: Working to Become a Line of Business and Federal Transition Framework Catalog Entries (see slide 27). • DRM 2.0 and Metadata for the USGS Scientific Information Management Workshop, March 21-23, 2006: • Dr. Etienne Wenger on Communities of Practice and myself on Wikis to Support CoPs: • http://colab.cim3.net/cgi-bin/wiki.pl?UsgsSimw_2006_03_2123 • http://colab.cim3.net/cgi-bin/wiki.pl?USGSCoPofCoPs

13. SWIM • April 13, 2006, DoD CoI Forum and SWIM Meetings: • Net-Centric Enterprise Services (NCES) Status Presentation: • New Portal name (https://dko.us.army.mil) - Defense Knowledge Online, but really just about information sharing now. • But since NCES is the foundation for improved knowledge sharing and future knowledge creation, there is a need for additional tools and expertise to accomplish this goal. • Semantic Wiki Demonstration: • Add structure and modeling to information sharing and multiple metadata formats (e.g. ISO/IEC 11179, ontologies in OWL, etc.) using semantic agents underlying a Wiki interface (VisualKnowledge Semantic Wiki Beta).

14. SWIM • Upcoming Conferences and Meetings (demonstrations): • April 27, 2006, Convergence of Semantic Naming and Identification Technologies? • See http://colab.cim3.net/cgi-bin/wiki.pl?OpenGroupSICoP_2006_04_27 • April 28, 2006, Community Learning-Wiki Training: • See http://colab.cim3.net/cgi-bin/wiki.pl?CommunityLearning_CWE/ConferenceCalls_2006_04_28 • April 28, 2006, SWIM Meeting (9-12 noon): • See http://colab.cim3.net/cgi-bin/wiki.pl?SICoP/SemanticWikisandInformationManagementWG

15. SWIM • Upcoming Conferences and Meetings (demonstrations): • June 1-3, 2006, June 13-15, 2006, The Role of the New Data Reference Model 2.0, Invited Presentation at the Internal Government Agency Communications, Knowledge-Sharing and Collaboration Conference: • See http://www.ark-group.com • June 13-15, 2006, June 1-3, Conference of the National Knowledge Commission of India in Southern California (in planning): • See http://knowledge.indonet.com/ • July 18, Collaborative Expedition Workshop at NSF, Wikis and Semantic Wikis (in planning): • See http://colab.cim3.net/cgi-bin/wiki.pl?ExpeditionWorkshop

16. Success Story of the GeoCoP • Last spring our CIO Council CoP Outreach Team met with the Federal Geographic Data Committee to suggest a CoP approach to developing a Geospatial Data Profile for the FEA and offering to provide the Collaboration Wiki to support the work of the GeoCoP. • The GeoCop was formed, used the Collaborative Wiki, delivered its document, which OMB approved and distributed, and this was made a Line of Business in the FEA as announced in the President’s FY 2007 Budget! • See http://colab.cim3.net/cgi-bin/wiki.pl?GeoSpatialCommunityofPractice • GSA and OMB release RFI in support of the Geospatial LoB this week! • See http://www.gcn.com/online/vol1_no1/40351-1.html

17. Background • What is knowledge? • What are the two kinds of knowledge? • What is knowledge management? • How is knowledge management practiced? • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture? • What is a Knowledge Management Community of Practice Architecture, Process and Reference Model?

18. Background • What is knowledge?: • The full use of information and data combined with the skills. Competencies, ideas, intuitions, insights, and experiences of people. Information and knowledge are the fundamental resources that allow organizations to function intelligently. Information is the “what,” while knowledge is the “how, when, and why.” • Source: U.S. Department of the Interior, Bureau of Land Management, Knowledge Management Policy and Implementation Framework.

19. Background • What are the two kinds of knowledge?: • Explicit and tacit: • Explicit knowledge is information and data that can be documented and archived. • Tacit (or implicit) knowledge is human brain power – the “know-how” and “know-why” that lives inside people’s minds. The value of knowledge is greatly enhanced when it moves from tacit to explicit. Knowledge must be made explicit in user-friendly and accessible formats to be effectively disseminated. • Source: U.S. Department of the Interior, Bureau of Land Management, Knowledge Management Policy and Implementation Framework.

20. Background • What is knowledge management?: • KM is a set of processes and procedures for gathering the organization’s critical knowledge from wherever it resides, i.e., in computers, on paper, in employee’s heads, organizing and disseminating it for shared use, as well as preserving it for reuse when and where needed. • Source: U.S. Department of the Interior, Bureau of Land Management, Knowledge Management Policy and Implementation Framework.

21. Background • How is knowledge management practiced?: • KM is really about changing behaviors and work processes to free share one’s knowledge and expertise with others. • By supporting empowerment and responsibility at the individual level, KM focuses on understanding the knowledge needs of the organization and the sharing and creation of knowledge by becoming a part of the fabric of the organization. • KM seeks to provide timely answers through a balance between accessed to stored information that is directly relevant and networks with other people who are likely to know how to help. • Source: U.S. Department of the Interior, Bureau of Land Management, Knowledge Management Policy and Implementation Framework.

22. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and Enterprise Architecture? • The President Urges Agencies to Work Together: • “Our success depends on agencies working as a team across traditional boundaries to better serve the American people, focusing on citizens rather than individual agency needs … I thank agencies who have actively engaged in cross-agency teamwork, using E-Government to create more cost-effective and efficient ways to serve citizens, and I urge others to follow their lead.” • See http://www.whitehouse.gov/omb/egov/g-1-background.html

23. Background Federal Enterprise Architecture Reference Models: – See http://www.whitehouse.gov/omb/egov/a-2-EAModelsNEW2.html

24. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture (continued)?: • FEA Performance Reference Model: • Processes and Activities • Management and Innovation • Management policies and procedures, compliance with applicable requirements, capabilities in risk mitigation, knowledge management, and continuous improvement. • FEA Service Component Reference Model: • Digital Asset Services: • The Digital Asset Services Domain defines the set of capabilities that support the generation, management and distribution of intellectual capital and electronic media across the business and extended enterprise. • Content Management • Document Management • Document Referencing • Knowledge Management (see more details in next slide) • Records Management

25. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture (continued)?: • FEA Service Component Reference Model (continued): • Digital Asset Services- Knowledge Management: • Defines the set of capabilities that support the identification, gathering and transformation of documents, reports and other sources into meaningful information. • Categorization • Information Mapping / Taxonomy • Information Retrieval • Information Sharing • Knowledge Capture • Knowledge Discovery • Knowledge Distribution and Delivery • Knowledge Engineering

26. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture (continued)?: • Line of Business: A cross-agency effort to define, design, implement and monitor a set of common solutions for a government-wide business function or service. Prior to the initiation of a LoB, OMB will work with senior policy officials and subject matter experts to define the preliminary vision, goals, and objectives for a newly-formed LoB. • Source: Office of E-Gov and IT, Line of Business Initiatives, Concept of Operations, DRAFT, pages 3-4.

27. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture (continued)?: • The Federal Transition Framework (FTF) is a catalog of cross-agency information technology (IT) initiatives. It is a single information source for government-wide IT policy objectives and cross-agency initiatives. • Initiative usage scenarios are not limited to lines of business or other cross-agency initiatives that are sponsored by OMB. OMB encourages the use of the Federal Transition Framework and the LOB CONOPS as a model to support the development and organization of architectural work products for other types of cross-agency initiatives. • Source: Federal Transitional Framework (FTF), Release 0.5, DRAFT, Usage Guide, Catalog of Cross Agency Initiatives, and Metamodel Reference. • See http://colab.cim3.net/file/work/KMWGBoard/FTFMetamodel04092006.doc

28. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture (continued)?: • Architecture Principles for The Federal Government: • The Federal Government is Citizen-Centered • The Federal Government Is a Single, Unified Enterprise • The Federal Government Operates Collaboratively • The Federal Architecture is Business-Driven • Security, Privacy and Protection of Information are Core Government Needs • Information is a National Asset (see details in next slide) • The Federal Architecture Seeks to Simplify Government Operations Source: Draft from the OMB Federal Enterprise Architecture Program, March 21, 2006, for review by the Architecture & Infrastructure Committee and Chief Architect Forum.

29. Background • What is the relationship of KM to the President’s Management Agenda, E-Government, and the Federal Enterprise Architecture (continued)?: • Architecture Principles for The Federal Government (continued): • Information is a National Asset: • Statement: Information is an asset needed by the public to understand the activities of their government and it is an internal asset to be leveraged across the single, unified enterprise to improve performance, support decision-making, document agency activities and enable accurate reporting. • Rationale: The effective functioning of our constitutional democracy depends upon the participation in public life of a well informed citizenry, thus information must be available to them, and information must be shared among agencies to maximize the effectiveness of business decision-making throughout the Federal Government and beyond to external partners. • Implications: • This requires the Federal Government to improve its internal information sharing environment in order to better disseminate information to the public. • Authoritative sources of high quality information and data must be identified and maintained. • Program areas must provide access to specified data and information. • Authoritative data sources may need to be restructured and catalogued for easy dissemination, access and management.

30. Background • What is a Knowledge Management Community of Practice Architecture, Process and Reference Model? • Architecture Objectives: • Connects individual CoPs to a broader, coordinated effort that provides agile, rapid response, knowledge to citizens, decision makers, and researchers. • Provides an architecture that is “distributed, but connectable” in coordination with the FEA and the Architecture & Infrastructure Committee. • Builds on the DRM 2.0 and the community of knowledge management systems and vendors.

31. Background • What is a Knowledge Management Community of Practice Architecture, Process and Reference Model (continued)? • CoP Process: • Each employee should have a personal Wiki (“quick”) page to provide their context for the CoPs they participate in and to do knowledge capture and retention even after retirement. • CoPs are formed informally or formally around agency KM tasks. • Individual CoPs are networked by a CoP of CoPs and/or a Chief Knowledge Officer (CKO) to provide additional benefits to the agency and to an interact with CoPs outside the agency. • The CKO interacts with the KM Board to coordinate interagency CoP interactions and respond to specific needs from citizens, decision makers, and researchers.

32. Background • What is a Knowledge Management Community of Practice Architecture, Process and Reference Model? (continued): • Reference Model: • The DRM 2.0 CoP evolves to a collaboration on a Knowledge Reference Model for “distributed, but connectable” systems and applications by: • The Architecture and Infrastructure Committee’s new Data Architecture Subcommittee; • The KM WG Board; and • The new Service-Oriented Architecture CoP: • See http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP • Other?