【正文】 1 Point of Views: ? InterCon?s point of view on a given industry or methodology, . some perspective is brought to the document rather than a recitation of facts/steps ? Often, but not always, a short document (1520 pages) ? includes “what we finds” 02 Detailed Industry Overviews: ? Detailed overview of a specific industry ? Same content as Point of View, but more detail and more emphasis on analysis ? Indepth description of industries (major players, industry structure, critical success factors) 03 Marketing Support Materials: ? Quality material to share with clients during business development and other client munication activities, including: ? Capability brochures/statements ? Conference presentations ? Horseblankets/whitepapers ? Proposals/proposal letters ? Red issues (selling issues for a given client/industry) ? RFP (Request for Proposal。 it is one of the main ?drivers? of the business of business education ? Accenture, PricewaterhouseCoopers (PwC), Cap Gemini Ernst Young, McKinsey Co., Bain Co., The Boston Consulting Group and Mercer (to name but a few) are the archetypal panies of today?s global ?informational? capital, which attract the ?highest calibre? graduates. InterCon ? German subsidiary of a global management and technology consulting pany ? The IKM project ? Virtual project team ? IT Strategy ? CAs Operational Processes ?CAs Information Management ?CAs People ? CAs GMTs (Industries) Tele Media Consumer Goods Chemicals Life Sciences Financial Services Energy Transport/ Tourism Automotive / Engineering Utilities etc. USA France UK Germany Disciplines PoAs Organisational Structure of InterCon Project Knowledge Capture At Project Start Before Project End Access to Knowledge Feedback and Rewards updates KBase updates KBase finalize knowledge capture report, copy to PKC, PM, GMT/Disc, CoE, CA, PoA KC at project end, hands over project archive to local Info Centre review KCapture report and together with stream leads, identify ?Best in Class? GMT documents Key Roles GMT KC GMT Knowledge Champion PM Project Manager PKC Project Knowledge Champion GMT KS GMT Knowledge Specialist CoE, CA, PoA, Discipline Knowledge Specialist CoE, CA, PoA, Discipline Knowledge Champion ALL Strategic Direction KBase Maintenance CoE, CA, Disc., GMT Expert Team and KS Define and municate the strategic knowledge management objectives and set expectations at all levels . at yearly KM conference in September, Capabilities Councils and other leadership meetings Quarterly meeting with GMT/Disc. to filter non relevant documents out, identify gaps and discuss expectations to fill the gaps. Update CDROM copies of Tool Boxes and KBases. Projects access knowledge via: ? the COMPASS (intra which provides worldwide access to the KBases), ? CoE, CA, Discipline, GMT Expert Teams and KCs (whose main role is to help develop, capture and disseminate knowledge), and ? Knowledge Specialists (who act as a global point of contact and answer specific, plex requests for information on a case by case basis, throughout project duration). Make Knowledge Management part of the feedback and reward loop: ? 360o expectation and feedback exchange for knowledge capture ? Reward most innovative and ?best in class? contributions. Internal knowledge management involves a number of actors at all stages of the project life cycle review documents and allocate to the relevant (GMT, CoE, CA, Disc.) KBases updates PP Database Contacts PM to identify PKC and KS identifies PKC and accountable KS sends “KC Pack” and GMT KBase CDROM pletes PP form and forwards to KS fills in KCapture report and sends to KS define and municate knowledge capture approach and set concrete capture expectations with team abstract and sanitize best documents and send to KS Involvement of all project team members is critical to achieving our objectives GMT, CoE, CA and Disciplines KC and experts play a key role in assessing innovations and best in class contributions. In the case that the PM identifies a KS other than the GMT KS, please refer to Panel 16 to see how the KCapture process changes. A joint conference call for small projects and an onsite expectation session for large projects is suggested A joint conference call for small projects and an onsite knowledge capture session for large projects is suggested Capturing knowledge from projects involves the following principles... Project Knowledge Capture updates KBase updates KBase finalize knowledge capture report, copy to PKC, PM, GMT/Disc, CoE, CA, PoA KC at project end, hands over project archive to local Info Centre review KCapture report and together with stream leads, identify ?Best in Class? GMT documents Key Roles GMT KC GMT Knowledge Champion PM Project Manager PKC Project Knowledge Champion GMT KS GMT Knowledge Specialist CoE, CA, PoA, Discipline Knowledge Specialist CoE, CA, PoA, Discipline Knowledge Champion review documents and allocate to the relevant (GMT, CoE, CA, Disc.) KBases updates PP Database Contacts PM to identify PKC and KS identifies PKC and accountable KS sends “KC Pack” and GMT KBase CDROM pletes PP form and forwards to KS fills in KCapture report and sends to KS define and municate knowledge capture approach and set concrete capture expectations with team abstract and sanitize best