The Knowledge Aware approach is a completely new technique to managing knowledge
The Knowledge Aware approach is specifically a knowledge management technology that attempts to directly manage and implement knowledge life-cycling; which is distinctly not document-centric, a PLM tool, or requirements management. There are many ways the Knowledge Aware approach is different than what is being used today. Four of the most significant capabilities the Knowledge Aware approach provides an organization are what makes it so different. These capabilities are not often shared among other comparable solutions, such as: Document-Centric knowledge Management Systems, PLM, or Requirements Management solutions.
Significant Capabilities of the Knowledge Aware Approach
- Rules Process Engine and KaaS
- Bottom Up (organic style) Knowledge Management
- Assessment Control and Knowledge in the Flow
- Knowledge Packets and Knowledge Lifecyling
The Knowledge Aware approach and PLM are fundamentally different in both intent and implementation. Two of the largest PLM using companies in the world also have enterprise-wide Knowledge Aware deployments. In fact, one of these manufacturing leaders has more Knowledge Aware users than PLM users. Global deployments at these two companies serve as evidence the Knowledge Aware approach represents a new, fundamental, and impactful capability existing beyond PLM.
Document-Centric Knowledge Management Systems (i.e. SharePoint)
The Knowledge Aware approach provides a rich feature set that allows knowledge to be collaboratively captured, refined, made actionable, and integrated directly into technical workflows in ways that efficiently influence engineering capability and outcomes. On the other hand, Document-Centric Knowledge Management Systems are highly customizable, collaborative content portals used by teams to efficiently manage and share documents and other forms of transient information. While it may be superficially attractive to use it in the pursuit of Knowledge Management, this approach has ultimately proven to be a counterproductive strategy; adding years and skepticism to most Knowledge Management efforts and making it even harder for companies to hit mission-critical objectives.
The Knowledge Aware approach was designed to manage evolving and organic learnings, knowledge, and routines. Conversely, Requirements Management was designed to manage customer requirements, software requirements, and test configurations. These two solutions are fundamentally different; having differences in intent and in implementation.