Google has finally arrived into the Enterprise space with their Enterprise BPM offering called Noodle (named after process spaghetti!). They have silently put together their technology and shaped them beautifully into what we have been missing “in one single platform” for a long time. Here’s a sneak-peek at what they have unleashed out of the blue…
Process discovery: With Google’s powerful presence in the email & productivity space, combined with the strong tagging and pattern recognition technology, there’s finally a way to auto discover the spaghetti of processes. It uses the groups and aliases given to all the people and tracks down the frequently used labels and combines with who connected with whom most often, to come up with this. There’s also a way to search and filter the communications to trim off the garbage from this spaghetti.
Collaborative Modeling: Now, here’s a blessing. With a cool collaborative technology using the behind the scene syncing technology around Google docs, and a simple drag & drop and tagging interface, you have a collaborative process modeling environment. There’s obviously no match for “all-attend-in-person” process workshop, but there’s so much that happens after you’re out of that “workshop zone” that brings you back to the real world reality. And ability to remotely collaborate over process model is something that is indeed a blessing.
On the Cloud: Google is on the cloud, your process models will be on the cloud, your processes would execute from the cloud. Unless you have outsourced the process participants’ jobs too, people remain in-house with you.
BPM and ACM, meet each other: A process model designed and deployed through the modeler, process executes through emails, messaging, and the engine that keeps track of a “fixed” and “variable” parts of the process. You obviously cannot do it without detaching the models from the hard definition and single-model-across-instances approach. It works, here, similar to what happens to a Google Doc in a shared mode – while you’re viewing a doc on the cloud it remains the same copy for all. The moment you edit it and make it private for you, it creates a separate process instance so to say – in process world still visible for monitoring and process participation to others. What’s more, you can define which roles can “actually” edit and make the process better. While kicking off a new case/process, one can pick among their favorites. You can like and favorite the process designs you prefer for your group/instance! So, here’s to the process continuum that travels between structured and unstructured without having to pick a separate isolated tool set!
On Mobile: With the Android Apps and (I don’t still know how they did it being two completely disparate organizations even within google) by prebuilding an interface that every Android phone understands natively with Google App Engine, your processes can execute seamlessly from any handset that is powered by Android. It’s also beautiful to know that you can still keep the process going by a single click on the “go ahead” while filling out the detailed forms in parallel. The next participant gets a preview of the task up in their bin while they can wait for the previous form submission from previous participant. Cool!
Social, what social? When you do the collaborative modeling & execution and enable people to participate and subscribe in processes, and you have Android interfaces for capturing the relevant tags and kicking off the process instances, say in customer service; you’re already doing social, aren’t you! Then, you have cool stuff of liking, favoriting and sharing the process templates, Cool!
And there’s a bunch more in sneak-view with google’s marketplace and App Engine based approach that offers the potential to keep expanding the capability without having to fight around whether it is BPM or ACM or Social or mobile or even on cloud or not. Business happens!