<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Discussion on: What are the most desired features in IT Process Orchestration (e.g. RBA)?</title>
	<link>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/</link>
	<description></description>
	<pubDate>Fri, 22 Aug 2008 05:39:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.1</generator>

	<item>
		<title>By: Ryan Shopp</title>
		<link>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-99</link>
		<author>Ryan Shopp</author>
		<pubDate>Tue, 05 Feb 2008 15:48:54 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-99</guid>
		<description>Great feedback and input.  Vendors are always welcome.  This blog is an open opportunity to get your thoughts out there and differentiators heard etc.  So please, never be shy.  Just write away.

As for your key feature.  If I'm hearing you correctly is having a connector "studio" versus simply having a SDK (API, Documentation &#38; Examples).  I completely agree, any way you can automate a process, saving time and making it easier is fantastic.

I would encourage also having the SDK/API since some complicated interactions may not work (or be an option) through a recording process (also, even through more complicated, some people just prefer scripting).  Another thing this made me wonder is do you offer a community where your customers can share these "connectors" they build?  Do any IT Process Orchestration vendors offer this?</description>
		<content:encoded><![CDATA[<p>Great feedback and input.  Vendors are always welcome.  This blog is an open opportunity to get your thoughts out there and differentiators heard etc.  So please, never be shy.  Just write away.</p>
<p>As for your key feature.  If I&#8217;m hearing you correctly is having a connector &#8220;studio&#8221; versus simply having a SDK (API, Documentation &amp; Examples).  I completely agree, any way you can automate a process, saving time and making it easier is fantastic.</p>
<p>I would encourage also having the SDK/API since some complicated interactions may not work (or be an option) through a recording process (also, even through more complicated, some people just prefer scripting).  Another thing this made me wonder is do you offer a community where your customers can share these &#8220;connectors&#8221; they build?  Do any IT Process Orchestration vendors offer this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aveitch</title>
		<link>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-98</link>
		<author>Aveitch</author>
		<pubDate>Mon, 04 Feb 2008 14:22:16 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-98</guid>
		<description>Another vendor comment I'm afraid (Scapa Technologies). We've found that the big challenge in this space is to integrate with the vast number of products that are installed, particularly problematic are the legacy, home-grown applications and infrastructure. Taking the approach of writing an integration module for all of these systems would be impossible but if you can't integrate easily with the systems that you are automating then you are back to scripting.

Our solution (and my vote for a required feature) is capture/replay, ideally both for the Windows GUI and http. It's a really useful tool to have the in box when you need to integrate with something unusual. It also has the benefit for helpdesks or diagnostics that by going through the same UI a human would use, the automation will experience exactly the same behavior that customers are seeing avoiding the problem that an API will behave differently to a user interface in some cases.</description>
		<content:encoded><![CDATA[<p>Another vendor comment I&#8217;m afraid (Scapa Technologies). We&#8217;ve found that the big challenge in this space is to integrate with the vast number of products that are installed, particularly problematic are the legacy, home-grown applications and infrastructure. Taking the approach of writing an integration module for all of these systems would be impossible but if you can&#8217;t integrate easily with the systems that you are automating then you are back to scripting.</p>
<p>Our solution (and my vote for a required feature) is capture/replay, ideally both for the Windows GUI and http. It&#8217;s a really useful tool to have the in box when you need to integrate with something unusual. It also has the benefit for helpdesks or diagnostics that by going through the same UI a human would use, the automation will experience exactly the same behavior that customers are seeing avoiding the problem that an API will behave differently to a user interface in some cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Month in Review - January 2008 - Adventures in Data Center Automation</title>
		<link>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-92</link>
		<author>Month in Review - January 2008 - Adventures in Data Center Automation</author>
		<pubDate>Thu, 31 Jan 2008 17:05:27 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-92</guid>
		<description>[...] What are the most desired features in IT Process Orchestration (e.g., RBA) - discussion on key features [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] What are the most desired features in IT Process Orchestration (e.g., RBA) - discussion on key features [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Shopp</title>
		<link>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-88</link>
		<author>Ryan Shopp</author>
		<pubDate>Thu, 31 Jan 2008 16:50:07 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-88</guid>
		<description>Thanks, great feedback and insight!  Any customers out there using these products that could give us their perspective on which of these were the most important in their decision.</description>
		<content:encoded><![CDATA[<p>Thanks, great feedback and insight!  Any customers out there using these products that could give us their perspective on which of these were the most important in their decision.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ccrouchman</title>
		<link>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-86</link>
		<author>Ccrouchman</author>
		<pubDate>Wed, 23 Jan 2008 02:12:10 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/data-center-automation/what-are-the-most-desired-features-in-process-orchestration-eg-rba/#comment-86</guid>
		<description>First my own disclosure.  I am the CTO for one of the IT Process Automation Vendors listed above (Opalis) so please take my comments as being skewed to my particular view of the universe.  Having said that I believe that these attributes are broad market needs, not just shameless self promotion of my product (I leave that to the Marketing folks).

First I'll add a few more attributes that I think are important.

1. A set of out of the box integrations with infrastructure and management products that is both deep (i.e. engineered, not scripted) and broad (i.e. support for most tools you have in your environment from multiple vendors).
2. An integrated data bus for passing information within the workflow (eg. using the attributes entered in a Remedy form as parameters for provisioning a virtual machine) that doesn't require scripted variable substitution.
3. Integrated rules-based decision making capabilities that (guess what comes next) doesn't require scripting.

Without these things you'll find that in order to make the product work in your unique environment you'll be writing a lot of scripts, which is what you're supposed to be eliminating with these tools.

I'd also alter your statement about out of the box processes from "more is better" to "make sure that the vendor offers a broad and deep library of high value processes that solve real world problems".  In this area while quantity matters, quality matters more (do you really need 50 variants of "open a help desk ticket based on an alert"?).

Thanks for writing this blog.  I enjoy it very much.</description>
		<content:encoded><![CDATA[<p>First my own disclosure.  I am the CTO for one of the IT Process Automation Vendors listed above (Opalis) so please take my comments as being skewed to my particular view of the universe.  Having said that I believe that these attributes are broad market needs, not just shameless self promotion of my product (I leave that to the Marketing folks).</p>
<p>First I&#8217;ll add a few more attributes that I think are important.</p>
<p>1. A set of out of the box integrations with infrastructure and management products that is both deep (i.e. engineered, not scripted) and broad (i.e. support for most tools you have in your environment from multiple vendors).<br />
2. An integrated data bus for passing information within the workflow (eg. using the attributes entered in a Remedy form as parameters for provisioning a virtual machine) that doesn&#8217;t require scripted variable substitution.<br />
3. Integrated rules-based decision making capabilities that (guess what comes next) doesn&#8217;t require scripting.</p>
<p>Without these things you&#8217;ll find that in order to make the product work in your unique environment you&#8217;ll be writing a lot of scripts, which is what you&#8217;re supposed to be eliminating with these tools.</p>
<p>I&#8217;d also alter your statement about out of the box processes from &#8220;more is better&#8221; to &#8220;make sure that the vendor offers a broad and deep library of high value processes that solve real world problems&#8221;.  In this area while quantity matters, quality matters more (do you really need 50 variants of &#8220;open a help desk ticket based on an alert&#8221;?).</p>
<p>Thanks for writing this blog.  I enjoy it very much.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
