A blog by Oleg Shilovitsky
Information & Comments about Engineering and Manufacturing Software

Google Wave in Design and Process Collaboration

Google Wave in Design and Process Collaboration
olegshilovitsky
olegshilovitsky
9 November, 2009 | 2 min for reading

Picture 40In the past, I had chance to write about Google Wave (GW). Lots of interest coming around everything related to Google Wave. You can read some of my previous posts about Google Wave to get up to speed with my way to think about Google Wave.

Google Wave – Is it the Next Collaborative Process Engine for PLM?
6 reasons Why Google Wave will Change PLM Collaboration

So, the following interesting project from SAP drove my attention during the weekend, so I decided to share my thoughts about SAP Gravity project. However, before, take a look on video produced by SAP.

[youtube=http://www.youtube.com/watch?v=FaNhXPSCQWo]

From the earlier beginning of Google Wave, it was clear that we could expect an impact of Google Wave on the enterprise software world. Despite the fact enterprises are using a big amount of unique and valuable enterprise systems, all of them are heavily relying on email to collaborate. Therefore, GW offering updated email collaboration paradigm will become an attractive guest in enterprise eco-system.

You can read more about Google Wave SAP Web 2.0 Blog.

So, what are my thoughts about Google Wave in the context of SAP demo project? I have to say that I’m experimenting with Google Wave too and my thoughts, of course, affected by my own experience with Google Wave.

Pros:
1. Collaboration between the unstructured communication world and structured business process definition is notable
2. Google Wave integration capabilities
3. Very powerful history representation
3. There is a huge potential for additional developments – Gadgets and Robots

Cons:
1. Keep of track of all your Waves is as complicated as emails- no big surprise in this space.
2. The way Google Wave will manage store of integrated information is not clear (i.e. BPMN for SAP Gravity, but future thinking about 3D models etc.)
3. Wave to Wave merges and communication can create additional complexity.

What is the future perspective for Google Wave in PLM space in my view? The most perspective direction is collaboration around 3D and other design-related situational collaboration. This is space that today occupied by mail. This is not an empty space – innovative products like 3DLive as well as other CAD / Viewers -related products are also targeting this space. However, I see a potential to embed live 3D model or drawing into Wave and provide an ability to participants to collaborate, similar to how BPMN process was created by SAP Gravity.

I would be interested to hear your opinion and thoughts.
Best, Oleg

Recent Posts

Also on BeyondPLM

4 6
14 July, 2009

Short update. Since last month I’m contributing to Dassault Systems 3D Perspectives Blog. Actually, I discovered that PLM Think Tank...

24 August, 2018

I’m taking some time off with my family, so please excuse me for irregular blogging this week. My attention was...

13 August, 2023

New product development is an essential part of innovation. Every day, engineering and manufacturing organizations across the world are challenged...

30 November, 2024

I started my blogging journey back in 2008. In those days, there was huge excitement about the capabilities of platforms...

6 August, 2013

There are variety definitions of what is PLM. Not much agreement about that among PLM vendors, PLM analysts and manufacturing companies....

23 October, 2019

The new came online just a few hours ago about PTC is entering the agreement to acquire Onshape. The PTC...

14 July, 2015

Back to my trip to Develop3D Live conference earlier this year, I shared my thoughts about future of cloud competition....

8 June, 2019

Earlier this week, I had a privilege to present at IDE 2019 Summer School. The topic Beyond Transformation and Digital...

18 June, 2015

Enterprise integration is a messy space. It is always complex – applications, databases, new and legacy systems, complexity of requirements....

Blogroll

To the top