CODIFICATION OF KNOWLEDGE IN BUSINESS PROCESS IMPROVEMENT PROJECTS

In times of globalization, new technologies and high market transparency, companies search for ways to raise the efficiency of their business processes and achieve long-term customer relationships. Therefore enterprises are strongly devoted to business process improvement (BPI) initiatives. However, in times of globally spanning inter-organizational business processes, conducting BPI initiatives is particularly challenging du to the necessary diverse and distributed knowledge. Successful BPI projects require the participation of a variety of employees who are directly involved in a business process. The employees have tacit process knowledge that needs to be transformed into explicit knowledge to derive improvement opportunities in a BPI project. To reach this, a set of easy to understand and well-structured BPI techniqus is required to encourage employees to participate in corresponding initiatives. Further, the codification of the results gained in such initiatives is decisive to enable their proper documentation, communication and processing. \ \ The paper at hand introduces a BPI roadmap for coordinating the structured use of BPI techniqus in a project. The roadmap is based upon a set of formal conceptual model types for codifying the results generated by each techniqu. In addition, reports are specified that process the model information and facilitate the communication and documentation of the results. The presented approach thus contributes to the systematic transformation of employees´ tacit process knowledge to explicit knowledge in the course of BPI initiatives. By applying the roadmap in a use case, its benefits for BPI initiatives are illustrated.

Building dynamic capabilities through operations strategy: an empirical example

This paper suggests that the implementation of an effective operations strategy process is one of the necessary antecedents to the development of dynamic capabilities within an organisation and that once established, dynamic capabilities and operations strategy process settle into a symbiotic relationship. Key terms and a model of operations strategy process are proposed from literature as a framework for analysing data from a longitudinal case study with a UK based manufacturer of construction materials

Practitioner requirements for integrated Knowledge-Based Engineering in Product Lifecycle Management.

The effective management of knowledge as capital is considered essential to the success of engineering product/service systems. As Knowledge Management (KM) and Product Lifecycle Management (PLM) practice gain industrial adoption, the question of functional overlaps between both the approaches becomes evident. This article explores the interoperability between PLM and Knowledge-Based Engineering (KBE) as a strategy for engineering KM. The opinion of key KBE/PLM practitioners are systematically captured and analysed. A set of ranked business functionalities to be fulfiled by the KBE/PLM systems integration is elicited. The article provides insights for the researchers and the practitioners playing both the user and development roles on the future needs for knowledge systems based on PLM

Lessons learned: structuring knowledge codification and abstraction to provide meaningful information for learning

Purpose – To increase the spread and reuse of lessons learned (LLs), the purpose of this paper is to develop a standardised information structure to facilitate concise capture of the critical elements needed to engage secondary learners and help them apply lessons to their contexts. Design/methodology/approach – Three workshops with industry practitioners, an analysis of over 60 actual lessons from private and public sector organisations and seven practitioner interviews provided evidence of actual practice. Design science was used to develop a repeatable/consistent information model of LL content/structure. Workshop analysis and theory provided the coding template. Situation theory and normative analysis were used to define the knowledge and rule logic to standardise fields. Findings – Comparing evidence from practice against theoretical prescriptions in the literature highlighted important enhancements to the standard LL model. These were a consistent/concise rule and context structure, appropriate emotional language, reuse and control criteria to ensure lessons were transferrable and reusable in new situations. Research limitations/implications – Findings are based on a limited sample. Long-term benefits of standardisation and use need further research. A larger sample/longitudinal usage study is planned. Practical implications – The implementation of the LL structure was well-received in one government user site and other industry user sites are pending. Practitioners validated the design logic for improving capture and reuse of lessons to render themeasily translatable to a new learner’s context. Originality/value – The new LL structure is uniquely grounded in user needs, developed from existing best practice and is an original application of normative and situation theory to provide consistent rule logic for context/content structure

The Need of Knowledge Management Strategy for the Successfully Implementation of Reengineering Projects

This paper want to shown that current knowledge management approaches do not emphasise enough on knowledge sharing from reengineering project perspective. To achieve success with reengineering project, an organisation must possess and share knowledge about many different facets of this process. While many reengineering projects have resulted in improve performance, we believe that higher levels of performance improvement are possible by coupling IT capabilities with KM strategy. To explain these results it was assumed that the key to implementing with success reengineering project is having a wide knowledge management strategy. Our objective for the paper reported here was to understand the factors that motivate to share knowledge before implementing any knowledge management strategy to sustain the successfully implementation of reengineering projects.Information Technologies, knowledge, knowledge management, strategy, reengineering, project

Approach to Identify Internal Best Practices in a Software Organization.

Current approaches to software process improvements (SPI) in software organizations is based on identifying gaps by comparing the way organizations work with respect to practices contained in the reference models. Later, these gaps will be targeted for establishing software process improvements. This paper presents an approach for identifying best practices within the organization. This is considered a key element in order to compare the way software organizations work with the reference models. After that, these practices will be complemented with practices contained in these models depending on the organization's business goals