A Look At Use Cases
We have just released some new features. The new features give you the ability to send a link to people for a Vuuch page and provide these people an ability to subscribe (join the community of people who care about the deliverable the page represents). For example here is a link for the Vuuch page for a use case presentation I shared with Ken Wong http://www.vuuch.me/collaboration/fileRepNW4/discussions/888. Navigate to the page and subscribe and you will be able to aprticipate in discussions about this presentation as well as download the presentation. Feel free to openly share this link and if you have questions about the presentation please ask.
I imagine this has stirred a number of questions. Well here are some of the ones I have heard so far:
- What if I want to constrain the subscriptions to a certain group of people? When you turn this feature on you can configure a list of domains the person must be part of in order to subscribe. For example if I wanted to constrain who could subscribe to only people from Vuuch I would configure the subscription domain to be vuuch.com. Therefore only people from this domain could subscribe.
- Can I create Vuuch activities that only a certian list of people can see? Yes absolutely. See next question.
- Is everthing on the page available to everyone? No not at all. When an item is created you decide who has access. You can open it all the way up by making it public or you can close it all the way down by defining a list of participants (like a list of participants for an email). And you can change this at anytime.
- Can I connect/relate this page to other Vuuch pages? Yes absolutely. And these related pages could be public or completely private. When you do this only those people that are involved with the related page will be able to navigate to the related page.
- So how might this functionality be used? OK you are thinking this is pretty cool but how might this functionality be used? Well here are a few examples of cases we have worked with a number of companies. See below.
Example Use Cases:
- PowerPoint Use Case (Presentation sent out to your field team):
Within the presentation a link is provided and if the sales team has an interest in asking questions about the presentation or accessing FAQ information then they can subscribe. And if they install the Vuuch for MS Office add-in they can do all this without leaving the presentation. You can imagine a sales person sitting in a Starbucks getting ready for a customer presentation and they want feedback on a certain slide. They go to the slide and type their question. Later when they are at the customer site and just before projecting they check the slide for the responses. The sales person never needs to leave the presentation as the presentation is the access point to all those who have an interest in the presentation. - Supplier of Components:
For example if you supplied motors you could create a Vuuch page for each of your motors and engage a community of people that use each motor. For example if I were searching for a motor I could go to this page and ask the community for feedback on the motor and/or get additional information about the motor. I could define issues and tasks that I would like the motor supplier to address for me. Right from this page they access a public and private community. - Green Materials:
Remember anything can be Vuuched. In this case the user is using an application for green product development, say Sustainable Minds and they are looking at different material characteristic within the application. They see a material they think might work but they are not familiar with this material. Well luck for them the material database has been Vuuched. So they link to the Vuuch page for the material they are looking at using. Here they can access additional information and ready discussions people are having. As well they can post their own questions. As well they could create private tasks for people in their organization to further investigate the material, for example maybe they ask purchasing where they could purchase the material and they ask quality to provide a review. Right from this page they access both a public and private community.
If you enjoyed this article, please consider sharing it!
I think the use case for a build incident alert is a powerful application for this technology. Typically, a production shutdown results in mass pandemonium where a ton of email is circulated, but no one person has all the information. Phone calls happen in the background, but they go undocumented and root cause can be difficult to determine.
When a problem on the manufacturing floor shuts down assembly, the potential for collaboration outside the confines of the traditional PLM could be quite powerful. Outside experts can be consulted, non-integrated vendors can be leveraged, procurement can watch the status, and the sales function can stay on top of their deliverables.
Even if the issue doesn’t shut production down, the issue is still easily documented in a format that can feed into an ECO. If the issue escalates, Vuuch makes it easy to invite additional stake holders.
Yes this is a very good use case. It is like another I recently discussed that has nothing to do with Product Development though. This case has to do with the processing of medical insurance claims. In MA about 30% of the insurance claims are disputed. When this happens there are at least three parties that are disconnected and frustrated, the doctor, the insurance company and the patient. The patient and the doctor end up casing the others around trying to find a resolution. The idea is that through Vuuch the insurance claim would get Vuuched, creating a page that brings the people, discussions, issues, actions and status together, putting everyone on the same page.
Christine I see your case very much like this. The problem would get Vuuched. This is simple using a Vuuch Placeholder page. Now everyone involved, the issues, tasks, discussions and status are on the same page. I see this also being the case for ECOs. Certainly we would not replace the formal ECO, but Vuuch would manage getting the team all on the same page with respect to processing the ECO.