Comments on: Thingamy Thoughts http://www.smartermessaging.com/2006/04/20/thingamy-thoughts/ How do we enable smarter conversations? Wed, 07 Jan 2009 04:04:00 +0000 http://wordpress.org/?v=2.6.3 By: Luis http://www.smartermessaging.com/2006/04/20/thingamy-thoughts/#comment-436 Luis Fri, 24 Nov 2006 09:26:58 +0000 http://www.collaborationconsultant.com/2006/04/20/thingamy-thoughts/#comment-436 Thingamy is an ultimately configurable process modeler that actually runs the processes. It could be a killer app in the right hands. It could be a consultant’s swiss army knife. It is an SMB’s dream: to be able to change processes on the fly and have a framework that can facilitate, communicate, and implement new workflows across entire organizations. Thingamy is an ultimately configurable process modeler that actually runs the processes. It could be a killer app in the right hands. It could be a consultant’s swiss army knife. It is an SMB’s dream: to be able to change processes on the fly and have a framework that can facilitate, communicate, and implement new workflows across entire organizations.

]]> By: sig http://www.smartermessaging.com/2006/04/20/thingamy-thoughts/#comment-6 sig Fri, 21 Apr 2006 08:51:56 +0000 http://www.collaborationconsultant.com/2006/04/20/thingamy-thoughts/#comment-6 Mike, how can one not love this blogging thing, I mean, doing a demo and then get a full and no-nonsense report back - excellent! I've heard the issue of demo-to-end-users before, actually Thomas Otter at SAP said the exact same thing - so duly taken to heart of course! (Although I think I'll stick to you guys and let you who really are close to the front do that part if I may ;) The idea of a "Presence integration" is new - so far we have sorted that issue in a more asynchronous way, just by adding an "ad-hoc" internal communication process using a "communication object", leaving the identification to customer issue, whatever to the tags. Works, and I am a real fan of asynchronity and keeping all communication as real system objects for future history and reports (that way a "customer file" also includes internal communication whhatever ity might be, should be useful!). Loose nothing is the credo. But of course, will give it a think! E-mail integration is not new on the wish-list, and should not be a biggie! In fact it would be important to be able to flip those blasted mails into proper data-objects inside the system so they can be used side-by-side with all other data. That'll be there :) Thanks again, and am looking forward to sit down together and plonk down a end-user-demo! Mike, how can one not love this blogging thing, I mean, doing a demo and then get a full and no-nonsense report back - excellent!

I’ve heard the issue of demo-to-end-users before, actually Thomas Otter at SAP said the exact same thing - so duly taken to heart of course! (Although I think I’ll stick to you guys and let you who really are close to the front do that part if I may ;)

The idea of a “Presence integration” is new - so far we have sorted that issue in a more asynchronous way, just by adding an “ad-hoc” internal communication process using a “communication object”, leaving the identification to customer issue, whatever to the tags. Works, and I am a real fan of asynchronity and keeping all communication as real system objects for future history and reports (that way a “customer file” also includes internal communication whhatever ity might be, should be useful!). Loose nothing is the credo.
But of course, will give it a think!

E-mail integration is not new on the wish-list, and should not be a biggie! In fact it would be important to be able to flip those blasted mails into proper data-objects inside the system so they can be used side-by-side with all other data. That’ll be there :)

Thanks again, and am looking forward to sit down together and plonk down a end-user-demo!

]]>