π Lecture 33 β CORPORATE INTRANET, EXTRANET, AND PORTAL
π Overview: This lecture explores knowledge portals as web-based applications that provide a single point of access to online information, acting as virtual workplaces for knowledge sharing. It covers portal evolution, technologies, functionality, and business applications, explaining how organizations can leverage portals to manage both structured and unstructured data for competitive advantage.
ποΈ Topics Covered
The lecture covers the definition and evolution of portals from search engines to knowledge portals, business challenges that drive portal adoption, portal technologies including collaboration tools, content management and intelligent agents, and a comprehensive test section with 13 questions addressing portal implementation, benefits, and practical applications across different business contexts.
π Lecture Summary
KM Tools and Knowledge Portals
Portals are Web-based applications which provide a single point of access to online information. These can be regarded as virtual workplaces which promote knowledge sharing among end-users (e.g., customers, employees), provides access to data stored in databases and data warehouses, and helps organize unstructured data.
Evolution of Portals:
- Initially portals were merely search engines
- In the next phase they transformed to navigation sites
- Portals evolved to include advanced search capabilities and taxonomies
- Also called Information portals because they deal with information
- Organizations are becoming increasingly aware of opportunities from using dormant information
- Portals can integrate applications by combining, analyzing, and standardizing relevant information
- Knowledge portals provide information about all business activities and supply metadata to support decision making
- Knowledge portals focus on how information will be used by knowledge workers, not just content
- Knowledge portals have two kinds of interface: knowledge consumer interface and knowledge producer interface
- Enterprise Knowledge Portals (EKP) can distinguish knowledge from information and produce knowledge from raw data
π Definition β Knowledge Portal: A web-based application that provides information about all business activities and is capable of supplying metadata to support decision making, focusing on how information will be used by knowledge workers.
Business Challenge
Most businesses face an inherent pressure to optimize operational processes to reduce cost and enhance quality. Customer-oriented systems allow organizations to understand customer behavior patterns and offer the right product at the right time. Often, organizations need to commercialize their products at the lowest possible price.
π‘ Why this matters: Understanding business challenges helps identify why portals are necessary for modern organizations to stay competitive.
Portals and Business Transformation
Problems arise from two fundamental aspects of present computing technology:
- The explosion in quantity of business information captured in electronic documents leads organizations to lose grip on information as they upgrade processes
- The fast speed of information content growth requires strict internal discipline to expose and integrate enterprise knowledge sources
Types of pressures faced by most organizations:
- Shorter time to market
- More demanding investors/customers
- Knowledge worker turnover
Market Potential
Knowledge portals are emerging as key tools for supporting the knowledge workplace. The infrastructure components of the Enterprise Information Portal (EIP) market include:
- Business intelligence
- Content management
- Data management
- Data warehouses/data marts
Knowledge Portal Technologies Functionality
The key functionalities include:
- Gathering
- Categorization
- Collaboration
- Distribution
- Personalization
- Publishing
- Searching/Navigation
Collaboration
The aim of collaboration tools is to create a collaborative KM system supporting sharing and reusing information. Collaboration implies the ability for more than one person to work together in a coordinated fashion over time and space using electronic devices.
Types of collaboration:
- Asynchronous collaboration: Human-to-human interactions via computer systems having no time/space constraints
- Synchronous collaboration: Human-to-human interactions via computer systems that occur instantly
Push Technology: Places information where it is easily visible. Pull Technology: Requires specific actions to retrieve information.
π Definition β Asynchronous Collaboration: Human-to-human interactions via computer systems with no time or space constraints. π Definition β Synchronous Collaboration: Human-to-human interactions via computer systems that occur instantly.
π Example: Email and discussion forums are examples of asynchronous collaboration, while instant messaging and web conferencing are examples of synchronous collaboration.
Content Management
Content management requires directory/indexing capabilities to automatically manage ever-growing enterprise data warehouses. It addresses the problem of searching for knowledge in all information sources, including structured and unstructured internal information like office documents, collaborative data, MIS, experts, and external information.
Metadata is required to define the types of information. Content management handles how documents are analyzed, categorized, and stored. Categorizing organizes similar documents into smaller groups. Since document collections are not static, portals must provide taxonomy maintenance β as new documents are added, they must be placed in the proper taxonomy using classification technology.
π Definition β Content Management: A system requiring directory/indexing capabilities to automatically manage enterprise data, handling how documents are analyzed, categorized, and stored.
Intelligent Agents
Agents are software able to execute a wide range of functional tasks (e.g., comparing, learning, searching). Intelligent agents are tools applied in the context of EKPs, though still in their infancy with most applications being experimental.
As relationships between organizations and customers become more complex, intelligent agent technology can help address needs for understanding customer relationships. Customers set priorities while purchasing; intelligent agents can master individual customer demand priorities by learning from experience and analyzing these priorities qualitatively and quantitatively.
Customer services benefiting from intelligent agents:
- Customer assistance (customized) with online services
- Customer profiling and integrating profiles into marketing activities
- Forecasting customer requirements
- Executing financial transactions on behalf of customers
- Negotiating prices/payment schedules
π Definition β Intelligent Agents: Software tools that can execute functional tasks like comparing, learning, and searching, applied in EKP contexts to understand customer priorities and needs.
Test Your Understanding
Question 1: Need for portals arises from pressures including shorter time to market, knowledge worker turnover, and more demanding customers/investors. Data warehouses give access to collected data; portals provide the interface to reach and manipulate data in data warehouses plus collaboration services.
Question 2: Enterprise portals provide the same interface for employees, managers, customers, and suppliers globally. It's better to deploy portals over the Internet rather than Intranet for unrestricted worldwide access.
Question 3: Enterprise Information Portals use push/pull technologies, integrate disparate applications, and support bi-directional information exchange. Enterprise Knowledge Portals are goal-directed toward knowledge production, acquisition, transmission, and management, focused on business processes, and include all EIP functionalities.
Question 4: Companies need strategies and processes to utilize intellectual resources at strategic and operational levels. Next-generation information platforms (enterprise portals) and real-time tools (instant messaging, web conferencing, streaming media) are required.
Question 5: Static portals provide unified interface to enterprise applications. Dynamic portals have collaboration and interactivity features.
Question 6: Content management in EKP uses directory/indexing capabilities with metadata to manage structured and unstructured data. It can go outside the enterprise using crawlers to find pertinent Internet data, index it, and deliver to analysts.
Question 7: For globally distributed organizations, bandwidth is a fundamental constraining factor for many portal applications.
Question 8: Examples include Amazon.com (B2C), Plasticexchange.com (B2B for plastics), www.e-government.govt.nz (C2G), and www.firstgov.gov (comprehensive government portal).
Question 9: Portal accessibility technologies include Internet, Intranet, Extranet, and mobility portals.
Question 11: For an audit firm, recommended system is an Enterprise Knowledge Portal (EKP) with functionalities: Gathering (capture accounting standards), Categorization (organize Word/Excel files), Distribution (support electronic documents), Collaboration (asynchronous tools like email/discussion forums), and Search/Navigate.
Question 12: A hardware retailer can use a knowledge portal with synchronous collaboration tools for real-time customer support. Benefits include improved customer retention, reduced costs (fewer phone calls/site visits), and new market segments. Additional support includes FAQ sections updated from customer input, helping manufacturers improve product quality.
Question 13: Knowledge portals enable different business units to interact and collaborate for best results, enabling web-based workplace for drag-and-drop file sharing, multithreaded discussions, real-time messaging, and polling. Productivity increases as users across business units stay informed about enterprise activities.
β Key Takeaways
The most critical concepts from this lecture are that knowledge portals serve as virtual workplaces providing single-point access to online information, evolving from simple search engines to sophisticated platforms with knowledge consumer and producer interfaces. Enterprise Knowledge Portals (EKP) can distinguish knowledge from information and produce knowledge from raw data, integrating functionalities including gathering, categorization, collaboration, distribution, personalization, publishing, and searching/navigation. Collaboration can be asynchronous (no time/space constraints) or synchronous (instant interactions), supported by push and pull technologies. Content management requires directory/indexing capabilities with metadata to handle structured and unstructured information, while intelligent agents can learn and analyze customer priorities. The test questions illustrate practical applications across B2B, B2C, B2G, C2C, and C2G contexts, emphasizing how portals address business pressures like shorter time to market, knowledge worker turnover, and demanding customers.
π§ Quick Revision Questions
- What are the two interfaces of knowledge portals and what is the purpose of each?
- Distinguish between asynchronous and synchronous collaboration, providing an example of each.
- What is the difference between push technology and pull technology in the context of knowledge portals?
- List five customer services that can benefit from intelligent agent technology.
- What are the three types of pressures faced by most organizations that drive portal adoption?
π Lecture 34 β KM Systems and Technical Layers
π Overview: This lecture explores the architecture and technical layers of Knowledge Management systems, focusing on how technology enhances communication and knowledge sharing in the e-world. It details each layer of the KM system architecture, from user interface to repositories, and explains their roles in enabling effective knowledge transfer, security, and collaboration.
ποΈ Topics Covered
The lecture covers the technical core of KM systems, user interface layer, authorized access layer, collaborative intelligence and filtering layer, knowledge-enabling application layer, transport layer, middleware layer, and repositories layer. It also distinguishes between key concepts like transport and application layers, usability and portability, and collaborative intelligence versus intelligent agents.
π Lecture Summary
Knowledge Transfer in E-World β The Technical Core
The technical core aims to enhance communication and ensure effective knowledge sharing. Technology provides opportunities for managing tacit knowledge in communication areas. Communication networks create links between necessary databases. The term technical core refers to the totality of required hardware, software, and specialized human resources. Expected attributes include accuracy, speed, reliability, security, and integrity. Since an organization can be thought of as a knowledge network, the goal of knowledge economy is to push employees toward greater efficiency and productivity by making best possible use of the knowledge they possess. A knowledge core usually becomes a network of technologies designed to work on top of the organization's existing network.
π‘ Why this matters: The technical core establishes the foundation upon which all KM system layers operate, determining system performance and capability.
User Interface Layer
A web browser typically represents the interface between the user and the KM system. This is the top layer in the KM system architecture. The way text, graphics, and tables are displayed on the screen simplifies the technology for the user. The user interface layer should provide a way for the proper flow of tacit and explicit knowledge. Necessary knowledge transfer between people and technology involves capturing tacit knowledge from experts, storing it in a knowledge base, and making it available for solving complex problems.
Features to consider in user interface design:
- Consistency
- Relevancy
- Visual clarity
- Usability
- Ease of navigation
Authorized Access Layer
This layer maintains security and ensures authorized access to knowledge captured and stored in organizational repositories. Knowledge is usually captured using internet, intranet, or extranet. An organization's intranet represents the internal network of communication systems. Extranet is a type of intranet with extensions allowing specified people (customers, suppliers, etc.) to access some organizational information. Issues related to the access layer include access privileges and backups. The access layer focuses on security, use of protocols (like passwords), and software tools like firewalls.
Firewalls can protect against:
- E-mails that can cause problems
- Unauthorized access from the outside world
- Undesirable material (movies, images, music, etc.)
- Unauthorized sensitive information leaving the organization
Firewalls cannot protect against:
- Attacks not going through the firewall
- Viruses on floppy disks
- Weak security policies
Collaborative Intelligence and Filtering Layer
This layer provides customized views based on stored knowledge. Authorized users can find information (through a search mechanism) tailored to their needs. Intelligent agents (active objects which can perceive, reason, and act in a situation to help problem solving) are found to be extremely useful. In client/server computing, there is frequent and direct interaction between the client and the server. In mobile agent computing, the interaction happens between the agent and the server. A mobile agent roams around the internet across multiple servers looking for correct information, with benefits in fault tolerance, reduced overall network load, and heterogeneous operation.
Key components of this layer:
- The registration directory that develops tailored information based on user profile
- Membership in specific services (e.g., sales promotion, news service)
- The search facility (e.g., a search engine)
Prerequisites for this layer include: security, portability, flexibility, scalability, ease of use, and integration.
Knowledge-Enabling Application Layer (Value-Added Layer)
This creates a competitive edge. Most applications help users do their jobs in better ways. They include knowledge bases, discussion databases, decision support, and other tools.
Transport Layer
This is the most technical layer. It ensures the organization becomes a network of relationships where electronic transfer of knowledge is routine. This layer associates with LAN (Local Area Network), WAN (Wide Area Network), intranets, extranets, and internet. In this layer we consider multimedia, URLs, connectivity speeds/bandwidths, search tools, and managing network traffic.
Middleware Layer
This layer makes it possible to connect between old and new data formats. It contains a range of programs to perform this connection function.
Repositories Layer
This is the bottom layer of the KM architecture, representing the physical layer where repositories are installed. These may include legacy applications, intelligent data warehouses, operational databases, etc. After establishing the repositories, they are linked to form an integrated repository.
Distinguish Between Key Concepts
a. Transport Layer vs. Application Layer The Transport Layer standardizes exchanges between operating systems of computers in the system. It includes LANs, WANs, intranets, extranets, and the Internet. The Application Layer provides applications that help users do their jobs better, including knowledge bases, discussion databases, sales force automation tools, yellow pages, decision support, and imaging tools.
b. Usability vs. Portability Usability ensures user-friendly software. Portability is a measure of how well software will run on different computers.
c. Profiling vs. Repository Profiling in KM systems is generating a graphic or textual representation of people in terms of criteria such as skills, personality traits, etc. Repository is a storage subsystem, such as a database for data, information, or knowledge storage.
d. Collaborative Intelligence vs. Intelligent Agent Collaborative Intelligence provides customized or personalized views based on stored knowledge, designed to reduce search time by combining the knowledge sought and the user's profile. Intelligent agents are active objects that can perceive, reason (learn from past mistakes), and act in situations to assist in problem solving, retrieving the right information, behaving as personal assistants that cooperate with human users.
β Key Takeaways
Students must understand the layered architecture of KM systems, from the user interface at the top to the repositories at the bottom. The User Interface Layer simplifies technology for users and enables flow of tacit and explicit knowledge. The Authorized Access Layer ensures security through firewalls, passwords, and protocols. The Collaborative Intelligence and Filtering Layer provides customized views using intelligent agents and mobile agents for efficient information retrieval. The Transport Layer (including LAN, WAN, intranets) and Middleware Layer handle connectivity and data format conversion. Understanding distinctions between layers and concepts like usability vs. portability and collaborative intelligence vs. intelligent agents is critical for exam preparation.
π§ Quick Revision Questions
- What are the five expected attributes of technology under the technical core?
- What features should be considered in user interface design for KM systems?
- What three things can firewalls protect against, and what three things can they not protect against?
- What is the difference between client/server computing and mobile agent computing?
- What is the bottom layer of KM architecture, and what types of repositories might it include?
π Lecture 35 β KM System and Life Cycle Approach: Conventional vs KM
π Overview: This lecture explores the fundamental differences and similarities between conventional systems development life cycles and Knowledge Management System Life Cycles (KMSLC). It emphasizes why a life cycle approach is essential for building KM systems, compares the roles of systems analysts versus knowledge developers, and introduces key concepts like rapid prototyping, verification, validation, and user-expert attributes. Understanding these distinctions is critical for designing effective KM systems that are result-oriented and interactive.
ποΈ Topics Covered
The lecture begins by detailing the key differences between conventional and KM systems, followed by their key similarities. It then discusses structuring problems and tasks within a rapid prototyping cycle, compares user and expert attributes, outlines various KMSLC approaches, explains the importance of evaluating the existing infrastructure, and concludes with a test-your-understanding section that clarifies concepts like verification vs. validation, knowledge developer vs. systems analyst, pupil vs. tutor user, and projection vs. avoidance.
π Lecture Summary
Key Differences between Conventional vs. KM Systems
The lecture highlights several critical distinctions between conventional information system development and KM system development. In conventional systems, the systems analyst gathers data from users who know the problem but not the solution, and the process is primarily sequential, process-driven, and documentation-oriented. In contrast, a knowledge developer gathers knowledge from knowledgeable people who know both the problem and the solution. The KMSLC is incremental and interactive, result-oriented, and allows for verification and validation from the beginning of the cycle. Testing in conventional systems occurs after the system is built, while KMSLC supports rapid prototyping that can incorporate changes on the spot. Systems management is much more extensive for conventional systems than for KMSLC.
π Definition β Systems Analyst: A specialist in building information systems who acts as the architect, including designing, testing, and installing the system, and primarily interacts with novice users who know the problem but not the solution.
π Definition β Knowledge Developer: A specialist in building knowledge-based systems who acts as the key architect, interacting with knowledgeable experts who know both the problem and the solution.
π Key Distinction: Conventional SDLC β Sequential, process-driven, testing at end. KMSLC β Incremental, interactive, result-oriented, verification from start, supports rapid prototyping.
Key Similarities
Despite their differences, both cycles share fundamental similarities. Both life cycles start with a problem and end with a solution. The early phase of conventional systems involves information gathering, while in KMSLC, the early phase requires knowledge capture. Verification and validation of a KM system are often very similar to conventional systems testing. Lastly, both the systems analyst and the knowledge developer must choose the appropriate tools for designing their intended systems.
Structuring the Problem / Rapid Prototyping
The lecture presents a visual cycle for rapid prototyping in KMSLC. The process involves: Structuring the Problem β Reformulating the Problem β Structuring the Task β Making Modifications β Building a Task. This cycle repeats, emphasizing that KMSLC is inherently iterative, unlike the linear conventional approach.
Users and Experts: A Comparison
The lecture provides a comparative table of attributes for users vs. experts. Users have high dependence on the system, low ambiguity tolerance, and their contribution is information, whereas experts have low dependence on the system, high ambiguity tolerance, and their contribution is expertise/knowledge. Usersβ knowledge is readily available, while expertsβ knowledge is not readily available. Cooperation is required for users but is not required for experts.
π Example β User vs. Expert: In a troubleshooting KM system, a junior technician (user) has high dependence on the system to find a solution, tolerates ambiguity poorly, and provides information about the problem. A senior engineer (expert) has low dependence on the system, can handle ambiguous problems, and provides deep expertise rather than raw data.
KMSLC Approaches
Due to a lack of standardization, multiple approaches have been proposed for the KMSLC. While the conventional systems development approach can still be used for developing KM systems, it is usually being replaced by iterative design and prototyping, reflecting the dynamic nature of knowledge capture and sharing.
Evaluating the Existing Infrastructure
KM systems are developed to improve productivity and potential of employees and the company. The existing knowledge infrastructure is evaluated to ensure that the new system does not simply abandon the present ways of doing things. This evaluation provides the perception that the new system builds upon, rather than replaces, existing practices.
β Key Takeaways
The single most important distinction is that conventional SDLC is sequential and documentation-oriented, while KMSLC is incremental, interactive, and result-oriented, supporting prototyping and early verification. Students must remember the contrasting roles of a systems analyst (data from novice users) versus a knowledge developer (knowledge from experts). The rapid prototyping cycle (Structuring Problem β Reformulating β Structuring Task β Making Modifications β Building Task) is central to understanding KM system development. Additionally, the attributes of users (high system dependence, low ambiguity tolerance) and experts (low system dependence, high ambiguity tolerance) explain why different approaches are needed. Finally, both cycles share the fundamental structure of starting with a problem and ending with a tested solution.
π§ Quick Revision Questions
- What are the three key differences between conventional systems development and the Knowledge Management System Life Cycle (KMSLC)?
- How does the role of a systems analyst differ from the role of a knowledge developer in terms of their main interface and the type of user/expert they interact with?
- Describe the rapid prototyping cycle for KMSLC as presented in the lecture (list the steps in order).
- Compare the attributes of a "user" and an "expert" regarding their dependence on the system and their tolerance for ambiguity.
- What is the primary purpose of evaluating the existing knowledge infrastructure before developing a new KM system?
π Lecture 36 β KM System Justification and Feasibility Issues, Implementation Issues and Resistance
π Overview: This lecture addresses the critical phases of justifying, scoping, and implementing a Knowledge Management system, focusing on the practical challenges of feasibility analysis, knowledge capture, and user adoption. It provides a structured framework for evaluating whether a KM initiative is viable and outlines the key steps from team formation through post-implementation evaluation, emphasizing the human and organizational factors that determine success.
ποΈ Topics Covered
The lecture covers KM system justification through key questions about knowledge loss risk and expert availability; scoping and feasibility analysis using traditional project evaluation methods; user support requirements; strategic planning's role; forming a balanced KM team; knowledge capture methods including interviewing and rapid prototyping; expert selection criteria; the knowledge developer's role; designing the KM blueprint architecture; system testing through verification and validation; implementation and conversion; quality assurance for error types; user training classification; managing resistance to change; post-system evaluation questions; organizational implications for maintenance; and detailed factors for successful implementation including motivation, training logistics, and top management commitment.
π Lecture Summary
KM System Justification
KM system justification involves answering a series of critical questions to determine whether a system is truly needed and viable. Key questions include: whether existing knowledge will be lost through retirement, transfer, or departure; whether the system is needed in multiple locations; whether experts are available and willing to support building the system; whether the problem requires years of experience and cognitive reasoning to solve; whether the expert can articulate how the problem is solved; how critical the knowledge is; whether the tasks are non-algorithmic in nature; and whether a champion can be found within the organization.
Scoping means limiting the breadth and depth of the project within financial, human resource, and operational constraints. Feasibility study involves addressing whether the project can be completed within the expected timeframe, whether it is affordable, whether it is appropriate, and how frequently the system would be consulted and at what associated cost.
The traditional approach to feasibility study includes: forming a knowledge management team, preparing a master plan, performing cost/benefit analysis of the proposed system, and quantifying system criteria and costs.
π‘ Why this matters: Without proper justification and feasibility analysis, organizations may invest in KM systems that address the wrong problems or cannot be sustained.
User Support
User support considerations include: whether the proposed user is aware of the new KM system development and how it is perceived; how much involvement can be expected from the user during the building process; what type of user training will be needed when the system is operational; and what kind of operational support should be provided.
Role of Strategic Planning
As a consequence of evaluating the existing infrastructure, the organization should develop a strategic plan that aims at advancing the organization's objectives with the proposed KM system in mind. Areas to be considered include: vision, resources, and culture.
Forming a KM Team
Forming a KM team involves identifying key units, branches, divisions, etc., as the key stakeholders in the prospective KM system, and strategically, technically, and organizationally balancing the team size and competency.
Factors impacting team success include: quality and capability of team members (personality, experience, and communication skill), size of the team, complexity of the project, team motivation and leadership, and promising only what can be actually delivered.
Capturing Knowledge
Capturing knowledge involves extracting, analyzing, and interpreting the knowledge that a human expert uses to solve a specific problem. Explicit knowledge is typically captured in repositories from documentation and files. Tacit knowledge is captured from experts and from the organization's stored database(s).
π Definition β Knowledge Developer: In KM systems development, the knowledge developer acquires the necessary heuristic knowledge from the experts for building the appropriate knowledge base.
Interviewing is one of the most popular methods used to capture knowledge. Data mining is also useful for using intelligent agents that analyze the data warehouse and discover new findings. Knowledge capture and knowledge transfer are often carried out through teams. Knowledge capture includes determining feasibility, choosing the appropriate expert, tapping the expert's knowledge, retapping knowledge to plug gaps, and verifying/validating the knowledge base.
The Role of Rapid Prototyping
In most cases, knowledge developers use an iterative approach for capturing knowledge. For example, the knowledge developer may start with a prototype based on limited knowledge captured during the first few sessions.
The process can become rapid prototyping when: the knowledge developer explains a preliminary procedure based on rudimentary knowledge extracted from the expert; the expert reacts with remarks; while the expert watches, the knowledge developer enters additional knowledge into the computer-based prototype; and the developer runs the modified prototype and continues adding knowledge iteratively until the expert is satisfied.
π Definition β Rapid Prototyping: The spontaneous, iterative process of building a knowledge base is referred to as rapid prototyping.
Expert Selection
The expert must have excellent communication skill to be able to communicate information understandably and in sufficient detail. Common questions regarding expert selection include: how to know the so-called expert is actually an expert; whether they will stay with the project until completion; what backup is available if the expert loses interest or quits; and how the knowledge developer knows what lies within and outside the expert's area of expertise.
The Role of the Knowledge Developer
The knowledge developer can be considered the architect of the system. They identify the problem domain, capture knowledge, write and test heuristics that represent knowledge, and coordinate the entire project.
Necessary attributes of a knowledge developer include: communication skills, knowledge of knowledge capture tools/technology, ability to work in a team with professionals/experts, tolerance for ambiguity, ability to think conceptually, and ability to interact frequently with the champion, knowledge workers, and knowers in the organization.
Designing the KM Blueprint
This phase marks the beginning of designing the IT infrastructure/Knowledge Management infrastructure. The KM Blueprint (KM system design) addresses several issues, including: aiming for system interoperability/scalability with existing IT infrastructure, finalizing the scope of the proposed system, deciding about necessary system components, and developing the key layers of the KM architecture.
The key layers of KM architecture are: user interface, authentication/security layer, collaborative agents and filtering, application layer, transport internet layer, physical layer, and repositories.
Testing the KM System
Testing involves two steps: Verification Procedure ensures that the system is rightβthe programs do the task they are designed to do. Validation Procedure ensures that the system is the right systemβit meets user expectations and will be usable on demand.
Implementing the KM System
After capturing appropriate knowledge, encoding it in the knowledge base, and verifying/validating, the next task is to implement the proposed system on a server. Implementation means converting the new KM system into actual operation. Conversion is a major step in implementation, followed by post-implementation review and system maintenance.
Quality Assurance
Quality assurance indicates the development of controls to ensure a quality KM system. The types of errors to look for include: reasoning errors, ambiguity, incompleteness, and false representation.
Training Users
The level and duration of training depends on the user's knowledge level and the system's attributes. Users can range from novices (casual users with very limited knowledge) to experts (users with prior IT experience and knowledge of latest technology).
Users can also be classified as: tutors (who acquire working knowledge to keep the system current), pupils (unskilled workers trying to gain understanding of captured knowledge), or customers (interested in how to use the KM system). Training should be geared to the specific user based on capabilities, experience, and system complexity, and can be supported by user manuals, explanatory facilities, and job aids.
Managing Change
Implementation means change, and organizational members usually resist change. Resistors may include: experts, regular employees (users), troublemakers, and narrow-minded people.
Resistance can manifest as: projection (hostility towards peers), avoidance (withdrawal from the scene), or aggression.
Post System Evaluation
Key questions in the post-implementation stage include: How has the new system improved accuracy/timeliness of decision-making? Has the system caused organizational changes, and how constructive are they? Has the system affected end-user attitudes? How has the system changed business operation costs? In what ways has the system affected relationships between end users? Do the benefits justify the cost of investment?
Implications for KM
Managerial factors to consider include: the organization must commit to user training/education prior to building the system; top management should be informed with cost/benefit analysis; knowledge developers and potential knowledge engineers should be properly trained; domain experts must be recognized and rewarded; and the organization needs long-range strategic planning.
Questions regarding systems maintenance: Who will be in charge? What skills are needed? What is the best way to train the maintenance specialist? What incentives ensure quality maintenance? What types of support/funding will be required? What relationship should be established between KM system maintenance and the IT staff?
Q.1 Successful KM system implementation depends on several factors:
- Level of motivation of the user: Good documentation cannot compensate for low motivation or poor attitude. Promoting motivation must be planned in advance.
- Computer literacy and technical background: A computer-literate user is easier to work with. First-time users often require education and training.
- Communication skills of the trainer: Selling people on change is more an art than a science. Communication skills can determine user acceptance or rejection.
- Time availability and funding for training: A training program run on a shoestring is usually a loser. Training should be part of the implementation phase.
- Place of training: Off-site training offers dedicated, uninterrupted learning; on-site training saves travel costs but may suffer interruptions.
- Ease and duration of training: Depends on trainer caliber, trainee attitude, and "chemistry." A reasonable training period with measurable goals is essential.
- Ease of access and explanatory facilities: Systems should be easy to access and work with. Explanatory facilities promote ease of use and solution integrity.
- Ease of maintenance and system update: Good documentation and module-oriented design make the difference between easy maintenance and a nightmare.
- Payoff to the organization: Measurable payoff early in the development life cycle promotes successful implementation.
- Role of the champion: Solid top management support and a champion pushing for adoption can make the difference between success and lukewarm installation.
Q.2 How important are organizational factors in system implementation? The primary organizational factor is top management commitment, evident through adequate funding, ensuring hardware and personnel availability, and allowing the champion to function. The second organizational factor is user participation in the building process, which increases commitment and fosters a sense of ownership. Other factors include organizational politics (jockeying for leverage) and organizational climate. User readiness can also influence implementation success.
β Key Takeaways
The most critical concepts from this lecture are the comprehensive justification framework that evaluates knowledge loss risk, expert availability, and non-algorithmic task suitability before committing to a KM project; the distinction between verification (building the system right) and validation (building the right system) as two essential testing phases; the rapid prototyping approach as an iterative, spontaneous method for capturing tacit knowledge with active expert participation; the recognition that user resistance manifests through projection, avoidance, and aggression, requiring proactive change management; and the ten critical success factors for implementation, with top management commitment, user motivation, and a strong champion being the most decisive elements for KM system success.
π§ Quick Revision Questions
- What are the six key questions that must be answered during KM system justification?
- What is the difference between verification and validation in KM system testing?
- Describe the rapid prototyping process and how it differs from traditional knowledge capture methods.
- List and explain the three forms of personal resistance to change that may occur during KM implementation.
- Why is the role of the champion considered critical to successful KM system implementation, and what organizational factors support the champion's effectiveness?