Designing Roles and Smart Organizations
October 26, 2009
Roles is a key concept in social and organizational studies and is a hot topic in these application areas; Enterprise Role Management (ERM), Role Engineering Assessment (REA), Role Life-cycle Management (RLM), Social Networking for Business, Business Process Management (BPM), Enterprise Resource Planning (ERP), and Holistic Design of Active Knowledge Architectures. The definition of identity, authentication, authorization, accessibility, and traceability are security needs driving this growing interest.
In most IT applications authorization is isolated from the tasks, the enabling methods and data. Roles and role-specific workplaces with tasks and views, are not supported. Coherence, coordination and collaboration are poorly supported. Workplaces are programmed and can not be designed in context-rich workspaces. Roles operate in workspaces created by work-centric and situated knowledge.
In this post we therefore look at the benefits of designing roles in context-rich workspaces. How structured roles and work-centric knowledge form the basis for a new form of smart organization. A smart organization of service-teams must be able to design and engineer roles and workspaces as projects evolve to capture practical rules and methods. Agile project teams with clear responsibilities and rules for providing services to each other should be designed as part of project design. Read the rest of this entry »
Realizing Enterprise Knowledge Management
September 16, 2009
Knowledge Management (KM) ranked high on corporate manager agendas in the early 1990s, but KM rapidly became a confusing term that managers scorned. KM systems never delivered what IT providers promised. However, some advanced information management methods were invented, and enterprise portals were developed.
Web 2.0 and Enterprise 2.0 technologies are providing new means for social networking and sharing of personal and public knowledge. However, the core situated and work-centric enterprise knowledge can not yet be expressed, shared and managed by these technologies.
Managing work-centric and situated enterprise knowledge demands fundamental rethinking of not only the nature of enterprise knowledge, but also the practical approach to realizing knowledge management. Knowledge workers must be equipped with services to manage personal as well as role-specific knowledge. Practitioners must be empowered to react to operational events, and become responsible for their own actions, data, workspaces and work plans. Personal competence and skill profiles must match the roles the person is authorized to perform.
This post looks at how knowledge management can be implemented across projects, stages, systems and disciplines, and lifecycles, using active knowledge architectures to update and configure workspaces of work-centric and situated knowledge. Read the rest of this entry »
The Nature of Enterprise Knowledge
August 26, 2009
In the 1990s most leading companies were very much concerned about knowledge management, recognizing that knowledge and competence are the driving forces of business, design and innovation. Industrial managers were also concerned about brain drain, loss of practical competence when skilled workers with multiple job experiences retired or left to join competitors.
This post is an attempt to revitalize industrial interest in KM by introducing new concepts and discoveries, such as knowledge architectures and families, and by giving good answers to industry questions like:
- What is enterprise knowledge?
- What inherent properties does enterprise knowledge exhibit, and what capabilities does it provide?
- How is enterprise knowledge best expressed, shared and managed by industrial users?
- How is work-centric knowledge best encoded to meet industrial needs?
The questions are answered based on scientific discoveries and experiences from industrial pilots. Read the rest of this entry »
Project Design – Mastering Complexity and Change
July 6, 2009
Large projects are complex, involving multiple products, disciplines, methodologies, techniques, systems and stakeholders. They often fail to meet expectations, schedules and budgets, and results are often poorly validated and managed. Current IT support to project definition, planning, execution and management is fragmented and rigid. Lifecycle data exchange is transformative rather than evolutionary. Innovation is not driven by evolution, embedding experiences and lessons-learned. There are many uncertainties and unknown dependencies in the early phases, many nonproductive meetings, stove-piped and sequential information flows, poor data management, and limited knowledge sharing. Collaborative design, cross-functional team working, and service composition are inhibited. Work environments and user interfaces are rigid and discipline-specific.
This post raises the questions: Are we wrongly trying to generalize and program creative work, collaborative and adaptive environments, and human behavior? Are we doing right to standardize properties, embedding their parameters and values in code? Can this approach serve complex customers with dynamic demands for controlling dependencies, supporting innovation, and automating adaptation? Read the rest of this entry »
Why is Industry Dissatisfied with PLM?
March 26, 2009
Product Life-cycle Management (PLM) systems have been developed and implemented since the early 1990s. Early solutions were based on a chain of application systems with proprietary user interfaces, information logistics and databases. At the turn of the century product data management standards, protocols and meta-data for application integration matured. Knowledge Based Engineering (KBE), process and collaboration capabilities were introduced. Ten years later customers are still not satisfied with the capabilities offered and value delivered by current solutions. Read the rest of this entry »