<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How Product Models Determine Business Process Models</title>
	<atom:link href="http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/feed/" rel="self" type="application/rss+xml" />
	<link>http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/</link>
	<description>Architect Your Business</description>
	<lastBuildDate>Fri, 03 Feb 2012 12:44:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: eTOM Operation Process Pattern &#171; Astimen&#39;s Blog of KM Telecom</title>
		<link>http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/#comment-239</link>
		<dc:creator><![CDATA[eTOM Operation Process Pattern &#171; Astimen&#39;s Blog of KM Telecom]]></dc:creator>
		<pubDate>Tue, 20 Apr 2010 07:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://activeknowledgemodeling.com/?p=253#comment-239</guid>
		<description><![CDATA[[...] leave a comment &#187;  eTOM has three standard processes level for mapping &#8220;what should we do&#8221; in telecom business process approach and decompose third level to specific enterprise&#8217;s activities in fourth level&#8221;. We can create appropriate SOPs with third level before decomposing it into fourth level as staff&#8217;s activities or tasks and fifth level deal with specific tools, resources and IT&#8217;s. Each area of eTOM processes such of Strategic (SIP), Operations (OFAB) and Enterprise Management have their own generic pattern for custom mandatory third level processes form implemented one in real OSS&#8217;s field.    Generic Pattern for Problem Report &amp; Resolution are Create, Analyse, Fix and Close with Track &amp; Manage and Report running continuously. Strategy &amp; Commit&#8217;s pattern consist of Research, Strategy, Business Plan, Operational Support, Partnership and Commit. Order&#8217;s pattern consist of Create Order, Closure with Track &amp; Manage and Report run continuously. Product life cycle&#8217;s pattern consist of Research, Development, and Retirement. Other third level eTOM Processes can be added appropriately as mandatory element of decided stream process agreed in first level with KPIs of Enterprises Business Strategy.   Read SLA Management L3 Process Pattern at Google Book &#8230; Download Enterprise Process Pattern Application by Oscar Baros &#8230; Dowload Basic Knowledge&#8217;s Keyword of eTOM and SID Workshop &#8230; Read Full Comments of eTOM 3rd Level Processes in single XLS File &#8230; How Product Determine Process Model &#8230; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] leave a comment &raquo;  eTOM has three standard processes level for mapping &#8220;what should we do&#8221; in telecom business process approach and decompose third level to specific enterprise&#8217;s activities in fourth level&#8221;. We can create appropriate SOPs with third level before decomposing it into fourth level as staff&#8217;s activities or tasks and fifth level deal with specific tools, resources and IT&#8217;s. Each area of eTOM processes such of Strategic (SIP), Operations (OFAB) and Enterprise Management have their own generic pattern for custom mandatory third level processes form implemented one in real OSS&#8217;s field.    Generic Pattern for Problem Report &amp; Resolution are Create, Analyse, Fix and Close with Track &amp; Manage and Report running continuously. Strategy &amp; Commit&#8217;s pattern consist of Research, Strategy, Business Plan, Operational Support, Partnership and Commit. Order&#8217;s pattern consist of Create Order, Closure with Track &amp; Manage and Report run continuously. Product life cycle&#8217;s pattern consist of Research, Development, and Retirement. Other third level eTOM Processes can be added appropriately as mandatory element of decided stream process agreed in first level with KPIs of Enterprises Business Strategy.   Read SLA Management L3 Process Pattern at Google Book &#8230; Download Enterprise Process Pattern Application by Oscar Baros &#8230; Dowload Basic Knowledge&#8217;s Keyword of eTOM and SID Workshop &#8230; Read Full Comments of eTOM 3rd Level Processes in single XLS File &#8230; How Product Determine Process Model &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Product Lifecycle Management in the Telecommunications Industry: A Critical Perspective for Survival and Success &#171; Astimen&#39;s Blog of KM Telecom</title>
		<link>http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/#comment-238</link>
		<dc:creator><![CDATA[Product Lifecycle Management in the Telecommunications Industry: A Critical Perspective for Survival and Success &#171; Astimen&#39;s Blog of KM Telecom]]></dc:creator>
		<pubDate>Tue, 20 Apr 2010 07:07:06 +0000</pubDate>
		<guid isPermaLink="false">http://activeknowledgemodeling.com/?p=253#comment-238</guid>
		<description><![CDATA[[...] Read pdf more &#8230; Read Link : How Product Models Determine Business Process Models &#8230; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Read pdf more &#8230; Read Link : How Product Models Determine Business Process Models &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Business-Driven SOA – Reference Models and Standards &#171; Active Knowledge Modeling</title>
		<link>http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/#comment-89</link>
		<dc:creator><![CDATA[Business-Driven SOA – Reference Models and Standards &#171; Active Knowledge Modeling]]></dc:creator>
		<pubDate>Wed, 09 Dec 2009 15:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://activeknowledgemodeling.com/?p=253#comment-89</guid>
		<description><![CDATA[[...] process modeling is neither reconfigurable nor event-driven. Processes should be combined with product models and other knowledge dimensions in order to capture the rich context and all the interdependencies [...]]]></description>
		<content:encoded><![CDATA[<p>[...] process modeling is neither reconfigurable nor event-driven. Processes should be combined with product models and other knowledge dimensions in order to capture the rich context and all the interdependencies [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Modeling &#8211; What we have learned and what we have not &#171; Active Knowledge Modeling</title>
		<link>http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/#comment-78</link>
		<dc:creator><![CDATA[Enterprise Modeling &#8211; What we have learned and what we have not &#171; Active Knowledge Modeling]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 07:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://activeknowledgemodeling.com/?p=253#comment-78</guid>
		<description><![CDATA[[...] Product design and engineering, manufacturing [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Product design and engineering, manufacturing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: astimen</title>
		<link>http://activeknowledgemodeling.com/2009/06/19/how-product-models-determine-business-process-models/#comment-65</link>
		<dc:creator><![CDATA[astimen]]></dc:creator>
		<pubDate>Mon, 02 Nov 2009 04:33:01 +0000</pubDate>
		<guid isPermaLink="false">http://activeknowledgemodeling.com/?p=253#comment-65</guid>
		<description><![CDATA[Great post, thanks for adding our reference for telecom business process knowledge integration research.  Please visit http://astimen.wordpress.com/]]></description>
		<content:encoded><![CDATA[<p>Great post, thanks for adding our reference for telecom business process knowledge integration research.  Please visit <a href="http://astimen.wordpress.com/" rel="nofollow">http://astimen.wordpress.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

