<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Market Insight Group &#187; semantic web</title>
	<atom:link href="http://marketinsightgroup.com/tag/semantic-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://marketinsightgroup.com</link>
	<description>Enabling the Future</description>
	<lastBuildDate>Fri, 30 Apr 2010 19:40:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Bridging the Divides</title>
		<link>http://marketinsightgroup.com/2009/08/bridging-the-divides/</link>
		<comments>http://marketinsightgroup.com/2009/08/bridging-the-divides/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 20:06:37 +0000</pubDate>
		<dc:creator>Barry Rabkin</dc:creator>
				<category><![CDATA[Analytics]]></category>
		<category><![CDATA[Digital Marketplace]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[document management]]></category>
		<category><![CDATA[Information]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[Operational Data]]></category>
		<category><![CDATA[semantic web]]></category>
		<category><![CDATA[Structured Data]]></category>
		<category><![CDATA[Unstructured Data]]></category>

		<guid isPermaLink="false">http://insurancetechnologyanalyst.wordpress.com/2009/08/24/bridging-the-divides/</guid>
		<description><![CDATA[<p>It doesn&#8217;t seem that long ago that I thought the &#8220;great divide&#8221; insurers faced was bridging operations and information. Operations &#8211; policy administration, billing, claims, producer onboarding and compensation, reinsurance and so forth - kept the business going while information extracted from those functional processes and other sources fueled decisions.</p>
<p>Oh for the good old days.</p>
<p>We really haven&#8217;t solved the operational / informational divide but the rapidly emerging Digital Marketplace has uncovered a divide that had always existed but has now taken on more urgency: the divide between structured data and unstructured data.</p>
<p><strong>Structured &amp; Unstructured Data</strong></p>
<p>Structured data we know and sometimes love: numbers, spreadsheets, databases, &#8230; But unstructured data is all around us in the insurance value chains including but certainly not limited to:</p>
<ul>
<li> E-mails from external stakeholders (I&#8217;m referring to policyholders, prospects, producers, regulators and reinsurers) to insurance company personnel</li>
<li>E-mails within the value chains of the insurance company (from one or more employees to other employees)</li>
<li>Phone calls within and between stakeholders whether internally or externally or some combination</li>
<li>Policy application forms in some state of completeness</li>
<li>Product development forms</li>
<li>Claim adjuster forms </li>
<li>Claim adjuster pictures or videos</li>
<li>Instant messages</li>
<li>Tweets (yes, tweets within and between stakeholders)</li>
<li>And, well you get the idea.</li>
</ul>
<p>This divide must be solved sooner than later. And the solutions rests with understanding the importance of investing in capabilities that enable the insurance company to mix, merge or otherwise blend, and access structured and unstructured data into one coherent data repository &#8230; and, of course, be able to visualize the results of the queries in a way that leads to effective and efficient decision-making.</p>
<p>What is your insurance company doing to bridge the structured / unstructured data gap?</p>
]]></description>
			<content:encoded><![CDATA[<p>It doesn&#8217;t seem that long ago that I thought the &#8220;great divide&#8221; insurers faced was bridging operations and information. Operations &#8211; policy administration, billing, claims, producer onboarding and compensation, reinsurance and so forth - kept the business going while information extracted from those functional processes and other sources fueled decisions.</p>
<p>Oh for the good old days.</p>
<p>We really haven&#8217;t solved the operational / informational divide but the rapidly emerging Digital Marketplace has uncovered a divide that had always existed but has now taken on more urgency: the divide between structured data and unstructured data.</p>
<p><strong>Structured &amp; Unstructured Data</strong></p>
<p>Structured data we know and sometimes love: numbers, spreadsheets, databases, &#8230; But unstructured data is all around us in the insurance value chains including but certainly not limited to:</p>
<ul>
<li> E-mails from external stakeholders (I&#8217;m referring to policyholders, prospects, producers, regulators and reinsurers) to insurance company personnel</li>
<li>E-mails within the value chains of the insurance company (from one or more employees to other employees)</li>
<li>Phone calls within and between stakeholders whether internally or externally or some combination</li>
<li>Policy application forms in some state of completeness</li>
<li>Product development forms</li>
<li>Claim adjuster forms </li>
<li>Claim adjuster pictures or videos</li>
<li>Instant messages</li>
<li>Tweets (yes, tweets within and between stakeholders)</li>
<li>And, well you get the idea.</li>
</ul>
<p>This divide must be solved sooner than later. And the solutions rests with understanding the importance of investing in capabilities that enable the insurance company to mix, merge or otherwise blend, and access structured and unstructured data into one coherent data repository &#8230; and, of course, be able to visualize the results of the queries in a way that leads to effective and efficient decision-making.</p>
<p>What is your insurance company doing to bridge the structured / unstructured data gap?</p>
]]></content:encoded>
			<wfw:commentRss>http://marketinsightgroup.com/2009/08/bridging-the-divides/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Release Your Imprisoned Data !!</title>
		<link>http://marketinsightgroup.com/2009/08/free-your-hard-copy-data/</link>
		<comments>http://marketinsightgroup.com/2009/08/free-your-hard-copy-data/#comments</comments>
		<pubDate>Sat, 22 Aug 2009 16:23:29 +0000</pubDate>
		<dc:creator>Barry Rabkin</dc:creator>
				<category><![CDATA[Analytics]]></category>
		<category><![CDATA[Digital Marketplace]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[document management]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[semantic web]]></category>

		<guid isPermaLink="false">http://insurancetechnologyanalyst.wordpress.com/?p=123</guid>
		<description><![CDATA[<p>Insurance companies could fuel years, if not decades, of rip-roaring bonfires with their inventory of hard-copy documents. Every department from underwriting to claims to legal (and for life insurers, medical) and other functional departments all have mountains of documents stored in file cabinets and desk drawers too numerous to count.</p>
<p>Each one of those documents encompasses significant information assets crying out to be freed from their paper prisons and released into a coherent digital infrastructure. As long as the information is held prisoner in their forms, only the jailer can access and use the assets frozen in place. Sharing across departments is done infrequently if at all. Sharing throughout the value chains that touch the field staff, producers, regulators and reinsurers is done mostly at the proverbial point of a gun.</p>
<p><strong>Be Free, Data, Be Free!!</strong></p>
<p>If all the data were set free from their hard-copy prisons and poured into coherent data structures that were tagged and searchable throughout the insurance company (including by stakeholders across all the value chains), what might we want to do?</p>
<ul>
<li>Perhaps we could tag the various products with the terms, conditions, restrictions, endorsements or riders (depending on the flavor of insurance we are talking about) so that someone could search on any one of those attributes, Or</li>
<li>Each set of claim information could have descriptions of what the claim adjuster was thinking when s/he saw the loss occurrence &#8211; something relating to the magnitude of the impact or loss of the claimant&#8217;s property, Or</li>
<li>Product forms could have descriptions relating to why the product was created, the markets the insurer wanted to penetrate and the competitors the insurer was striving to gain market share from with that specific product</li>
<li>Underwriters could possibly attribute why they had stipulated the acceptance or rejection criteria for each product</li>
<li>Campaign data assets might have descriptions by the marketing department relating to the purpose and scope of each specific campaign</li>
<li>Customer service personnel could describe the tone and nature of the calls they have received from policyholders, prospects and producers for each communication event</li>
</ul>
<p>What would you want to do or expect if your insurance company data were thawed out from their frozen cells and released into a collaborative environment?</p>
]]></description>
			<content:encoded><![CDATA[<p>Insurance companies could fuel years, if not decades, of rip-roaring bonfires with their inventory of hard-copy documents. Every department from underwriting to claims to legal (and for life insurers, medical) and other functional departments all have mountains of documents stored in file cabinets and desk drawers too numerous to count.</p>
<p>Each one of those documents encompasses significant information assets crying out to be freed from their paper prisons and released into a coherent digital infrastructure. As long as the information is held prisoner in their forms, only the jailer can access and use the assets frozen in place. Sharing across departments is done infrequently if at all. Sharing throughout the value chains that touch the field staff, producers, regulators and reinsurers is done mostly at the proverbial point of a gun.</p>
<p><strong>Be Free, Data, Be Free!!</strong></p>
<p>If all the data were set free from their hard-copy prisons and poured into coherent data structures that were tagged and searchable throughout the insurance company (including by stakeholders across all the value chains), what might we want to do?</p>
<ul>
<li>Perhaps we could tag the various products with the terms, conditions, restrictions, endorsements or riders (depending on the flavor of insurance we are talking about) so that someone could search on any one of those attributes, Or</li>
<li>Each set of claim information could have descriptions of what the claim adjuster was thinking when s/he saw the loss occurrence &#8211; something relating to the magnitude of the impact or loss of the claimant&#8217;s property, Or</li>
<li>Product forms could have descriptions relating to why the product was created, the markets the insurer wanted to penetrate and the competitors the insurer was striving to gain market share from with that specific product</li>
<li>Underwriters could possibly attribute why they had stipulated the acceptance or rejection criteria for each product</li>
<li>Campaign data assets might have descriptions by the marketing department relating to the purpose and scope of each specific campaign</li>
<li>Customer service personnel could describe the tone and nature of the calls they have received from policyholders, prospects and producers for each communication event</li>
</ul>
<p>What would you want to do or expect if your insurance company data were thawed out from their frozen cells and released into a collaborative environment?</p>
]]></content:encoded>
			<wfw:commentRss>http://marketinsightgroup.com/2009/08/free-your-hard-copy-data/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
