Visual WIKI – is it next step in collaborative product development?

I’d like to come to raise the idea of visual WIKI. This is a possible way to make PLM more collaborative and more adaptable for users’ needs. In today’s world, PLM companies are struggling about how to deliver PLM implementation quickly and at a low cost. The traditional way – providing out-of-the-box has brought some success over the past few years. It has allowed customers who agree about the common business practice of PLM deployment to benefit from this out-of-the-box deployment. At the same time, I think the problem still remains. Although many customers are ready to start with out-of-the-box, they have additional requirements that are hard to recognize before implementation. Also, these requirements might be very unique and require customization. Normally, these customizations are done by service providers or implemented by customers.

 Getting back to the “visual wiki” idea: The core of the wiki idea is to provide technology that will make a collection of Web pages be able to have multiple participants co-edit its content. Wiki developed the WYSIWYG concept for interactive content editing. I really like it in context of Product Lifecycle Management. PLM products can allow users to create structured Wiki pages using the content of the products they are developing. In addition, we can intensively use 3D content on these pages with various lightweight 3D format representations – 3D PDF, 3DXML, JT Open, etc.

 The next powerful capability we can create is tracking and controlling changes. Since Wiki is shared content with controlled user access, we can allow particular users to create content (i.e. designers and engineers) and allow others authorization to review only. Also, since a Wiki page can aggregate content about products during their development, this page can be used to track the development maturity used by potential customers to review product capabilities, and also centralize information about potential customer claims and support requests.

 To sum up: I see Wiki as a powerful content aggregation tool  allowing collaborative access by multiple users from organizations involved in product development , and consumers as well. Wiki can also develop consumer communities around this content. There are many Wiki software options available. I will say that most of these products and technologies can be reused for PLM products. The ability wiki to adapt content to a specific customer’s need will resolve heavy customization issues in current out-of-the-box software offering.



Share This Post

  • We have been using PB wiki and it has been helping us to build and storage knowledge in a collaborative way.

  • Victor, thank you for comments! What type of knowledge you accumulate in PBW? Did you have system for this purpose before PBW? Thanks. Oleg.

  • The wiki in PLM is right on target. Design / Product Development is a free form process of innovation and discovery and therefore fixed or rigid systems do not do well until there is a need to lock down and control things. I did 20 months of research on the concpet of using a wiki in design. Our concept was called Product DynamiX, PDX. The problem with a generic wiki is there is very little structure so the users must create a structure or taxonomy. What is required to make this work is a wiki that understand the object. For example imagine a wiki that understood what a “part” was…

  • Your last two post, wiki and rss fit together. Imagine a wiki page that represented a part and imagine if a CAD file that represented this part could express a 3D view on to the page. This would be very cool, but what would be WAY COOL is if the CAD file was not managed. Imagine if you could navigate to the “Part” page and see all discussions that are going on about this part or all discussions that went on 2 years ago about this part…

  • chris, I’ve seen many usage of wiki in the area of knowledge sharing. This is not much different from design, I think. What was outcome of you PDX?

    about RSS and WIKI: yes, they fit together because WIKI can provide content and RSS notification and communication. But CAD files are still managed… question how long? but, in my view this is the same point in vuuch – identification of file can potentially be show-stopper to follow discussion.

  • chris, did you make a try to work with formats like 3DXML, JT Open and others in your PDX research?

  • Pingback: Use Wiki for PLM Change Management – revised! « Daily PLM Think Tank Blog()

  • In order to earn cash from paid writing jobs, adopt any of the following options since they are
    quick, easy ways to make money through content
    writing. Their perspectives and point of views are of a
    priority in the blogosphere. Transcribing audio files can
    make money online for you based upon on the number of audio files transcribed.