<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://mix.chimpfeedr.com/29cb9-TotalData</id>
  <title>TotalData</title>
  <updated>2017-08-16T21:38:00+00:00</updated>
  <link rel="self" href="http://mix.chimpfeedr.com/29cb9-TotalData"/>
  <generator>http://www.chimpfeedr.com/</generator>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-3772301548727054194</id>
    <title type="html">Digital Disruption, Delivery and Differentiation in Fast Food</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2017-08-16T21:38:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2017/08/digital-disruption-delivery-and.html"/>
    <summary type="html"><![CDATA[What are the differentiating forces in the fast food sector? Stuart Lauchlan hears some contrasting opinions from a couple of industry leaders.<br><br>In the short term, those fast food outlets that offer digital experience and delivery may get some degree of competitive advantage by reaching more customers, with greater convenience. Denny Marie Post, CEO at Red Robin Gourmet Burgers, sees the expansion of third-party delivery services as a strategic priority. So from <b>agility </b>to <b>reach</b>. <br><br>But Lenny Comma, CEO of Jack in the Box, argues that this advantage will be short-lived. Longer-term competitive advantage will depend on the quality of the brand. So from <b>assurance </b>to <b>richness</b>.<br><br><br><hr><br>Stuart Lauchlan, <a href="http://diginomica.com/2017/08/16/digital-delivery-d-matters-fast-food-industry-two-contrasting-views/amp/">Digital and delivery &ndash; which &lsquo;D&rsquo; matters most to the fast food industry? Two contrasting views </a>(Diginomica, 16 August 2017)<br><br>Related post: <a href="https://rvsoapbox.blogspot.co.uk/2017/08/reach-richness-agility-and-assurance.html">Reach, Richness, Agility and Assurance</a> (Aug 2017) <br><br><br>]]></summary>
    <content type="html"><![CDATA[What are the differentiating forces in the fast food sector? Stuart Lauchlan hears some contrasting opinions from a couple of industry leaders.<br><br>In the short term, those fast food outlets that offer digital experience and delivery may get some degree of competitive advantage by reaching more customers, with greater convenience. Denny Marie Post, CEO at Red Robin Gourmet Burgers, sees the expansion of third-party delivery services as a strategic priority. So from <b>agility </b>to <b>reach</b>. <br><br>But Lenny Comma, CEO of Jack in the Box, argues that this advantage will be short-lived. Longer-term competitive advantage will depend on the quality of the brand. So from <b>assurance </b>to <b>richness</b>.<br><br><br><hr><br>Stuart Lauchlan, <a href="http://diginomica.com/2017/08/16/digital-delivery-d-matters-fast-food-industry-two-contrasting-views/amp/">Digital and delivery &ndash; which &lsquo;D&rsquo; matters most to the fast food industry? Two contrasting views </a>(Diginomica, 16 August 2017)<br><br>Related post: <a href="https://rvsoapbox.blogspot.co.uk/2017/08/reach-richness-agility-and-assurance.html">Reach, Richness, Agility and Assurance</a> (Aug 2017) <br><br><br>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-8012294271182461203</id>
    <title type="html">Reach, Richness, Agility and Assurance</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2017-08-15T22:11:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2017/08/reach-richness-agility-and-assurance.html"/>
    <summary type="html"><![CDATA[The concept of TotalData&trade; implements the four dimensions of data and information - reach, richness, assurance and agility. But where did these dimensions come from?<br><br><a href="https://4.bp.blogspot.com/-VhZwsmWtpz4/V6cXV1C5KtI/AAAAAAAAAIM/HwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB/s1600/TotalData.png"><img border="0" height="181" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-VhZwsmWtpz4%2FV6cXV1C5KtI%2FAAAAAAAAAIM%2FHwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB%2Fs400%2FTotalData.png&width=540&mix=29cb9-TotalData" width="400"></a><br><br>I first encountered these four dimensions in discussions of net-centricity, which spilled out from the US defence world into the commercial world over ten years ago. Trying to dig up the original material recently, I found a military version in a report written in 2005 by the Association for Enterprise Integration (AFEI) for the Net-Centric Operations Industry Forum (NCOIF).<br><br>Going further back, the first two dimensions - reach and richness - had been discussed by Evans and Wurster before the turn of the millennium. They argued that old technologies had forced you to choose (either/or) between reach and richness, whereas the new technologies emerging at that time allowed you to have both/and.<br><br><table align="center" cellpadding="0" cellspacing="0"><tbody><tr><td><a href="https://hbr.org/1997/09/strategy-and-the-new-economics-of-information" imageanchor="1"><img border="0" data-original-height="245" data-original-width="390" height="201" src="http://chimpfeedr.com/img/?url=https%3A%2F%2Fhbr.org%2Fresources%2Fimages%2Farticle_assets%2Fhbr%2F9709%2F97504_A.gif&width=540&mix=29cb9-TotalData" width="320"></a></td></tr><tr><td><a href="https://hbr.org/1997/09/strategy-and-the-new-economics-of-information">Source: Evans and Wurster 1997</a></td></tr></tbody></table><br>The authors also introduced the concept of affiliation, by which they meant transparency of relationships - for example, knowing whether the intermediary agent is working for you or working for the other side. Or both. And knowing who really wrote all those "customer reviews".<br><br>According to the authors, it would be these three factors - reach, richness and affiliation - that would determine the success of e-commerce. Clearly some sectors would be more open to these factors than others - according to The Economist in February 2000, online trade was then dominated by business-to-business (B2B). The three factors identified some of the challenges facing other sectors, including professional services, in going online. As Duncan, Barton and McKellar argued for legal firms, "The Web provides Reach, but offering Richness and the sense of community required for creating and sustaining relationships with visitors could be difficult."<br><br>Meanwhile, new architectural thinking had shown ways of resolving the traditional trade-off between speed (agility) and quality (assurance). (A very early version of this was known as Bimodal IT. Some industry analysts are still pushing this idea.)<br><br>When agility and assurance were added to reach and richness to produce the four dimensions of net-centricity, affiliation appears to have been divided between community (reach) and trust (assurance). But the importance of affiliation was never entirely forgotten. As Commander Chakraborty observes, "organisational affiliations and culture ... play very significant roles in a networked environment."<br><br>So whatever happened to net-centricity? It has been replaced by data-centricity, which, as Dan Risacher argues, is probably a more accurate term anyway. Or as we call it at Reply, TotalData&trade;.<br><br><br><br><hr>Notes and References<br><br>Much of the original material for the NCOW Reference Model is no longer available. This includes the pages referenced from Wikipedia: <a href="https://en.wikipedia.org/wiki/NCOW">NCOW</a> (retrieved 8 August 2017). Net-centric concepts were incorporated into DODAF Version 1.5 (April 2007).<br><br><a href="http://www.economist.com/node/285533">Define and Sell</a> (Economist, 24 Feb 2000) <br><br>AFEI, <a href="https://www.blogger.com/resources.sei.cmu.edu/asset_files/WhitePaper/2005_019_001_29406.pdf">Industry Best Practices in Achieving Service Oriented Architecture (SOA)</a> (NCOIF, April 2005)<br><br>Devbrat Chakraborty, <a href="http://www.spsnavalforces.com/story/?id=154">Net-Centricity to Ne(x)t-Centricity</a> (SP's Navel Forces, Issue 4/2011)<br><br>Peter Duncan, Karen Barton and Patricia McKellar, <a href="http://www.bileta.ac.uk/content/files/conference%20papers/2001/Reach%20and%20Rich%20-%20the%20New%20Economics%20of%20Information%20and%20the%20Provision%20of%20On-Line%20Legal%20Services%20in%20The%20UK.pdf">Reach and Rich: the new economics of information and the provision of on-line legal services in the U.K.</a> (16th Bileta Annual Conference, 2001)<br><br>Philip Evans and Thomas S. Wurster, <a href="https://hbr.org/1997/09/strategy-and-the-new-economics-of-information">Strategy and the New Economics of Information</a> (Harvard Business Review, Sept-Oct 1997)<br><br>Philip Evans and Thomas Wurster, Blown to Bits - How the New Economics of Information Transforms Strategy (Boston Consulting Group, 2000) - <a href="https://www.bcgperspectives.com/content/articles/strategy_growth_blown_to_bits_book/">excerpts</a>. See also reviews by McRae and O'Keefe.<br><br>Hamish McRae, <a href="http://www.independent.co.uk/news/business/the-business-world-three-factors-that-lead-to-successful-e-commerce-1126558.html">The business world: Three factors that lead to successful e-commerce</a> (Independent, 17 November 1999) - review of Evans and Wurster (2000)<br><br>Jordan Moskowitz, <a href="http://blog.servicechannel.info/facilities-management-blog/richness-versus-reach">Richness versus Reach</a> (Service Channel, 29 Jan 2013)<br><br>Terry O'Keefe, <a href="https://www.bizjournals.com/atlanta/stories/1999/11/01/smallb8.html">The strategy of information: Richness and reach</a> (Atlanta Business Journal, 1 November 1999) - review of Evans and Wurster (2000)<br><br>Dan Risacher, <a href="https://risacher.org/blog/2013/02/netcentricity/">The Fundamentals of Net-Centricity (a little late)</a> (4 February 2013)<br><br><br><br>Related Posts: <a href="https://rvsoapbox.blogspot.co.uk/2016/05/beyond-bimodal.html">Beyond Bimodal</a> (May 2016), <a href="https://rvsoapbox.blogspot.co.uk/2016/08/new-white-paper-totaldata.html">New White Paper - TotalData&trade;</a> (August 2016)<br><br>TotalData&trade; is a registered trademark of Reply Ltd.]]></summary>
    <content type="html"><![CDATA[The concept of TotalData&trade; implements the four dimensions of data and information - reach, richness, assurance and agility. But where did these dimensions come from?<br><br><a href="https://4.bp.blogspot.com/-VhZwsmWtpz4/V6cXV1C5KtI/AAAAAAAAAIM/HwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB/s1600/TotalData.png"><img border="0" height="181" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-VhZwsmWtpz4%2FV6cXV1C5KtI%2FAAAAAAAAAIM%2FHwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB%2Fs400%2FTotalData.png&width=540&mix=29cb9-TotalData" width="400"></a><br><br>I first encountered these four dimensions in discussions of net-centricity, which spilled out from the US defence world into the commercial world over ten years ago. Trying to dig up the original material recently, I found a military version in a report written in 2005 by the Association for Enterprise Integration (AFEI) for the Net-Centric Operations Industry Forum (NCOIF).<br><br>Going further back, the first two dimensions - reach and richness - had been discussed by Evans and Wurster before the turn of the millennium. They argued that old technologies had forced you to choose (either/or) between reach and richness, whereas the new technologies emerging at that time allowed you to have both/and.<br><br><table align="center" cellpadding="0" cellspacing="0"><tbody><tr><td><a href="https://hbr.org/1997/09/strategy-and-the-new-economics-of-information" imageanchor="1"><img border="0" data-original-height="245" data-original-width="390" height="201" src="http://chimpfeedr.com/img/?url=https%3A%2F%2Fhbr.org%2Fresources%2Fimages%2Farticle_assets%2Fhbr%2F9709%2F97504_A.gif&width=540&mix=29cb9-TotalData" width="320"></a></td></tr><tr><td><a href="https://hbr.org/1997/09/strategy-and-the-new-economics-of-information">Source: Evans and Wurster 1997</a></td></tr></tbody></table><br>The authors also introduced the concept of affiliation, by which they meant transparency of relationships - for example, knowing whether the intermediary agent is working for you or working for the other side. Or both. And knowing who really wrote all those "customer reviews".<br><br>According to the authors, it would be these three factors - reach, richness and affiliation - that would determine the success of e-commerce. Clearly some sectors would be more open to these factors than others - according to The Economist in February 2000, online trade was then dominated by business-to-business (B2B). The three factors identified some of the challenges facing other sectors, including professional services, in going online. As Duncan, Barton and McKellar argued for legal firms, "The Web provides Reach, but offering Richness and the sense of community required for creating and sustaining relationships with visitors could be difficult."<br><br>Meanwhile, new architectural thinking had shown ways of resolving the traditional trade-off between speed (agility) and quality (assurance). (A very early version of this was known as Bimodal IT. Some industry analysts are still pushing this idea.)<br><br>When agility and assurance were added to reach and richness to produce the four dimensions of net-centricity, affiliation appears to have been divided between community (reach) and trust (assurance). But the importance of affiliation was never entirely forgotten. As Commander Chakraborty observes, "organisational affiliations and culture ... play very significant roles in a networked environment."<br><br>So whatever happened to net-centricity? It has been replaced by data-centricity, which, as Dan Risacher argues, is probably a more accurate term anyway. Or as we call it at Reply, TotalData&trade;.<br><br><br><br><hr>Notes and References<br><br>Much of the original material for the NCOW Reference Model is no longer available. This includes the pages referenced from Wikipedia: <a href="https://en.wikipedia.org/wiki/NCOW">NCOW</a> (retrieved 8 August 2017). Net-centric concepts were incorporated into DODAF Version 1.5 (April 2007).<br><br><a href="http://www.economist.com/node/285533">Define and Sell</a> (Economist, 24 Feb 2000) <br><br>AFEI, <a href="https://www.blogger.com/resources.sei.cmu.edu/asset_files/WhitePaper/2005_019_001_29406.pdf">Industry Best Practices in Achieving Service Oriented Architecture (SOA)</a> (NCOIF, April 2005)<br><br>Devbrat Chakraborty, <a href="http://www.spsnavalforces.com/story/?id=154">Net-Centricity to Ne(x)t-Centricity</a> (SP's Navel Forces, Issue 4/2011)<br><br>Peter Duncan, Karen Barton and Patricia McKellar, <a href="http://www.bileta.ac.uk/content/files/conference%20papers/2001/Reach%20and%20Rich%20-%20the%20New%20Economics%20of%20Information%20and%20the%20Provision%20of%20On-Line%20Legal%20Services%20in%20The%20UK.pdf">Reach and Rich: the new economics of information and the provision of on-line legal services in the U.K.</a> (16th Bileta Annual Conference, 2001)<br><br>Philip Evans and Thomas S. Wurster, <a href="https://hbr.org/1997/09/strategy-and-the-new-economics-of-information">Strategy and the New Economics of Information</a> (Harvard Business Review, Sept-Oct 1997)<br><br>Philip Evans and Thomas Wurster, Blown to Bits - How the New Economics of Information Transforms Strategy (Boston Consulting Group, 2000) - <a href="https://www.bcgperspectives.com/content/articles/strategy_growth_blown_to_bits_book/">excerpts</a>. See also reviews by McRae and O'Keefe.<br><br>Hamish McRae, <a href="http://www.independent.co.uk/news/business/the-business-world-three-factors-that-lead-to-successful-e-commerce-1126558.html">The business world: Three factors that lead to successful e-commerce</a> (Independent, 17 November 1999) - review of Evans and Wurster (2000)<br><br>Jordan Moskowitz, <a href="http://blog.servicechannel.info/facilities-management-blog/richness-versus-reach">Richness versus Reach</a> (Service Channel, 29 Jan 2013)<br><br>Terry O'Keefe, <a href="https://www.bizjournals.com/atlanta/stories/1999/11/01/smallb8.html">The strategy of information: Richness and reach</a> (Atlanta Business Journal, 1 November 1999) - review of Evans and Wurster (2000)<br><br>Dan Risacher, <a href="https://risacher.org/blog/2013/02/netcentricity/">The Fundamentals of Net-Centricity (a little late)</a> (4 February 2013)<br><br><br><br>Related Posts: <a href="https://rvsoapbox.blogspot.co.uk/2016/05/beyond-bimodal.html">Beyond Bimodal</a> (May 2016), <a href="https://rvsoapbox.blogspot.co.uk/2016/08/new-white-paper-totaldata.html">New White Paper - TotalData&trade;</a> (August 2016)<br><br>TotalData&trade; is a registered trademark of Reply Ltd.]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-3004477109350026790</id>
    <title type="html">From Dodgy Data to Dodgy Policy - Mrs May's Immigration Targets</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2017-03-16T18:11:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2017/03/from-dodgy-data-to-dodgy-policy-mrs.html"/>
    <summary type="html"><![CDATA[The TotalData&trade; value chain is about the flow from raw data to business decisions (including evidence-based policy decisions).<br><br>In this post, I want to talk about an interesting example of a flawed data-driven policy. The UK Prime Minister,  Theresa May, is determined to reduce the number of international students visiting the UK. This conflicts with the advice she is getting from nearly everyone, including her own ministers.<br><br>As @Skapinker explains in the Financial Times, there are a number of mis-steps in this case.<br><ul><li><b>Distorted data collection</b>. Mrs May's policy is supported by raw data indicating the number of students that return to their country of origin. These are estimated measurements, based on daytime and evening surveys taken at UK airports. Therefore students travelling on late-night flights to such countries as China, Nigeria, Hong Kong, Saudi Arabia and Singapore are systematically excluded from the data. </li></ul><ul><li><b>Disputed data definition</b>. Most British people do not regard international students as immigrants. But as May stubbornly repeated to a parliamentary committee in December 2016, she insists on using an international definition of migration, which includes any students that stay for more than 12 months. </li></ul><ul><li><b>Conflating measurement with target</b>. Mrs May told the committee that "the target figures are calculated from the overall migration figures, and students are in the overall migration figures because it is an international definition of migration". But as Yvette Cooper pointed out "The figures are different from the target. ... You choose what to target."</li></ul><ul><li><b>Refusal to correct baseline</b>. Sometimes the easiest way to achieve a goal is to move the goalposts. Some people are quick to use this tactic, while others instinctively resist change. Mrs May is in the latter camp, and appears to regard any adjustment of the baseline as backsliding and morally suspect.</li></ul>If you work with enterprise data, you may recognize these anti-patterns.<br><br><br><hr><br>David Runciman, <a href="https://www.lrb.co.uk/v39/n06/david-runciman/do-your-homework">Do your homework</a> (London Review of Books Vol. 39 No. 6, 16 March 2017) <br><br>Michael Skapinker, <a href="https://www.ft.com/content/a1b695da-07e7-11e7-97d1-5e720a26771b">Theresa May&rsquo;s clampdown on international students is a mystery</a> (Financial Times, 15 March 2017)<br><br><a href="http://www.migrationobservatory.ox.ac.uk/resources/commentaries/international-students-and-the-net-migration-target-should-students-be-taken-out/">International students and the net migration target: Should students be taken out?</a> (Migration Observatory, 25 Jun 2015) <br><br><a href="https://www.parliament.uk/documents/commons-committees/liaison/Prime-Minister-evidence-December-2016.pdf">Oral evidence: The Prime Minister</a> (House of Commons HC 833, 20 December 2016)&nbsp;<br><br><span><br></span><span><span>TotalData&trade; is a trademark of Reply Ltd. All rights reserved</span> </span>]]></summary>
    <content type="html"><![CDATA[The TotalData&trade; value chain is about the flow from raw data to business decisions (including evidence-based policy decisions).<br><br>In this post, I want to talk about an interesting example of a flawed data-driven policy. The UK Prime Minister,  Theresa May, is determined to reduce the number of international students visiting the UK. This conflicts with the advice she is getting from nearly everyone, including her own ministers.<br><br>As @Skapinker explains in the Financial Times, there are a number of mis-steps in this case.<br><ul><li><b>Distorted data collection</b>. Mrs May's policy is supported by raw data indicating the number of students that return to their country of origin. These are estimated measurements, based on daytime and evening surveys taken at UK airports. Therefore students travelling on late-night flights to such countries as China, Nigeria, Hong Kong, Saudi Arabia and Singapore are systematically excluded from the data. </li></ul><ul><li><b>Disputed data definition</b>. Most British people do not regard international students as immigrants. But as May stubbornly repeated to a parliamentary committee in December 2016, she insists on using an international definition of migration, which includes any students that stay for more than 12 months. </li></ul><ul><li><b>Conflating measurement with target</b>. Mrs May told the committee that "the target figures are calculated from the overall migration figures, and students are in the overall migration figures because it is an international definition of migration". But as Yvette Cooper pointed out "The figures are different from the target. ... You choose what to target."</li></ul><ul><li><b>Refusal to correct baseline</b>. Sometimes the easiest way to achieve a goal is to move the goalposts. Some people are quick to use this tactic, while others instinctively resist change. Mrs May is in the latter camp, and appears to regard any adjustment of the baseline as backsliding and morally suspect.</li></ul>If you work with enterprise data, you may recognize these anti-patterns.<br><br><br><hr><br>David Runciman, <a href="https://www.lrb.co.uk/v39/n06/david-runciman/do-your-homework">Do your homework</a> (London Review of Books Vol. 39 No. 6, 16 March 2017) <br><br>Michael Skapinker, <a href="https://www.ft.com/content/a1b695da-07e7-11e7-97d1-5e720a26771b">Theresa May&rsquo;s clampdown on international students is a mystery</a> (Financial Times, 15 March 2017)<br><br><a href="http://www.migrationobservatory.ox.ac.uk/resources/commentaries/international-students-and-the-net-migration-target-should-students-be-taken-out/">International students and the net migration target: Should students be taken out?</a> (Migration Observatory, 25 Jun 2015) <br><br><a href="https://www.parliament.uk/documents/commons-committees/liaison/Prime-Minister-evidence-December-2016.pdf">Oral evidence: The Prime Minister</a> (House of Commons HC 833, 20 December 2016)&nbsp;<br><br><span><br></span><span><span>TotalData&trade; is a trademark of Reply Ltd. All rights reserved</span> </span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-2922980019473300661</id>
    <title type="html">The Unexpected Happens</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2017-01-01T18:08:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2017/01/the-unexpected-happens.html"/>
    <summary type="html"><![CDATA[When Complex Event Processing (CEP) emerged around ten years ago, one of the early applications was real-time risk management. In the financial sector, there was growing recognition for the need for real-time visibility - continuous calibration of positions &ndash; in order to keep pace with the emerging importance of algorithmic trading. This is now relatively well-established in banking and trading sectors; Chemitiganti argues that the insurance industry now faces similar requirements.<br><br>In 2008, Chris Martins, then Marketing Director for CEP firm Apama, suggested considering CEP as a prospective "dog whisperer" that can help manage the risk of the technology "dog" biting its master.<br><br>But "dog bites master" works in both directions. In the case of Eliot Spitzer, the dog that bit its master was the anti money-laundering software that he had used against others.<br><br>And in the case of algorithmic trading, it seems we can no longer be sure who is master - whether black swan events are the inevitable and emergent result of excessive complexity, or whether hostile agents are engaged in a black swan breeding programme.&nbsp; One of the first CEP insiders to raise this concern was John Bates, first as CTO at Apama and subsequently with Software AG. (He now works for a subsidiary of SAP.)<br><br><table align="center" cellpadding="0" cellspacing="0"><tbody><tr><td><a href="https://4.bp.blogspot.com/-03HSe_aT65c/WGkvGZc482I/AAAAAAAAAKk/-CSQEafnjNcbE-jeliiVAs_7NpMFQe_5gCLcB/s1600/CEP%2BBlack%2BSwans%2BDark%2BPools%2Bp62.PNG" imageanchor="1"><img border="0" height="307" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-03HSe_aT65c%2FWGkvGZc482I%2FAAAAAAAAAKk%2F-CSQEafnjNcbE-jeliiVAs_7NpMFQe_5gCLcB%2Fs320%2FCEP%252BBlack%252BSwans%252BDark%252BPools%252Bp62.PNG&width=540&mix=29cb9-TotalData" width="320"></a></td></tr><tr><td>from Dark Pools by Scott Patterson</td></tr></tbody></table><br>And in 2015, Bates wrote that "high-speed  trading algorithms are an alluring target for cyber thieves". <br><br>So if technology is capable of both generating unexpected events and amplifying hostile attacks, are we being naive to imagine we use the same technology to protect ourselves?<br><br>Perhaps, but I believe there are some productive lines of development, as I've discussed previously on this blog and elsewhere.<br><br><br>1. <b>Organizational intelligence</b> - not relying either on human intelligence alone or on artificial intelligence alone, but looking for establishing sociotechnical systems that allow people and algorithms to collaborate effectively.<br><br>2. <b>Algorithmic biodiversity</b> - maintaining multiple algorithms, developed by different teams using  different datasets, in order to detect additional weak signals and  generate "second opinions".<br><br><br><br><hr><br>John Bates, <a href="http://apama.typepad.com/my_weblog/2010/08/algorithmic-terrorism.html">Algorithmic Terrorism</a> (Apama, 4 August 2010). <a href="http://www.huffingtonpost.com/john-bates/to-catch-an-algo-thief_b_6759286.html">To Catch an Algo Thief</a> (Huffington Post, 26 Feb 2015)<br><br>John Borland, <a href="http://www.technologyreview.com/Infotech/20435/?a=f">The Technology That Toppled Eliot Spitzer</a> (MIT Technology Review, 19 March 2008) via Adam Shostack, <a href="http://emergentchaos.com/archives/2008/03/algorithms-for-the-war-on-the-unexpected.html">Algorithms for the War on the Unexpected</a> (19 March 2008)<br><br>Vamsi Chemitiganti, <a href="http://www.vamsitalkstech.com/?p=2758">Why the Insurance Industry Needs to Learn from Banking&rsquo;s Risk Management Nightmares..</a> (10 September 2016)<br><br>Theo Hildyard, <a href="http://www.thetradingmesh.com/pg/blog/softwareag/read/618299/pillar-6-of-market-surveillance-20-known-and-unknown-threats">Pillar #6 of Market Surveillance 2.0: Known and unknown threats</a> (Trading Mesh, 2 April 2015)<br><br>Neil Johnson et al, <a href="https://arxiv.org/abs/1202.1448">Financial black swans driven by ultrafast machine ecology</a> (arXiv:1202.1448 [physics.soc-ph], 7 Feb 2012)<br><br>Chris Martins, <a href="http://apama.typepad.com/my_weblog/2008/03/cep-and-real-ti.html">CEP and Real-Time Risk &ndash; &ldquo;The Dog Whisperer&rdquo;</a> (Apama, 21 March 2008)<br><br>Scott Patterson, Dark Pools - The Rise of A. I. Trading Machines and the Looming Threat to Wall Street (Random House, 2013). See review by David Leinweber, <a href="http://www.forbes.com/sites/davidleinweber/2012/07/11/the-algorithmic-monsters-threatening-the-global-financial-system/#2d4993fa5c42">Are Algorithmic Monsters Threatening The Global Financial System?</a> (Forbes, 11 July 2012)<br><br>Richard Veryard, <a href="https://leanpub.com/orgintelligence/">Building Organizational Intelligence</a> (LeanPub, 2012)<br><br>Related Posts<br><br><a href="https://rvsoapbox.blogspot.co.uk/2016/10/the-shelf-life-of-algorithms.html">The Shelf-Life of Algorithms</a> (October 2016)]]></summary>
    <content type="html"><![CDATA[When Complex Event Processing (CEP) emerged around ten years ago, one of the early applications was real-time risk management. In the financial sector, there was growing recognition for the need for real-time visibility - continuous calibration of positions &ndash; in order to keep pace with the emerging importance of algorithmic trading. This is now relatively well-established in banking and trading sectors; Chemitiganti argues that the insurance industry now faces similar requirements.<br><br>In 2008, Chris Martins, then Marketing Director for CEP firm Apama, suggested considering CEP as a prospective "dog whisperer" that can help manage the risk of the technology "dog" biting its master.<br><br>But "dog bites master" works in both directions. In the case of Eliot Spitzer, the dog that bit its master was the anti money-laundering software that he had used against others.<br><br>And in the case of algorithmic trading, it seems we can no longer be sure who is master - whether black swan events are the inevitable and emergent result of excessive complexity, or whether hostile agents are engaged in a black swan breeding programme.&nbsp; One of the first CEP insiders to raise this concern was John Bates, first as CTO at Apama and subsequently with Software AG. (He now works for a subsidiary of SAP.)<br><br><table align="center" cellpadding="0" cellspacing="0"><tbody><tr><td><a href="https://4.bp.blogspot.com/-03HSe_aT65c/WGkvGZc482I/AAAAAAAAAKk/-CSQEafnjNcbE-jeliiVAs_7NpMFQe_5gCLcB/s1600/CEP%2BBlack%2BSwans%2BDark%2BPools%2Bp62.PNG" imageanchor="1"><img border="0" height="307" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-03HSe_aT65c%2FWGkvGZc482I%2FAAAAAAAAAKk%2F-CSQEafnjNcbE-jeliiVAs_7NpMFQe_5gCLcB%2Fs320%2FCEP%252BBlack%252BSwans%252BDark%252BPools%252Bp62.PNG&width=540&mix=29cb9-TotalData" width="320"></a></td></tr><tr><td>from Dark Pools by Scott Patterson</td></tr></tbody></table><br>And in 2015, Bates wrote that "high-speed  trading algorithms are an alluring target for cyber thieves". <br><br>So if technology is capable of both generating unexpected events and amplifying hostile attacks, are we being naive to imagine we use the same technology to protect ourselves?<br><br>Perhaps, but I believe there are some productive lines of development, as I've discussed previously on this blog and elsewhere.<br><br><br>1. <b>Organizational intelligence</b> - not relying either on human intelligence alone or on artificial intelligence alone, but looking for establishing sociotechnical systems that allow people and algorithms to collaborate effectively.<br><br>2. <b>Algorithmic biodiversity</b> - maintaining multiple algorithms, developed by different teams using  different datasets, in order to detect additional weak signals and  generate "second opinions".<br><br><br><br><hr><br>John Bates, <a href="http://apama.typepad.com/my_weblog/2010/08/algorithmic-terrorism.html">Algorithmic Terrorism</a> (Apama, 4 August 2010). <a href="http://www.huffingtonpost.com/john-bates/to-catch-an-algo-thief_b_6759286.html">To Catch an Algo Thief</a> (Huffington Post, 26 Feb 2015)<br><br>John Borland, <a href="http://www.technologyreview.com/Infotech/20435/?a=f">The Technology That Toppled Eliot Spitzer</a> (MIT Technology Review, 19 March 2008) via Adam Shostack, <a href="http://emergentchaos.com/archives/2008/03/algorithms-for-the-war-on-the-unexpected.html">Algorithms for the War on the Unexpected</a> (19 March 2008)<br><br>Vamsi Chemitiganti, <a href="http://www.vamsitalkstech.com/?p=2758">Why the Insurance Industry Needs to Learn from Banking&rsquo;s Risk Management Nightmares..</a> (10 September 2016)<br><br>Theo Hildyard, <a href="http://www.thetradingmesh.com/pg/blog/softwareag/read/618299/pillar-6-of-market-surveillance-20-known-and-unknown-threats">Pillar #6 of Market Surveillance 2.0: Known and unknown threats</a> (Trading Mesh, 2 April 2015)<br><br>Neil Johnson et al, <a href="https://arxiv.org/abs/1202.1448">Financial black swans driven by ultrafast machine ecology</a> (arXiv:1202.1448 [physics.soc-ph], 7 Feb 2012)<br><br>Chris Martins, <a href="http://apama.typepad.com/my_weblog/2008/03/cep-and-real-ti.html">CEP and Real-Time Risk &ndash; &ldquo;The Dog Whisperer&rdquo;</a> (Apama, 21 March 2008)<br><br>Scott Patterson, Dark Pools - The Rise of A. I. Trading Machines and the Looming Threat to Wall Street (Random House, 2013). See review by David Leinweber, <a href="http://www.forbes.com/sites/davidleinweber/2012/07/11/the-algorithmic-monsters-threatening-the-global-financial-system/#2d4993fa5c42">Are Algorithmic Monsters Threatening The Global Financial System?</a> (Forbes, 11 July 2012)<br><br>Richard Veryard, <a href="https://leanpub.com/orgintelligence/">Building Organizational Intelligence</a> (LeanPub, 2012)<br><br>Related Posts<br><br><a href="https://rvsoapbox.blogspot.co.uk/2016/10/the-shelf-life-of-algorithms.html">The Shelf-Life of Algorithms</a> (October 2016)]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-1254315679163990153.post-8333004453511300449</id>
    <title type="html">Pay as you Share</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2016-11-03T20:50:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://demandingchange.blogspot.com/2016/11/pay-as-you-share.html"/>
    <summary type="html"><![CDATA[Announced and rapidly withdrawn, Admiral's proposed collaboration  with Facebook was supposed to give drivers a discount on their car  insurance premiums if their Facebook posts indicated the right kind of  personality. According to some reports, the idea was that people who  were reckless with punctuation (too many exclamation marks, not enough  full stops) might also be reckless in their driving habits.<br><br>The  punctuation example is probably a red herring. The analysis of  personality will undoubtedly be based on much richer aspects than mere punctuation: Facebook  is capable of much more sophisticated analysis, as well as selling data to other organizations for the same  purpose.<br><br>For example, a Korean study in 2013 found that Facebook  activities had predictive power in distinguishing depressed and  nondepressed individuals. However, Facebook may not wish to draw too  much public attention to such capabilities. (There are some important ethical issues in the use of algorithms to predict mental health issues, for example in recruitment screening, discussed at length by Cathy O'Neil.)<br><br>Meanwhile, insurance companies will wish to use any information and insight they can get their hands on, to try and calculate risk more accurately. People may consent to sharing their data if they feel they will benefit personally, or if they are unaware of the possible data uses and implications, but that could just result in discrimination against the people who refuse to share their data. So privacy campaigners may not be reassured by the fact that this particular collaboration has been withdrawn. <br><br><hr><br>Cathy O'Neil, <a href="https://www.theguardian.com/science/2016/sep/01/how-algorithms-rule-our-working-lives">How algorithms rule our working lives</a> (Guardian, 1 Sept 2016)<br><br>Sungkyu Park et al, <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3806432/">Activities on Facebook Reveal the Depressive State of Users</a> (J Med Internet Res. 2013 Oct; 15(10): e217)<br><br>Graham Ruddick, <a href="https://www.theguardian.com/technology/2016/nov/02/admiral-to-price-car-insurance-based-on-facebook-posts">Admiral to price car insurance based on Facebook posts</a> (Guardian, 2 November 2016, 00.01 GMT)<br><br>Graham Ruddick, <a href="https://www.theguardian.com/money/2016/nov/02/facebook-admiral-car-insurance-privacy-data">Facebook forces Admiral to pull plan to price car insurance based on posts</a> (Guardian, 2 November 2016, 18.41 GMT)<br><br><br>Related posts<br><a href="https://businessorganizationmanagement.blogspot.co.uk/2016/10/weapons-of-math-destruction.html">Weapons of Math Destruction</a> (Oct 2016)]]></summary>
    <content type="html"><![CDATA[Announced and rapidly withdrawn, Admiral's proposed collaboration  with Facebook was supposed to give drivers a discount on their car  insurance premiums if their Facebook posts indicated the right kind of  personality. According to some reports, the idea was that people who  were reckless with punctuation (too many exclamation marks, not enough  full stops) might also be reckless in their driving habits.<br><br>The  punctuation example is probably a red herring. The analysis of  personality will undoubtedly be based on much richer aspects than mere punctuation: Facebook  is capable of much more sophisticated analysis, as well as selling data to other organizations for the same  purpose.<br><br>For example, a Korean study in 2013 found that Facebook  activities had predictive power in distinguishing depressed and  nondepressed individuals. However, Facebook may not wish to draw too  much public attention to such capabilities. (There are some important ethical issues in the use of algorithms to predict mental health issues, for example in recruitment screening, discussed at length by Cathy O'Neil.)<br><br>Meanwhile, insurance companies will wish to use any information and insight they can get their hands on, to try and calculate risk more accurately. People may consent to sharing their data if they feel they will benefit personally, or if they are unaware of the possible data uses and implications, but that could just result in discrimination against the people who refuse to share their data. So privacy campaigners may not be reassured by the fact that this particular collaboration has been withdrawn. <br><br><hr><br>Cathy O'Neil, <a href="https://www.theguardian.com/science/2016/sep/01/how-algorithms-rule-our-working-lives">How algorithms rule our working lives</a> (Guardian, 1 Sept 2016)<br><br>Sungkyu Park et al, <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3806432/">Activities on Facebook Reveal the Depressive State of Users</a> (J Med Internet Res. 2013 Oct; 15(10): e217)<br><br>Graham Ruddick, <a href="https://www.theguardian.com/technology/2016/nov/02/admiral-to-price-car-insurance-based-on-facebook-posts">Admiral to price car insurance based on Facebook posts</a> (Guardian, 2 November 2016, 00.01 GMT)<br><br>Graham Ruddick, <a href="https://www.theguardian.com/money/2016/nov/02/facebook-admiral-car-insurance-privacy-data">Facebook forces Admiral to pull plan to price car insurance based on posts</a> (Guardian, 2 November 2016, 18.41 GMT)<br><br><br>Related posts<br><a href="https://businessorganizationmanagement.blogspot.co.uk/2016/10/weapons-of-math-destruction.html">Weapons of Math Destruction</a> (Oct 2016)]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-7722141891272197658</id>
    <title type="html">The Shelf-Life of Algorithms</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2016-10-26T13:50:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2016/10/the-shelf-life-of-algorithms.html"/>
    <summary type="html"><![CDATA[@<a href="https://twitter.com/mrkwpalmer/status/773098394952884225">mrkwpalmer</a> (TIBCO) invites us to take what he calls a Hyper-Darwinian approach to analytics. He observes that "many algorithms, once discovered, have a remarkably short shelf-life" and argues that one must be as good at "killing off weak or vanquished algorithms" as creating new ones.<br><br>As I've pointed out elsewhere (<a href="http://posiwid.blogspot.co.uk/2010/12/arguments-from-nature.html">Arguments from Nature</a>, December 2010), the non-survival of the unfit (as implied by his phrase) is not logically equivalent to the survival of the fittest, and Darwinian analogies always need to be taken with a pinch of salt. However, Mark raises an important point about the limitations of algorithms, and the need for constant review and adaptation, to maintain what he calls <b>algorithmic efficacy</b>.<br><br>His examples fall into three types. Firstly there are algorithms designed to anticipate and outwit human and social processes, from financial trading to fraud. Clearly these need to be constantly modified, otherwise the humans will learn to outwit the algorithms. And secondly there are algorithms designed to compete with other algorithms. In both cases, these algorithms need to keep ahead of the competition and to avoid themselves becoming predictable. Following an evolutionary analogy, the mutual adaptation of fraud and anti-fraud tactics resembles the co-evolution of predator and prey.<br><br>Mark also mentions a third type of algorithm, where the element of competition and the need for constant change is less obvious. His main example of this type is in the area of predictive maintenance, where the algorithm is trying to predict the behaviour of devices and networks that may fail in surprising and often inconvenient ways. It is a common human tendency to imagine that these devices are inhabited by demons -- as if a printer or photocopier deliberately jams or runs out of toner because it somehow knows when one is in a real hurry -- but most of us don't take this idea too seriously.<br><br>Where does surprise come from? Bateson suggests that it comes from an interaction between two contrary variables: probability and stability --<br><blockquote>"There would be no surprises in a universe governed either by probability alone or by stability alone."</blockquote>--&nbsp; and points out that because adaptations in Nature are always based on a finite range of circumstances (data points), Nature can always present new circumstances (data) which undermine these adaptations. He calls this the caprice of Nature.<br><blockquote>"This is, in a sense, most unfair. ... But in another sense, or looked at in a wider perspective, this unfairness is the recurrent condition for evolutionary creativity."</blockquote><br>The problem with adaptation being based solely on past experience also arises with machine learning, which generally uses a large but finite dataset to perform inductive reasoning, in a way that is non-transparent to the human. This probably works okay for preventative maintenance on relatively simple and isolated devices, but as devices and their interconnections get more complex, we shouldn't be too surprised if algorithms, whether based on human mathematics or machine learning, sometimes get caught out by the caprice of Nature. Or by so-called Black Swans.<br><br>This potential unreliability is particularly problematic in two cases. Firstly, when the algorithms are used to make critical decisions affecting human lives - as in justice or recruitment systems. (See for example, Zeynap Tufekci's recent TED talk.) And secondly, when preventative maintenance has safety implications - from aeroengineering to medical implants.<br><br>One way of mitigating this risk might be to maintain multiple algorithms, developed by different teams using different datasets, in order to detect additional weak signals and generate "second opinions". And get human experts to look at the cases where the algorithms strongly disagree.<br><br>This would suggest that we maybe shouldn't be too hasty to kill off algorithms with poor efficacy, but sometimes keep them in the interests of algorithmic biodiversity.&nbsp; (There - now I'm using the evolutionary metaphor.)<br><br><br><hr>Gregory Bateson, "The New Conceptual Frames for Behavioural Research". Proceedings of the Sixth Annual Psychiatric Institute (Princeton NJ: New Jersey Neuro-Psychiatric Institute, September 17, 1958). Reprinted in G. Bateson, A Sacred Unity: Further Steps to an Ecology of Mind (edited R.E. Donaldson, New York: Harper Collins, 1991) pp 93-110 <br><br>Mark Palmer, <a href="https://techcrunch.com/2016/09/04/the-emerging-darwinian-approach-to-analytics-and-augmented-intelligence/">The emerging Darwinian approach to analytics and augmented intelligence</a> (TechCrunch, 4 September 2016)<br><br>Zeynap Tufekci, <a href="http://www.ted.com/talks/zeynep_tufekci_we_can_t_control_what_our_intelligent_machines_are_learning?language=en" lang="en">Machine intelligence makes human morals more important</a> (TED Talks, Filmed June 2016)<br><br><br><b>Related Posts</b><br><a href="http://demandingchange.blogspot.com/2016/10/the-transparency-of-algorithms.html">The Transparency of Algorithms</a> (October 2016)]]></summary>
    <content type="html"><![CDATA[@<a href="https://twitter.com/mrkwpalmer/status/773098394952884225">mrkwpalmer</a> (TIBCO) invites us to take what he calls a Hyper-Darwinian approach to analytics. He observes that "many algorithms, once discovered, have a remarkably short shelf-life" and argues that one must be as good at "killing off weak or vanquished algorithms" as creating new ones.<br><br>As I've pointed out elsewhere (<a href="http://posiwid.blogspot.co.uk/2010/12/arguments-from-nature.html">Arguments from Nature</a>, December 2010), the non-survival of the unfit (as implied by his phrase) is not logically equivalent to the survival of the fittest, and Darwinian analogies always need to be taken with a pinch of salt. However, Mark raises an important point about the limitations of algorithms, and the need for constant review and adaptation, to maintain what he calls <b>algorithmic efficacy</b>.<br><br>His examples fall into three types. Firstly there are algorithms designed to anticipate and outwit human and social processes, from financial trading to fraud. Clearly these need to be constantly modified, otherwise the humans will learn to outwit the algorithms. And secondly there are algorithms designed to compete with other algorithms. In both cases, these algorithms need to keep ahead of the competition and to avoid themselves becoming predictable. Following an evolutionary analogy, the mutual adaptation of fraud and anti-fraud tactics resembles the co-evolution of predator and prey.<br><br>Mark also mentions a third type of algorithm, where the element of competition and the need for constant change is less obvious. His main example of this type is in the area of predictive maintenance, where the algorithm is trying to predict the behaviour of devices and networks that may fail in surprising and often inconvenient ways. It is a common human tendency to imagine that these devices are inhabited by demons -- as if a printer or photocopier deliberately jams or runs out of toner because it somehow knows when one is in a real hurry -- but most of us don't take this idea too seriously.<br><br>Where does surprise come from? Bateson suggests that it comes from an interaction between two contrary variables: probability and stability --<br><blockquote>"There would be no surprises in a universe governed either by probability alone or by stability alone."</blockquote>--&nbsp; and points out that because adaptations in Nature are always based on a finite range of circumstances (data points), Nature can always present new circumstances (data) which undermine these adaptations. He calls this the caprice of Nature.<br><blockquote>"This is, in a sense, most unfair. ... But in another sense, or looked at in a wider perspective, this unfairness is the recurrent condition for evolutionary creativity."</blockquote><br>The problem with adaptation being based solely on past experience also arises with machine learning, which generally uses a large but finite dataset to perform inductive reasoning, in a way that is non-transparent to the human. This probably works okay for preventative maintenance on relatively simple and isolated devices, but as devices and their interconnections get more complex, we shouldn't be too surprised if algorithms, whether based on human mathematics or machine learning, sometimes get caught out by the caprice of Nature. Or by so-called Black Swans.<br><br>This potential unreliability is particularly problematic in two cases. Firstly, when the algorithms are used to make critical decisions affecting human lives - as in justice or recruitment systems. (See for example, Zeynap Tufekci's recent TED talk.) And secondly, when preventative maintenance has safety implications - from aeroengineering to medical implants.<br><br>One way of mitigating this risk might be to maintain multiple algorithms, developed by different teams using different datasets, in order to detect additional weak signals and generate "second opinions". And get human experts to look at the cases where the algorithms strongly disagree.<br><br>This would suggest that we maybe shouldn't be too hasty to kill off algorithms with poor efficacy, but sometimes keep them in the interests of algorithmic biodiversity.&nbsp; (There - now I'm using the evolutionary metaphor.)<br><br><br><hr>Gregory Bateson, "The New Conceptual Frames for Behavioural Research". Proceedings of the Sixth Annual Psychiatric Institute (Princeton NJ: New Jersey Neuro-Psychiatric Institute, September 17, 1958). Reprinted in G. Bateson, A Sacred Unity: Further Steps to an Ecology of Mind (edited R.E. Donaldson, New York: Harper Collins, 1991) pp 93-110 <br><br>Mark Palmer, <a href="https://techcrunch.com/2016/09/04/the-emerging-darwinian-approach-to-analytics-and-augmented-intelligence/">The emerging Darwinian approach to analytics and augmented intelligence</a> (TechCrunch, 4 September 2016)<br><br>Zeynap Tufekci, <a href="http://www.ted.com/talks/zeynep_tufekci_we_can_t_control_what_our_intelligent_machines_are_learning?language=en" lang="en">Machine intelligence makes human morals more important</a> (TED Talks, Filmed June 2016)<br><br><br><b>Related Posts</b><br><a href="http://demandingchange.blogspot.com/2016/10/the-transparency-of-algorithms.html">The Transparency of Algorithms</a> (October 2016)]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-1892141954410065503</id>
    <title type="html">85 Million Faces</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2016-10-25T18:57:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2016/10/85-million-faces.html"/>
    <summary type="html"><![CDATA[It should be pretty obvious why Microsoft wants 85 million faces. According to its privacy policy<br><blockquote>Microsoft uses the data we collect to provide you the products we offer,  which includes using data to improve and personalize your experiences.  We also may use the data to communicate with you, for example, informing  you about your account, security updates and product information. And  we use data to help show more relevant ads, whether in our own products  like MSN and Bing, or in products offered by third parties. (retrieved 25 October 2016)</blockquote>Facial recognition software is big business, and high quality image data is clearly a valuable asset.<br><br>But why would 85 million people go along with this? I guess they thought they were just playing a game, and didn't think of it in terms of donating their personal data to Microsoft. The bait was to persuade people to find out how old the software thought they were. <br><br>The Daily Mail persuaded a number of female celebrities to test the software, and printed the results in today's paper.<br><blockquote data-lang="en"><div dir="ltr" lang="en">Computer"tell yr age" programme on my face puts me 69 <a href="https://t.co/EhEog5LQcN">https://t.co/EhEog5LQcN</a> Haha!But why are those judged younger than they are so pleased</div>&mdash; mary beard (@wmarybeard) <a href="https://twitter.com/wmarybeard/status/790881620563783680">October 25, 2016</a></blockquote><br>Talking of beards ...<br><blockquote data-lang="en"><div dir="ltr" lang="en">. <a href="https://twitter.com/futureidentity">@futureidentity</a> If we ever reach peak data, advertisers will check photos before advertising beard accessories <a href="https://twitter.com/hashtag/personalization?src=hash">#personalization</a> <a href="https://twitter.com/hashtag/TotalData?src=hash">#TotalData</a></div>&mdash; Richard Veryard (@richardveryard) <a href="https://twitter.com/richardveryard/status/715905179959369728">April 1, 2016</a></blockquote><br><blockquote data-lang="en"><div dir="ltr" lang="en">. <a href="https://twitter.com/futureidentity">@futureidentity</a> So, did you ever buy that right-handed beard brush? <a href="https://twitter.com/hashtag/PeakHipster?src=hash">#PeakHipster</a> <a href="https://twitter.com/hashtag/Sinister?src=hash">#Sinister</a> <a href="https://t.co/kESqmUooNk">https://t.co/kESqmUooNk</a> <a href="https://twitter.com/hashtag/CISNOLA?src=hash">#CISNOLA</a> cc <a href="https://twitter.com/mfratto">@mfratto</a></div>&mdash; Richard Veryard (@richardveryard) <a href="https://twitter.com/richardveryard/status/740614064301342720">June 8, 2016</a></blockquote><br><hr><br>Kyle Chayka, <a href="http://www.independent.co.uk/life-style/gadgets-and-tech/features/face-recognition-software-is-this-the-end-of-anonymity-for-all-of-us-9278697.html">Face-recognition software: Is this the end of anonymity for all of us?</a> (Independent, 23 April 2014)     <br><br>Chris Frey, <a href="https://www.theguardian.com/cities/2016/mar/03/revealed-facial-recognition-software-infiltrating-cities-saks-toronto">Revealed: how facial recognition has invaded shops &ndash; and your privacy</a> (Guardian, 3 March 2016)<br><br>Rebecca Ley, <a href="http://www.dailymail.co.uk/femail/article-3868712/Would-dare-ask-computer-old-look-Eight-brave-women-try-terrifyingly-simple-new-internet-craze.html">Would YOU &nbsp;dare ask a computer how old you look? Eight brave women try out the terrifyingly simple new internet craze</a> (Daily Mail, 25 October 2016)<br><br><br>Related Post: <a href="https://rvsoapbox.blogspot.co.uk/2018/01/another-20-million-faces.html">Another 20 million faces</a> (January 2018)<br><br><span><br></span><span><span>TotalData&trade; is a trademark of Reply Ltd. All rights reserved</span> </span><br><div><br></div>]]></summary>
    <content type="html"><![CDATA[It should be pretty obvious why Microsoft wants 85 million faces. According to its privacy policy<br><blockquote>Microsoft uses the data we collect to provide you the products we offer,  which includes using data to improve and personalize your experiences.  We also may use the data to communicate with you, for example, informing  you about your account, security updates and product information. And  we use data to help show more relevant ads, whether in our own products  like MSN and Bing, or in products offered by third parties. (retrieved 25 October 2016)</blockquote>Facial recognition software is big business, and high quality image data is clearly a valuable asset.<br><br>But why would 85 million people go along with this? I guess they thought they were just playing a game, and didn't think of it in terms of donating their personal data to Microsoft. The bait was to persuade people to find out how old the software thought they were. <br><br>The Daily Mail persuaded a number of female celebrities to test the software, and printed the results in today's paper.<br><blockquote data-lang="en"><div dir="ltr" lang="en">Computer"tell yr age" programme on my face puts me 69 <a href="https://t.co/EhEog5LQcN">https://t.co/EhEog5LQcN</a> Haha!But why are those judged younger than they are so pleased</div>&mdash; mary beard (@wmarybeard) <a href="https://twitter.com/wmarybeard/status/790881620563783680">October 25, 2016</a></blockquote><br>Talking of beards ...<br><blockquote data-lang="en"><div dir="ltr" lang="en">. <a href="https://twitter.com/futureidentity">@futureidentity</a> If we ever reach peak data, advertisers will check photos before advertising beard accessories <a href="https://twitter.com/hashtag/personalization?src=hash">#personalization</a> <a href="https://twitter.com/hashtag/TotalData?src=hash">#TotalData</a></div>&mdash; Richard Veryard (@richardveryard) <a href="https://twitter.com/richardveryard/status/715905179959369728">April 1, 2016</a></blockquote><br><blockquote data-lang="en"><div dir="ltr" lang="en">. <a href="https://twitter.com/futureidentity">@futureidentity</a> So, did you ever buy that right-handed beard brush? <a href="https://twitter.com/hashtag/PeakHipster?src=hash">#PeakHipster</a> <a href="https://twitter.com/hashtag/Sinister?src=hash">#Sinister</a> <a href="https://t.co/kESqmUooNk">https://t.co/kESqmUooNk</a> <a href="https://twitter.com/hashtag/CISNOLA?src=hash">#CISNOLA</a> cc <a href="https://twitter.com/mfratto">@mfratto</a></div>&mdash; Richard Veryard (@richardveryard) <a href="https://twitter.com/richardveryard/status/740614064301342720">June 8, 2016</a></blockquote><br><hr><br>Kyle Chayka, <a href="http://www.independent.co.uk/life-style/gadgets-and-tech/features/face-recognition-software-is-this-the-end-of-anonymity-for-all-of-us-9278697.html">Face-recognition software: Is this the end of anonymity for all of us?</a> (Independent, 23 April 2014)     <br><br>Chris Frey, <a href="https://www.theguardian.com/cities/2016/mar/03/revealed-facial-recognition-software-infiltrating-cities-saks-toronto">Revealed: how facial recognition has invaded shops &ndash; and your privacy</a> (Guardian, 3 March 2016)<br><br>Rebecca Ley, <a href="http://www.dailymail.co.uk/femail/article-3868712/Would-dare-ask-computer-old-look-Eight-brave-women-try-terrifyingly-simple-new-internet-craze.html">Would YOU &nbsp;dare ask a computer how old you look? Eight brave women try out the terrifyingly simple new internet craze</a> (Daily Mail, 25 October 2016)<br><br><br>Related Post: <a href="https://rvsoapbox.blogspot.co.uk/2018/01/another-20-million-faces.html">Another 20 million faces</a> (January 2018)<br><br><span><br></span><span><span>TotalData&trade; is a trademark of Reply Ltd. All rights reserved</span> </span><br><div><br></div>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-7794810704259587309</id>
    <title type="html">Why does my bank need more personal data?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2016-08-07T13:33:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2016/08/why-does-my-bank-need-more-personal-data.html"/>
    <summary type="html"><![CDATA[I recently went into a High Street branch of my bank and moved a bit of money between accounts. I could have done more, but I didn't have any additional forms of identification with me.<br><br>At the end, the cashier asked me for my nationality. British, as it happens. Why do you want to know? The cashier explained that this enabled a security control: if I ever bring my passport into a branch as a form of identification, the system can check that my passport matches my declared nationality.<br><br>Really? Really? If this is really a security measure, it's a pretty feeble one. Does my bank imagine I'm going to say I'm British and then produce a North Korean passport? Like a James Bond film?<br><br>After she had explained how the bank would use my nationality data, she then asked for my National Insurance number. I declined, choosing not to quiz her any further, and left the branch planning to write a stiff letter to the head of data protection at the bank's head office. <br><br>As a data expert, I am always a little suspicious of corporate motives for data collection. So the thought did occur to me that my bank might be planning to use my personal data for some purpose other than that stated.<br><br>Of course, my bank is perfectly entitled to collect data for marketing purposes, with my consent. But in this case, I was explicitly told that the data were being collected for a very narrowly defined security purpose. <br><br>So there are two possibilities. Either my bank doesn't understand security, or it doesn't understand data protection. (Of course there will be individuals who understand these things, but the bank as an organization appears to have failed to embed this understanding into its systems and working practices.) I shall be happy to provide advice and guidance on these topics.<br><br><br><br>]]></summary>
    <content type="html"><![CDATA[I recently went into a High Street branch of my bank and moved a bit of money between accounts. I could have done more, but I didn't have any additional forms of identification with me.<br><br>At the end, the cashier asked me for my nationality. British, as it happens. Why do you want to know? The cashier explained that this enabled a security control: if I ever bring my passport into a branch as a form of identification, the system can check that my passport matches my declared nationality.<br><br>Really? Really? If this is really a security measure, it's a pretty feeble one. Does my bank imagine I'm going to say I'm British and then produce a North Korean passport? Like a James Bond film?<br><br>After she had explained how the bank would use my nationality data, she then asked for my National Insurance number. I declined, choosing not to quiz her any further, and left the branch planning to write a stiff letter to the head of data protection at the bank's head office. <br><br>As a data expert, I am always a little suspicious of corporate motives for data collection. So the thought did occur to me that my bank might be planning to use my personal data for some purpose other than that stated.<br><br>Of course, my bank is perfectly entitled to collect data for marketing purposes, with my consent. But in this case, I was explicitly told that the data were being collected for a very narrowly defined security purpose. <br><br>So there are two possibilities. Either my bank doesn't understand security, or it doesn't understand data protection. (Of course there will be individuals who understand these things, but the bank as an organization appears to have failed to embed this understanding into its systems and working practices.) I shall be happy to provide advice and guidance on these topics.<br><br><br><br>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-7213063186121461707</id>
    <title type="html">New White Paper - TotalData™</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2016-08-07T11:30:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2016/08/new-white-paper-totaldata.html"/>
    <summary type="html"><![CDATA[My latest white paper for @GlueReply has been posted on the Reply website.<br><br><!--[if gte mso 9]><xml> <o:OfficeDocumentSettings>  <o:RelyOnVML/>  <o:AllowPNG/> </o:OfficeDocumentSettings></xml><![endif]--><br><!--[if gte mso 9]><xml> <w:WordDocument>  <w:View>Normal</w:View>  <w:Zoom>0</w:Zoom>  <w:TrackMoves/>  <w:TrackFormatting/>  <w:PunctuationKerning/>  <w:ValidateAgainstSchemas/>  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>  <w:DoNotPromoteQF/>  <w:LidThemeOther>IT</w:LidThemeOther>  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>  <w:Compatibility>   <w:BreakWrappedTables/>   <w:SnapToGridInCell/>   <w:WrapTextWithPunct/>   <w:UseAsianBreakRules/>   <w:DontGrowAutofit/>   <w:SplitPgBreakAndParaMark/>   <w:EnableOpenTypeKerning/>   <w:DontFlipMirrorIndents/>   <w:OverrideTableStyleHps/>  </w:Compatibility>  <m:mathPr>   <m:mathFont m:val="Cambria Math"/>   <m:brkBin m:val="before"/>   <m:brkBinSub m:val="--"/>   <m:smallFrac m:val="off"/>   <m:dispDef/>   <m:lMargin m:val="0"/>   <m:rMargin m:val="0"/>   <m:defJc m:val="centerGroup"/>   <m:wrapIndent m:val="1440"/>   <m:intLim m:val="subSup"/>   <m:naryLim m:val="undOvr"/>  </m:mathPr></w:WordDocument></xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"   DefSemiHidden="false" DefQFormat="false" DefPriority="99"   LatentStyleCount="371">  <w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>  <w:LsdException Locked="false" Priority="0" QFormat="true" Name="heading 1"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 6"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 7"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 8"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 9"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 1"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 2"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 3"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 4"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 5"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 6"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 7"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 8"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 9"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Normal Indent"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="footnote text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="annotation text"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="header"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="footer"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index heading"/>  <w:LsdException Locked="false" Priority="35" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="caption"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="table of figures"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="envelope address"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="envelope return"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="footnote reference"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="annotation reference"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="line number"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="page number"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="endnote reference"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="endnote text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="table of authorities"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="macro"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="toa heading"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 5"/>  <w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Closing"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Signature"/>  <w:LsdException Locked="false" Priority="1" SemiHidden="true"    UnhideWhenUsed="true" Name="Default Paragraph Font"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text Indent"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Message Header"/>  <w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Salutation"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Date"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text First Indent"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text First Indent 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Note Heading"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text Indent 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text Indent 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Block Text"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="Hyperlink"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="FollowedHyperlink"/>  <w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>  <w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Document Map"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Plain Text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="E-mail Signature"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Top of Form"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Bottom of Form"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Normal (Web)"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Acronym"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Address"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Cite"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Code"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Definition"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Keyboard"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Preformatted"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Sample"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Typewriter"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Variable"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Normal Table"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="annotation subject"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="No List"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Outline List 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Outline List 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Outline List 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Simple 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Simple 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Simple 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Colorful 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Colorful 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Colorful 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 6"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 7"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 8"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 6"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 7"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 8"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table 3D effects 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table 3D effects 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table 3D effects 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Contemporary"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Elegant"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Professional"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Subtle 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Subtle 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Web 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Web 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Web 3"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="Balloon Text"/>  <w:LsdException Locked="false" Priority="39" Name="Table Grid"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Theme"/>  <w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>  <w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading"/>  <w:LsdException Locked="false" Priority="61" Name="Light List"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>  <w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>  <w:LsdException Locked="false" Priority="34" QFormat="true"    Name="List Paragraph"/>  <w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>  <w:LsdException Locked="false" Priority="30" QFormat="true"    Name="Intense Quote"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>  <w:LsdException Locked="false" Priority="19" QFormat="true"    Name="Subtle Emphasis"/>  <w:LsdException Locked="false" Priority="21" QFormat="true"    Name="Intense Emphasis"/>  <w:LsdException Locked="false" Priority="31" QFormat="true"    Name="Subtle Reference"/>  <w:LsdException Locked="false" Priority="32" QFormat="true"    Name="Intense Reference"/>  <w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>  <w:LsdException Locked="false" Priority="37" SemiHidden="true"    UnhideWhenUsed="true" Name="Bibliography"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>  <w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>  <w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>  <w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>  <w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>  <w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>  <w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>  <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>  <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>  <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 1"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 2"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 3"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 4"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 5"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 6"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 6"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 6"/>  <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>  <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>  <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 1"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 2"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 3"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 4"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 5"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 6"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 6"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 6"/> </w:LatentStyles></xml><![endif]--><!--[if gte mso 10]><style> /* Style Definitions */  table.MsoNormalTable  {mso-style-name:"Table Normal";  mso-tstyle-rowband-size:0;  mso-tstyle-colband-size:0;  mso-style-noshow:yes;  mso-style-priority:99;  mso-style-parent:"";  mso-padding-alt:0cm 5.4pt 0cm 5.4pt;  mso-para-margin:0cm;  mso-para-margin-bottom:.0001pt;  mso-pagination:widow-orphan;  font-size:10.0pt;  font-family:"Times",serif;  mso-bidi-font-family:"Times New Roman";  mso-ansi-language:IT;  mso-fareast-language:IT;} </style><![endif]--><span>It outlines four dimensions of TotalData</span><span>&trade; - reach, richness, assurance and agility - and presents a Value Chain from Raw Data to the Data-Fueled Business.</span><br><br><a href="https://4.bp.blogspot.com/-VhZwsmWtpz4/V6cXV1C5KtI/AAAAAAAAAIM/HwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB/s1600/TotalData.png" imageanchor="1"><img border="0" height="181" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-VhZwsmWtpz4%2FV6cXV1C5KtI%2FAAAAAAAAAIM%2FHwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB%2Fs400%2FTotalData.png&width=540&mix=29cb9-TotalData" width="400"></a><a href="https://4.bp.blogspot.com/-dvySRhJFyHI/V6cYjy3tbpI/AAAAAAAAAIY/Squ0lcXSJCQTa9_tVNptzJnCb_ps7Z5-wCLcB/s1600/TotalDataValueChain.png"><img border="0" height="200" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-dvySRhJFyHI%2FV6cYjy3tbpI%2FAAAAAAAAAIY%2FSqu0lcXSJCQTa9_tVNptzJnCb_ps7Z5-wCLcB%2Fs200%2FTotalDataValueChain.png&width=540&mix=29cb9-TotalData" width="136"></a><br><br>TotalData&trade;: Start making better use of Data (<a href="http://www.reply.eu/en/topics/big-data-and-analytics/totaldata">html</a>) (<a href="http://www.reply.eu/en/topics/big-data-and-analytics/Shared%20Documents/Total-Data_eng.pdf">pdf</a>)<br><br>(Now I need to write some more detailed stuff, based on a few client projects.)<br><br><br><span><br></span><span><span>TotalData&trade; is a trademark of Reply Ltd. All rights reserved</span> </span>]]></summary>
    <content type="html"><![CDATA[My latest white paper for @GlueReply has been posted on the Reply website.<br><br><!--[if gte mso 9]><xml> <o:OfficeDocumentSettings>  <o:RelyOnVML/>  <o:AllowPNG/> </o:OfficeDocumentSettings></xml><![endif]--><br><!--[if gte mso 9]><xml> <w:WordDocument>  <w:View>Normal</w:View>  <w:Zoom>0</w:Zoom>  <w:TrackMoves/>  <w:TrackFormatting/>  <w:PunctuationKerning/>  <w:ValidateAgainstSchemas/>  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>  <w:DoNotPromoteQF/>  <w:LidThemeOther>IT</w:LidThemeOther>  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>  <w:Compatibility>   <w:BreakWrappedTables/>   <w:SnapToGridInCell/>   <w:WrapTextWithPunct/>   <w:UseAsianBreakRules/>   <w:DontGrowAutofit/>   <w:SplitPgBreakAndParaMark/>   <w:EnableOpenTypeKerning/>   <w:DontFlipMirrorIndents/>   <w:OverrideTableStyleHps/>  </w:Compatibility>  <m:mathPr>   <m:mathFont m:val="Cambria Math"/>   <m:brkBin m:val="before"/>   <m:brkBinSub m:val="--"/>   <m:smallFrac m:val="off"/>   <m:dispDef/>   <m:lMargin m:val="0"/>   <m:rMargin m:val="0"/>   <m:defJc m:val="centerGroup"/>   <m:wrapIndent m:val="1440"/>   <m:intLim m:val="subSup"/>   <m:naryLim m:val="undOvr"/>  </m:mathPr></w:WordDocument></xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"   DefSemiHidden="false" DefQFormat="false" DefPriority="99"   LatentStyleCount="371">  <w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>  <w:LsdException Locked="false" Priority="0" QFormat="true" Name="heading 1"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>  <w:LsdException Locked="false" Priority="9" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 6"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 7"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 8"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index 9"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 1"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 2"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 3"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 4"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 5"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 6"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 7"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 8"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" Name="toc 9"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Normal Indent"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="footnote text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="annotation text"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="header"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="footer"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="index heading"/>  <w:LsdException Locked="false" Priority="35" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="caption"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="table of figures"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="envelope address"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="envelope return"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="footnote reference"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="annotation reference"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="line number"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="page number"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="endnote reference"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="endnote text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="table of authorities"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="macro"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="toa heading"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Bullet 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Number 5"/>  <w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Closing"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Signature"/>  <w:LsdException Locked="false" Priority="1" SemiHidden="true"    UnhideWhenUsed="true" Name="Default Paragraph Font"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text Indent"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="List Continue 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Message Header"/>  <w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Salutation"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Date"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text First Indent"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text First Indent 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Note Heading"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text Indent 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Body Text Indent 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Block Text"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="Hyperlink"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="FollowedHyperlink"/>  <w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>  <w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Document Map"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Plain Text"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="E-mail Signature"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Top of Form"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Bottom of Form"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Normal (Web)"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Acronym"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Address"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Cite"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Code"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Definition"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Keyboard"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Preformatted"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Sample"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Typewriter"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="HTML Variable"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Normal Table"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="annotation subject"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="No List"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Outline List 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Outline List 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Outline List 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Simple 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Simple 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Simple 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Classic 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Colorful 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Colorful 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Colorful 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Columns 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 6"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 7"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Grid 8"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 4"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 5"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 6"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 7"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table List 8"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table 3D effects 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table 3D effects 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table 3D effects 3"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Contemporary"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Elegant"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Professional"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Subtle 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Subtle 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Web 1"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Web 2"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Web 3"/>  <w:LsdException Locked="false" Priority="0" SemiHidden="true"    UnhideWhenUsed="true" Name="Balloon Text"/>  <w:LsdException Locked="false" Priority="39" Name="Table Grid"/>  <w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"    Name="Table Theme"/>  <w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>  <w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading"/>  <w:LsdException Locked="false" Priority="61" Name="Light List"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>  <w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>  <w:LsdException Locked="false" Priority="34" QFormat="true"    Name="List Paragraph"/>  <w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>  <w:LsdException Locked="false" Priority="30" QFormat="true"    Name="Intense Quote"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>  <w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>  <w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>  <w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>  <w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>  <w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>  <w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>  <w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>  <w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>  <w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>  <w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>  <w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>  <w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>  <w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>  <w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>  <w:LsdException Locked="false" Priority="19" QFormat="true"    Name="Subtle Emphasis"/>  <w:LsdException Locked="false" Priority="21" QFormat="true"    Name="Intense Emphasis"/>  <w:LsdException Locked="false" Priority="31" QFormat="true"    Name="Subtle Reference"/>  <w:LsdException Locked="false" Priority="32" QFormat="true"    Name="Intense Reference"/>  <w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>  <w:LsdException Locked="false" Priority="37" SemiHidden="true"    UnhideWhenUsed="true" Name="Bibliography"/>  <w:LsdException Locked="false" Priority="39" SemiHidden="true"    UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>  <w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>  <w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>  <w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>  <w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>  <w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>  <w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>  <w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>  <w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>  <w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 1"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 2"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 3"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 4"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 5"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="46"    Name="Grid Table 1 Light Accent 6"/>  <w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>  <w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>  <w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>  <w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>  <w:LsdException Locked="false" Priority="51"    Name="Grid Table 6 Colorful Accent 6"/>  <w:LsdException Locked="false" Priority="52"    Name="Grid Table 7 Colorful Accent 6"/>  <w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>  <w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>  <w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 1"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 1"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 2"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 2"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 3"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 3"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 4"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 4"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 5"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 5"/>  <w:LsdException Locked="false" Priority="46"    Name="List Table 1 Light Accent 6"/>  <w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>  <w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>  <w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>  <w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>  <w:LsdException Locked="false" Priority="51"    Name="List Table 6 Colorful Accent 6"/>  <w:LsdException Locked="false" Priority="52"    Name="List Table 7 Colorful Accent 6"/> </w:LatentStyles></xml><![endif]--><!--[if gte mso 10]><style> /* Style Definitions */  table.MsoNormalTable  {mso-style-name:"Table Normal";  mso-tstyle-rowband-size:0;  mso-tstyle-colband-size:0;  mso-style-noshow:yes;  mso-style-priority:99;  mso-style-parent:"";  mso-padding-alt:0cm 5.4pt 0cm 5.4pt;  mso-para-margin:0cm;  mso-para-margin-bottom:.0001pt;  mso-pagination:widow-orphan;  font-size:10.0pt;  font-family:"Times",serif;  mso-bidi-font-family:"Times New Roman";  mso-ansi-language:IT;  mso-fareast-language:IT;} </style><![endif]--><span>It outlines four dimensions of TotalData</span><span>&trade; - reach, richness, assurance and agility - and presents a Value Chain from Raw Data to the Data-Fueled Business.</span><br><br><a href="https://4.bp.blogspot.com/-VhZwsmWtpz4/V6cXV1C5KtI/AAAAAAAAAIM/HwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB/s1600/TotalData.png" imageanchor="1"><img border="0" height="181" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-VhZwsmWtpz4%2FV6cXV1C5KtI%2FAAAAAAAAAIM%2FHwQrViAcvjEKcgmdx97RxsjWNVBot2TJQCLcB%2Fs400%2FTotalData.png&width=540&mix=29cb9-TotalData" width="400"></a><a href="https://4.bp.blogspot.com/-dvySRhJFyHI/V6cYjy3tbpI/AAAAAAAAAIY/Squ0lcXSJCQTa9_tVNptzJnCb_ps7Z5-wCLcB/s1600/TotalDataValueChain.png"><img border="0" height="200" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F4.bp.blogspot.com%2F-dvySRhJFyHI%2FV6cYjy3tbpI%2FAAAAAAAAAIY%2FSqu0lcXSJCQTa9_tVNptzJnCb_ps7Z5-wCLcB%2Fs200%2FTotalDataValueChain.png&width=540&mix=29cb9-TotalData" width="136"></a><br><br>TotalData&trade;: Start making better use of Data (<a href="http://www.reply.eu/en/topics/big-data-and-analytics/totaldata">html</a>) (<a href="http://www.reply.eu/en/topics/big-data-and-analytics/Shared%20Documents/Total-Data_eng.pdf">pdf</a>)<br><br>(Now I need to write some more detailed stuff, based on a few client projects.)<br><br><br><span><br></span><span><span>TotalData&trade; is a trademark of Reply Ltd. All rights reserved</span> </span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-3548667937394415722</id>
    <title type="html">From Networked BI to Collaborative BI</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2016-04-03T08:30:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2016/04/networked-bi.html"/>
    <summary type="html"><![CDATA[Back in September 2005, I commented on some material  by MicroStrategy identifying Five Types of Business Intelligence. I  arranged these five types into a 2x2 matrix, and commented on the fact  that the top right quadrant was then empty.&nbsp; <br><br><br><div><a href="https://1.bp.blogspot.com/-qacariekOj4/VwBP6CeeDyI/AAAAAAAAAGM/v737S4xP7MI6cDmdLAoNYLPhUhwYh9GeQ/s1600/image003.png"><img border="0" height="227" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F1.bp.blogspot.com%2F-qacariekOj4%2FVwBP6CeeDyI%2FAAAAAAAAAGM%2Fv737S4xP7MI6cDmdLAoNYLPhUhwYh9GeQ%2Fs320%2Fimage003.png&width=540&mix=29cb9-TotalData" width="320"></a></div><br>&nbsp; <br>The  Cloud BI and analytics vendor Birst has now produced a similar matrix  to explain what it is calling Networked BI, placing it in the top  right quadrant. Gartner has been talking about Mode&nbsp;1 (conventional) and  Mode&nbsp;2 (self-service) approaches to BI, so Birst is calling this  Mode&nbsp;3.<br><br><br><div><a href="https://3.bp.blogspot.com/-PF1fDAt0apo/VxkAQvvRf_I/AAAAAAAAAGk/PduvsfOqzXYvKZsTK5vvEatmhatV3qw0wCKgB/s1600/BImatrix2.png" imageanchor="1"><img border="0" height="162" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F3.bp.blogspot.com%2F-PF1fDAt0apo%2FVxkAQvvRf_I%2FAAAAAAAAAGk%2FPduvsfOqzXYvKZsTK5vvEatmhatV3qw0wCKgB%2Fs320%2FBImatrix2.png&width=540&mix=29cb9-TotalData" width="320"></a></div><div><a href="https://2.bp.blogspot.com/-dOwaYru6ogQ/VwBRothTpXI/AAAAAAAAAGU/dknbKlG62k4M4Zfazo6oy28rBQ_YtZ1fA/s1600/image004.png"><br></a></div><br>While  there are some important technological advances and enablers in the  Mode 3 quadrant, I also see it as a move towards Collaborative BI, which  is about the collective ability of the organization to design  experiments, to generate analytical insight, to interpret results, and  to mobilize action and improvement. This means not only sharing the data, but also sharing the insight and the actioning of the insight. Thus we are not only  driving data and analytics to the edge of the organization, but also  developing the collective intelligence of the organization to use data  and analytics in an agile yet joined-up way. <br><br>I first mentioned Collaborative BI on my blog during 2005, and discussed it  further in my article for the CBDI Journal in October 2005. The concept  started to gather momentum a few years later, thanks to Gartner, which  predicted the development of collaborative decision-making in 2009, as  well as some interesting work by Wayne Eckerson. Also around this time,  there were some promising developments by a few BI vendors, including  arcplan and TIBCO. But internet searches for the concept are dominated by material between 2009 and 2012, and things seem to have gone quiet recently.<br><br><hr>Previous posts in this series<br><br><a href="http://rvsoapbox.blogspot.co.uk/2005/09/service-oriented-business-intelligence_22.htm">Service-Oriented Business Intelligence</a> (September 2005)<br><a href="http://rvsoapbox.blogspot.co.uk/2009/05/from-business-intelligence-to.html">From Business Intelligence to Organizational Intelligence</a> (May 2009)<br><a href="http://rvsoftware.blogspot.co.uk/2011/03/tibco-platform-for-organizational.html">TIBCO Platform for Organizational Intelligence</a> (March 2011)<br><br><br>Other sources<br><br><a href="http://www.gartner.com/newsroom/id/856714">Gartner Reveals Five Business Intelligence Predictions for 2009 and Beyond</a> (Gartner, January 2009). Dave Linthicum, <a href="http://www.ebizq.net/blogs/linthicum/2009/05/gartner_reveals_five_business.php">Let's See How Gartner is Doing</a> (ebizQ, May 2009)<br><br>Chris Middleton, <a href="http://www.computerweekly.com/feature/Business-intelligence-Collaborative-decision-making">Business Intelligence: Collaborative Decision-Making</a> (Computer Weekly, July 2009)<br><br>Ian Bertram, <a href="http://www-07.ibm.com/my/events/isbts/lotusiod/pdf/Collaborative_Decision-Making_Platforms-A_New_Way_to_Make_Decisions_Gartner_Ian_Bertram.pdf">Collaborative Decision-Making Platforms</a> (Gartner 2011)<br><br>Wayne Eckerson, <a href="http://www.beyeresearch.com/study/15977">Collaborative Business Intelligence: Optimizing the Process of Making Decisions</a> (April 2012)<br><br>Monique Morgan, <a href="http://www.arcplan.com/en/blog/2012/04/collaborative-bi-today-tomorrow/">Collaborative BI: Today and Tomorrow</a> (arcplan, April 2012)<br>Tiemo Winterkamp, <a href="http://www.arcplan.com/en/blog/2012/04/top-5-collaborative-bi-solution-criteria/">Top 5 Collaborative BI Solution Criteria</a> (arcplan, April 2012)<br><br>Cliff Saran, <a href="http://www.computerweekly.com/news/2240241926/Prepare-for-two-modes-of-business-intelligence-says-Gartner">Prepare for two modes of business intelligence, says Gartner</a> (Computer Weekly, March 2015) <br><br><a href="https://www.birst.com/wp-content/uploads/2016/03/Birst_NetworkedBI_WhitePaper.pdf">The Future of BI is Networked</a> (Birst, March 2016)<br><br><br><span>Updated 21 April 2016 (image corrected) </span>]]></summary>
    <content type="html"><![CDATA[Back in September 2005, I commented on some material  by MicroStrategy identifying Five Types of Business Intelligence. I  arranged these five types into a 2x2 matrix, and commented on the fact  that the top right quadrant was then empty.&nbsp; <br><br><br><div><a href="https://1.bp.blogspot.com/-qacariekOj4/VwBP6CeeDyI/AAAAAAAAAGM/v737S4xP7MI6cDmdLAoNYLPhUhwYh9GeQ/s1600/image003.png"><img border="0" height="227" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F1.bp.blogspot.com%2F-qacariekOj4%2FVwBP6CeeDyI%2FAAAAAAAAAGM%2Fv737S4xP7MI6cDmdLAoNYLPhUhwYh9GeQ%2Fs320%2Fimage003.png&width=540&mix=29cb9-TotalData" width="320"></a></div><br>&nbsp; <br>The  Cloud BI and analytics vendor Birst has now produced a similar matrix  to explain what it is calling Networked BI, placing it in the top  right quadrant. Gartner has been talking about Mode&nbsp;1 (conventional) and  Mode&nbsp;2 (self-service) approaches to BI, so Birst is calling this  Mode&nbsp;3.<br><br><br><div><a href="https://3.bp.blogspot.com/-PF1fDAt0apo/VxkAQvvRf_I/AAAAAAAAAGk/PduvsfOqzXYvKZsTK5vvEatmhatV3qw0wCKgB/s1600/BImatrix2.png" imageanchor="1"><img border="0" height="162" src="http://chimpfeedr.com/img/?url=https%3A%2F%2F3.bp.blogspot.com%2F-PF1fDAt0apo%2FVxkAQvvRf_I%2FAAAAAAAAAGk%2FPduvsfOqzXYvKZsTK5vvEatmhatV3qw0wCKgB%2Fs320%2FBImatrix2.png&width=540&mix=29cb9-TotalData" width="320"></a></div><div><a href="https://2.bp.blogspot.com/-dOwaYru6ogQ/VwBRothTpXI/AAAAAAAAAGU/dknbKlG62k4M4Zfazo6oy28rBQ_YtZ1fA/s1600/image004.png"><br></a></div><br>While  there are some important technological advances and enablers in the  Mode 3 quadrant, I also see it as a move towards Collaborative BI, which  is about the collective ability of the organization to design  experiments, to generate analytical insight, to interpret results, and  to mobilize action and improvement. This means not only sharing the data, but also sharing the insight and the actioning of the insight. Thus we are not only  driving data and analytics to the edge of the organization, but also  developing the collective intelligence of the organization to use data  and analytics in an agile yet joined-up way. <br><br>I first mentioned Collaborative BI on my blog during 2005, and discussed it  further in my article for the CBDI Journal in October 2005. The concept  started to gather momentum a few years later, thanks to Gartner, which  predicted the development of collaborative decision-making in 2009, as  well as some interesting work by Wayne Eckerson. Also around this time,  there were some promising developments by a few BI vendors, including  arcplan and TIBCO. But internet searches for the concept are dominated by material between 2009 and 2012, and things seem to have gone quiet recently.<br><br><hr>Previous posts in this series<br><br><a href="http://rvsoapbox.blogspot.co.uk/2005/09/service-oriented-business-intelligence_22.htm">Service-Oriented Business Intelligence</a> (September 2005)<br><a href="http://rvsoapbox.blogspot.co.uk/2009/05/from-business-intelligence-to.html">From Business Intelligence to Organizational Intelligence</a> (May 2009)<br><a href="http://rvsoftware.blogspot.co.uk/2011/03/tibco-platform-for-organizational.html">TIBCO Platform for Organizational Intelligence</a> (March 2011)<br><br><br>Other sources<br><br><a href="http://www.gartner.com/newsroom/id/856714">Gartner Reveals Five Business Intelligence Predictions for 2009 and Beyond</a> (Gartner, January 2009). Dave Linthicum, <a href="http://www.ebizq.net/blogs/linthicum/2009/05/gartner_reveals_five_business.php">Let's See How Gartner is Doing</a> (ebizQ, May 2009)<br><br>Chris Middleton, <a href="http://www.computerweekly.com/feature/Business-intelligence-Collaborative-decision-making">Business Intelligence: Collaborative Decision-Making</a> (Computer Weekly, July 2009)<br><br>Ian Bertram, <a href="http://www-07.ibm.com/my/events/isbts/lotusiod/pdf/Collaborative_Decision-Making_Platforms-A_New_Way_to_Make_Decisions_Gartner_Ian_Bertram.pdf">Collaborative Decision-Making Platforms</a> (Gartner 2011)<br><br>Wayne Eckerson, <a href="http://www.beyeresearch.com/study/15977">Collaborative Business Intelligence: Optimizing the Process of Making Decisions</a> (April 2012)<br><br>Monique Morgan, <a href="http://www.arcplan.com/en/blog/2012/04/collaborative-bi-today-tomorrow/">Collaborative BI: Today and Tomorrow</a> (arcplan, April 2012)<br>Tiemo Winterkamp, <a href="http://www.arcplan.com/en/blog/2012/04/top-5-collaborative-bi-solution-criteria/">Top 5 Collaborative BI Solution Criteria</a> (arcplan, April 2012)<br><br>Cliff Saran, <a href="http://www.computerweekly.com/news/2240241926/Prepare-for-two-modes-of-business-intelligence-says-Gartner">Prepare for two modes of business intelligence, says Gartner</a> (Computer Weekly, March 2015) <br><br><a href="https://www.birst.com/wp-content/uploads/2016/03/Birst_NetworkedBI_WhitePaper.pdf">The Future of BI is Networked</a> (Birst, March 2016)<br><br><br><span>Updated 21 April 2016 (image corrected) </span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-2411144945875239375</id>
    <title type="html">Predictive and Real-Time Analytics</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2015-11-28T13:01:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2015/11/predictive-and-real-time-analytics.html"/>
    <summary type="html"><![CDATA[I shall be chairing the @<a href="https://twitter.com/UNICOMSeminars/status/670222050510938112">UNICOMSeminars</a> Data Analytics conference next week. <a href="http://conferences.unicom.co.uk/data-analytics-business-value/">Exploring the Business Value of Predictive and Real-Time Analytics</a> (London, 2 December 2015) <br><br>A lot of the obvious applications of real-time analytics are in fraud detection and predictive maintenance. I shall be talking about some of the things I&rsquo;ve been doing recently in the retail and  consumer sector, using rich consumer data to drive real-time  personalized engagement with the consumer across multiple touchpoints.  We have been exploring ways to combine real-time analysis of the consumer&rsquo;s  current state (e.g. current location, what products they are currently  looking at, readiness to buy, etc.) with a rich understanding of what  one might call the consumer&rsquo;s &ldquo;purchasing genes&rdquo; &ndash; for example, do they  like to spend a long time reviewing alternative products before  purchasing, do they like to wait for a special offer or voucher before  buying, or on the other hand do they like to be the first in their  social network to have a given product. This is a lot more complex than  simply putting them into a fixed number of &ldquo;consumer segments&rdquo;. <br><br>Based on this analysis, it is possible to select an appropriate &ldquo;next action&rdquo; &ndash; for example, selecting the appropriate  banner to display to the consumer when visiting the website, or the  right topic of conversation for a human customer services agent.<br><br>Thus predictive analytics are  helping retail as it moves from omnichannel commerce (which joins up the buying transaction  between the online and the physical world) to omnichannel engagement  (which joins up all aspect of the relationship with the consumer). <br><br><table border="1" cellpadding="4" cellspacing="4"><tbody><tr><td valign="top"><b>Omnichannel Commerce</b><br>(Systems of Record)<br><br><i>joins up the buying transaction between the online and the physical world</i> </td>      <td valign="top"><b>Omnichannel Marketing</b><br>(Systems of Engagement)<br><br><i>joins up all aspects of the relationship with the consumer</i></td>    </tr></tbody></table><br>Given the large volumes of data involved, and the  reliance on legacy systems to produce and process the data, we are not  yet seeing this analysis being completely done in real-time. However,  there are some critical factors that have to be done in real-time. For  example, as soon as the consumer buys something, our clients want to  stop trying to sell it, and move to a post-sales scenario. (In  comparison, even the great Google is still showing me advertisements  based on what I was browsing three weeks ago. Fail!) <br><br>Over the next couple of years, as the technology gets  better, the data scientists get even smarter, and the marketing people  get more sophisticated, we may expect an increasing proportion of the  analysis to be done in real-time, using machine learning as well as more  sophisticated analytics tools.]]></summary>
    <content type="html"><![CDATA[I shall be chairing the @<a href="https://twitter.com/UNICOMSeminars/status/670222050510938112">UNICOMSeminars</a> Data Analytics conference next week. <a href="http://conferences.unicom.co.uk/data-analytics-business-value/">Exploring the Business Value of Predictive and Real-Time Analytics</a> (London, 2 December 2015) <br><br>A lot of the obvious applications of real-time analytics are in fraud detection and predictive maintenance. I shall be talking about some of the things I&rsquo;ve been doing recently in the retail and  consumer sector, using rich consumer data to drive real-time  personalized engagement with the consumer across multiple touchpoints.  We have been exploring ways to combine real-time analysis of the consumer&rsquo;s  current state (e.g. current location, what products they are currently  looking at, readiness to buy, etc.) with a rich understanding of what  one might call the consumer&rsquo;s &ldquo;purchasing genes&rdquo; &ndash; for example, do they  like to spend a long time reviewing alternative products before  purchasing, do they like to wait for a special offer or voucher before  buying, or on the other hand do they like to be the first in their  social network to have a given product. This is a lot more complex than  simply putting them into a fixed number of &ldquo;consumer segments&rdquo;. <br><br>Based on this analysis, it is possible to select an appropriate &ldquo;next action&rdquo; &ndash; for example, selecting the appropriate  banner to display to the consumer when visiting the website, or the  right topic of conversation for a human customer services agent.<br><br>Thus predictive analytics are  helping retail as it moves from omnichannel commerce (which joins up the buying transaction  between the online and the physical world) to omnichannel engagement  (which joins up all aspect of the relationship with the consumer). <br><br><table border="1" cellpadding="4" cellspacing="4"><tbody><tr><td valign="top"><b>Omnichannel Commerce</b><br>(Systems of Record)<br><br><i>joins up the buying transaction between the online and the physical world</i> </td>      <td valign="top"><b>Omnichannel Marketing</b><br>(Systems of Engagement)<br><br><i>joins up all aspects of the relationship with the consumer</i></td>    </tr></tbody></table><br>Given the large volumes of data involved, and the  reliance on legacy systems to produce and process the data, we are not  yet seeing this analysis being completely done in real-time. However,  there are some critical factors that have to be done in real-time. For  example, as soon as the consumer buys something, our clients want to  stop trying to sell it, and move to a post-sales scenario. (In  comparison, even the great Google is still showing me advertisements  based on what I was browsing three weeks ago. Fail!) <br><br>Over the next couple of years, as the technology gets  better, the data scientists get even smarter, and the marketing people  get more sophisticated, we may expect an increasing proportion of the  analysis to be done in real-time, using machine learning as well as more  sophisticated analytics tools.]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-8481215146907640104</id>
    <title type="html">Towards the Internet of Underthings</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2015-11-14T12:11:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2015/11/towards-internet-of-underthings.html"/>
    <summary type="html"><![CDATA[<span>#WearableTech #InternetOfThings </span>Once upon a time, the wires in an undergarment merely provided structural support. Now, people may have all sorts of wires and wireless devices hidden under their clothing. Here are some interesting examples.<br><br><ul><li>The Foxleaf Bra delivers cancer-fighting drugs through the wearer's skin.</li><li>The @<a href="https://twitter.com/tweetingbra/status/453139110077935616">tweetingbra</a> reminds women to examine themselves. (?)</li><li>The Lumo Lift helps improve posture through app-enabled coaching.</li><li>Various manufacturers (including Clothing+, OMsignal and SmartLife) produce health vests and sportswear packed with monitors to track your heart rate, breathing rate and the amount of calories you've burnt. </li></ul><br>We are now encouraged to account for everything we do: footsteps, heartbeats, posture. Until recently this kind of micro-attention to oneself was regarded as slightly obsessional, nowadays it seems to be perfectly normal. And of course these data are collected, and sent to the cloud, and turned into someone else's big data. (Good luck with those privacy settings, by the way.)<br><br>If a device is classed as a medical device, it will be subject to various forms of accreditation and regulation. For this reason, many device makers will be careful to avoid any specific medical claims, but devices that offer some health advice are considered a borderline area.<br><br>Another borderline area is hi-tech underpants that protect men from the evil rays allegedly produced by all those wireless devices. Especially the radiation from mobile phones. (Including the Bluetooth that links your underwear to your smartphone.) One brand of underpants that claims to use a mesh of pure silver to create a Faraday cage around the genitals has been banned by the UK Advertising Standards Authority from making any medical claims.<br><br>Or maybe you could just switch the whole lot off.<br><br><br><hr><span><a href="http://www.marketingresearch.org/article/wearable-medical-device-your-future%E2%80%A6is-now">The Wearable Medical Device in Your Future&hellip;Is Now!</a> (Marketing Research Association, 28 April 2015) </span><br><ul></ul><span>Jennie Agg, <a href="http://www.dailymail.co.uk/health/article-2987245/The-hi-tech-bra-helps-beat-breast-cancer-clothes-treat-prevent-illness.html">The hi-tech bra that helps you beat breast cancer - and other clothes that can treat or prevent illness</a> (Daily Mail, 10 March 2015)</span><br><br><span>Sarah Blackman, <a href="http://www.lingerieinsight.com/article-5748-student-designs-cancer-fighting-bra/">Student designs cancer-fighting bra</a> (Lingerie Insight, 10 Feb 2015)&nbsp;</span><br><br><span>Britta O'Boyle, <a href="http://www.pocket-lint.com/news/133184-smartlife-clothing-claims-to-make-sure-you-never-miss-a-beat">SmartLife clothing claims to make sure you never miss a beat</a> (Pocket-Lint, 12 March 2015)&nbsp;</span><br><br><span>Rob Crilly, <a href="http://www.telegraph.co.uk/news/worldnews/northamerica/usa/11178843/Hi-tech-pants-protect-sperm-from-phone-waves.html">Hi-tech pants "protect sperm from phone waves"</a> (Telegraph 22 October 2014)</span><br><br><span>Julie Papanek, <a href="http://techcrunch.com/2015/02/19/how-wearable-startups-can-win-big-in-the-medical-industry/">How Wearable Startups Can Win Big In The Medical Industry</a> (TechCrunch, 19 Feb 2015)</span><br><br><span>Hannah Jane Parkinson, <a href="http://www.theguardian.com/technology/2014/nov/14/lumo-lift-review-posture-tracking-gadget">Lumo Lift review: posture-tracking gadget is a straight shooter</a> (Guardian, 14 November 2014)&nbsp;</span><br><br><span>Helen Popkin, <a href="http://www.nbcnews.com/technology/tweeting-bra-exposed-genuine-support-or-publicity-lift-8C11467042">Tweeting bra exposed: Genuine support or publicity lift?</a> (NBC News 25 October 2013)</span><br><br><span>Meera Senthilingam, <a href="http://edition.cnn.com/2015/05/07/tech/smart-clothes-track-your-health/">How a high-tech bra could be your next doctor</a> (CNN, 11 May 2015)</span><br><br><span>Brendan Seibel, <a href="http://www.wired.com/2010/04/gallery-underwear/">High-Tech Underwear for Adventurous Geeks</a> (21 April 2010)</span><br><br><span>Mark Sweney, <a href="http://www.theguardian.com/media/2014/aug/13/underwear-brand-ad-banned-wireless-armoursir-richard-branson">Hi-tech underwear advert banned</a> (Guardian 13 August 2014)</span><br><br><span><span>Dan Sung, <a href="http://www.wareable.com/wearable-tech/world-cancer-day-foxleaf-real-wonderbra-739">World Cancer Day - The Real Wonderbra</a> (Wearable, 14 Feb 2015)&nbsp;&nbsp;</span></span><br><br><span><br></span><span>Related Posts <a href="http://rvsoftware.blogspot.co.uk/2014/12/have-you-got-big-data-in-your-underwear.html">Have you got big data in your underwear</a> (December 2014)</span>]]></summary>
    <content type="html"><![CDATA[<span>#WearableTech #InternetOfThings </span>Once upon a time, the wires in an undergarment merely provided structural support. Now, people may have all sorts of wires and wireless devices hidden under their clothing. Here are some interesting examples.<br><br><ul><li>The Foxleaf Bra delivers cancer-fighting drugs through the wearer's skin.</li><li>The @<a href="https://twitter.com/tweetingbra/status/453139110077935616">tweetingbra</a> reminds women to examine themselves. (?)</li><li>The Lumo Lift helps improve posture through app-enabled coaching.</li><li>Various manufacturers (including Clothing+, OMsignal and SmartLife) produce health vests and sportswear packed with monitors to track your heart rate, breathing rate and the amount of calories you've burnt. </li></ul><br>We are now encouraged to account for everything we do: footsteps, heartbeats, posture. Until recently this kind of micro-attention to oneself was regarded as slightly obsessional, nowadays it seems to be perfectly normal. And of course these data are collected, and sent to the cloud, and turned into someone else's big data. (Good luck with those privacy settings, by the way.)<br><br>If a device is classed as a medical device, it will be subject to various forms of accreditation and regulation. For this reason, many device makers will be careful to avoid any specific medical claims, but devices that offer some health advice are considered a borderline area.<br><br>Another borderline area is hi-tech underpants that protect men from the evil rays allegedly produced by all those wireless devices. Especially the radiation from mobile phones. (Including the Bluetooth that links your underwear to your smartphone.) One brand of underpants that claims to use a mesh of pure silver to create a Faraday cage around the genitals has been banned by the UK Advertising Standards Authority from making any medical claims.<br><br>Or maybe you could just switch the whole lot off.<br><br><br><hr><span><a href="http://www.marketingresearch.org/article/wearable-medical-device-your-future%E2%80%A6is-now">The Wearable Medical Device in Your Future&hellip;Is Now!</a> (Marketing Research Association, 28 April 2015) </span><br><ul></ul><span>Jennie Agg, <a href="http://www.dailymail.co.uk/health/article-2987245/The-hi-tech-bra-helps-beat-breast-cancer-clothes-treat-prevent-illness.html">The hi-tech bra that helps you beat breast cancer - and other clothes that can treat or prevent illness</a> (Daily Mail, 10 March 2015)</span><br><br><span>Sarah Blackman, <a href="http://www.lingerieinsight.com/article-5748-student-designs-cancer-fighting-bra/">Student designs cancer-fighting bra</a> (Lingerie Insight, 10 Feb 2015)&nbsp;</span><br><br><span>Britta O'Boyle, <a href="http://www.pocket-lint.com/news/133184-smartlife-clothing-claims-to-make-sure-you-never-miss-a-beat">SmartLife clothing claims to make sure you never miss a beat</a> (Pocket-Lint, 12 March 2015)&nbsp;</span><br><br><span>Rob Crilly, <a href="http://www.telegraph.co.uk/news/worldnews/northamerica/usa/11178843/Hi-tech-pants-protect-sperm-from-phone-waves.html">Hi-tech pants "protect sperm from phone waves"</a> (Telegraph 22 October 2014)</span><br><br><span>Julie Papanek, <a href="http://techcrunch.com/2015/02/19/how-wearable-startups-can-win-big-in-the-medical-industry/">How Wearable Startups Can Win Big In The Medical Industry</a> (TechCrunch, 19 Feb 2015)</span><br><br><span>Hannah Jane Parkinson, <a href="http://www.theguardian.com/technology/2014/nov/14/lumo-lift-review-posture-tracking-gadget">Lumo Lift review: posture-tracking gadget is a straight shooter</a> (Guardian, 14 November 2014)&nbsp;</span><br><br><span>Helen Popkin, <a href="http://www.nbcnews.com/technology/tweeting-bra-exposed-genuine-support-or-publicity-lift-8C11467042">Tweeting bra exposed: Genuine support or publicity lift?</a> (NBC News 25 October 2013)</span><br><br><span>Meera Senthilingam, <a href="http://edition.cnn.com/2015/05/07/tech/smart-clothes-track-your-health/">How a high-tech bra could be your next doctor</a> (CNN, 11 May 2015)</span><br><br><span>Brendan Seibel, <a href="http://www.wired.com/2010/04/gallery-underwear/">High-Tech Underwear for Adventurous Geeks</a> (21 April 2010)</span><br><br><span>Mark Sweney, <a href="http://www.theguardian.com/media/2014/aug/13/underwear-brand-ad-banned-wireless-armoursir-richard-branson">Hi-tech underwear advert banned</a> (Guardian 13 August 2014)</span><br><br><span><span>Dan Sung, <a href="http://www.wareable.com/wearable-tech/world-cancer-day-foxleaf-real-wonderbra-739">World Cancer Day - The Real Wonderbra</a> (Wearable, 14 Feb 2015)&nbsp;&nbsp;</span></span><br><br><span><br></span><span>Related Posts <a href="http://rvsoftware.blogspot.co.uk/2014/12/have-you-got-big-data-in-your-underwear.html">Have you got big data in your underwear</a> (December 2014)</span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-6414262301974885931</id>
    <title type="html">Have you got big data in your underwear?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>https://plus.google.com/107891026040206160712</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2014-12-10T08:05:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2014/12/have-you-got-big-data-in-your-underwear.html"/>
    <summary type="html"><![CDATA[Apparently, women's breasts aren't all the same. (Who knew?) True+Co. uses an algorithm based on customer feedback to recommend comfortable and flattering bras for its customers. A visitor to the website completes a questionnaire, and the website recommends some suitable bras. If the customer orders the bra, she then completes another questionnaire providing feedback on comfort and appearance. To date, over a million women have completed the questionnaire, providing 15 million data points.<br><br>@<a href="https://twitter.com/tetradian/status/510873284851015682">tetradian</a> reckoned this is a great example of #bizmodel #bigdata for mass-uniqueness. But I didn't see this example the same way: I don't see anything here that turns Mass Customization into what Tom likes to call Mass Uniqueness.<br><br>Tom's favourite example of "mass uniqueness" is Picasso. I bet the algorithm couldn't find a bra for the breasts of <a href="http://wtfarthistory.com/post/33229596129/breasts-of-picassos-demoiselles">Picasso's Demoiselles</a> (NSFW).<br><div>Breasts of Picasso&rsquo;s Demoiselle (NSFW)&hellip;</div><br>A single questionnaire, even from a million women, doesn't get into the big data league. Maybe it would when they start analysing pictures and videos of customer breasts, rather than relying on a simple questionnaire.<br><br>Or if the company were to fit sensors to its underwear, monitoring stretch during a range of activities, collecting millions of data points every minute via the Internet of Things.<br><br>Do you think I'm joking? Microsoft is working on a Smart Bra, which will monitor the mood of the wearer and detect stress. The Daily Mail suggests that this will help women to lose weight.<br><br><blockquote><span>"To stop women reaching for the cookie jar when things hit a low, Microsoft's new prototype bra predicts when the wearer is likely to comfort eat and warns against it.  The software company's high-tech undergarment features sensors in the cup pockets and side panels that detect changes in heart rate, skin temperature and stress levels - apparent precursors to overeating.  All of the data is then streamed via Bluetooth to a smartphone app providing real-time 'mood-triggered eating' alerts." </span></blockquote><br>Now that's what I call big data. Scary, huh?<br><br><br><hr><br><a href="https://twitter.com/goodjillian">Jillian Goodman</a>, <a href="http://www.fastcodesign.com/3035228/innovation-by-design-2014/cup-size-isnt-everything">Cup Size Isn&rsquo;t Everything</a> (Fast Company, October 2014)<br><br>Tom Graves, <a href="http://weblog.tetradian.com/2014/05/23/on-mass-uniqueness/">On Mass Uniqueness</a> (23 May 2014)<br><br><a href="https://twitter.com/aprjoy">April Joyner</a>, <a href="http://www.ozy.com/fast-forward/where-big-data-fashion-meet/33190.article">Big Data: Coming Soon to Your Bra?</a> (Fast Forward, 6 September 2014)<br><br>Hayley Krischer, <a href="http://www.theguardian.com/fashion/2015/jun/04/bra-size-fitter-bloomingdales-town-shop">The underappreciated artistry of the professional bra fitter</a> (Guardian 4 June 2015)<br><br>Sadie Whitelocks, <a href="http://www.dailymail.co.uk/femail/article-2515062/Microsofts-prototype-bra-designed-stop-women-comfort-eating.html">Supporting your body in more ways than one! The high-tech bra designed to stop women from comfort eating</a> (Daily Mail, 28 November 2013)<br><br><a href="http://www.bbc.co.uk/news/technology-25197917">Microsoft working on a smart bra to measure mood</a> (BBC News, 3 December 2013)<br><br><br>See also <a href="http://rvsoftware.blogspot.co.uk/2015/11/towards-internet-of-underthings.html">Towards the Internet of Underthings</a> (November 2015), <a href="http://rvsoftware.blogspot.co.uk/2015/11/weaving-in-three-dimensions.html">Weaving in three dimensions</a> (November 2015)<br><span><br></span><span>Updated 15 November 2015</span>]]></summary>
    <content type="html"><![CDATA[Apparently, women's breasts aren't all the same. (Who knew?) True+Co. uses an algorithm based on customer feedback to recommend comfortable and flattering bras for its customers. A visitor to the website completes a questionnaire, and the website recommends some suitable bras. If the customer orders the bra, she then completes another questionnaire providing feedback on comfort and appearance. To date, over a million women have completed the questionnaire, providing 15 million data points.<br><br>@<a href="https://twitter.com/tetradian/status/510873284851015682">tetradian</a> reckoned this is a great example of #bizmodel #bigdata for mass-uniqueness. But I didn't see this example the same way: I don't see anything here that turns Mass Customization into what Tom likes to call Mass Uniqueness.<br><br>Tom's favourite example of "mass uniqueness" is Picasso. I bet the algorithm couldn't find a bra for the breasts of <a href="http://wtfarthistory.com/post/33229596129/breasts-of-picassos-demoiselles">Picasso's Demoiselles</a> (NSFW).<br><div>Breasts of Picasso&rsquo;s Demoiselle (NSFW)&hellip;</div><br>A single questionnaire, even from a million women, doesn't get into the big data league. Maybe it would when they start analysing pictures and videos of customer breasts, rather than relying on a simple questionnaire.<br><br>Or if the company were to fit sensors to its underwear, monitoring stretch during a range of activities, collecting millions of data points every minute via the Internet of Things.<br><br>Do you think I'm joking? Microsoft is working on a Smart Bra, which will monitor the mood of the wearer and detect stress. The Daily Mail suggests that this will help women to lose weight.<br><br><blockquote><span>"To stop women reaching for the cookie jar when things hit a low, Microsoft's new prototype bra predicts when the wearer is likely to comfort eat and warns against it.  The software company's high-tech undergarment features sensors in the cup pockets and side panels that detect changes in heart rate, skin temperature and stress levels - apparent precursors to overeating.  All of the data is then streamed via Bluetooth to a smartphone app providing real-time 'mood-triggered eating' alerts." </span></blockquote><br>Now that's what I call big data. Scary, huh?<br><br><br><hr><br><a href="https://twitter.com/goodjillian">Jillian Goodman</a>, <a href="http://www.fastcodesign.com/3035228/innovation-by-design-2014/cup-size-isnt-everything">Cup Size Isn&rsquo;t Everything</a> (Fast Company, October 2014)<br><br>Tom Graves, <a href="http://weblog.tetradian.com/2014/05/23/on-mass-uniqueness/">On Mass Uniqueness</a> (23 May 2014)<br><br><a href="https://twitter.com/aprjoy">April Joyner</a>, <a href="http://www.ozy.com/fast-forward/where-big-data-fashion-meet/33190.article">Big Data: Coming Soon to Your Bra?</a> (Fast Forward, 6 September 2014)<br><br>Hayley Krischer, <a href="http://www.theguardian.com/fashion/2015/jun/04/bra-size-fitter-bloomingdales-town-shop">The underappreciated artistry of the professional bra fitter</a> (Guardian 4 June 2015)<br><br>Sadie Whitelocks, <a href="http://www.dailymail.co.uk/femail/article-2515062/Microsofts-prototype-bra-designed-stop-women-comfort-eating.html">Supporting your body in more ways than one! The high-tech bra designed to stop women from comfort eating</a> (Daily Mail, 28 November 2013)<br><br><a href="http://www.bbc.co.uk/news/technology-25197917">Microsoft working on a smart bra to measure mood</a> (BBC News, 3 December 2013)<br><br><br>See also <a href="http://rvsoftware.blogspot.co.uk/2015/11/towards-internet-of-underthings.html">Towards the Internet of Underthings</a> (November 2015), <a href="http://rvsoftware.blogspot.co.uk/2015/11/weaving-in-three-dimensions.html">Weaving in three dimensions</a> (November 2015)<br><span><br></span><span>Updated 15 November 2015</span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-2914714708789565831</id>
    <title type="html">Misunderstanding CRM and Big Data</title>
    <author>
      <name>Richard Veryard</name>
      <uri>https://plus.google.com/107891026040206160712</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2014-11-27T22:53:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2014/11/misunderstanding-crm-and-big-data.html"/>
    <summary type="html"><![CDATA[Listening to @peter_w_ryan, @markhillary and Alexey Minkevich talking about #CRM and #BigData at the Institute of Directors, sponsored by <a href="http://blog.ibagroupit.com/?p=1090">IBA Group</a>.<br><br>Peter cites an Ovum survey showing that Customer Satisfaction is now the number one concern of management, and argues for what Ovum calls Intelligent CRM. (CA announced something under this label back in October 2000. Other products are available.)<br><br>Mark says that CRM and Big Data are widely misunderstood, which is certainly true. My own opinion is the first misunderstanding is to think CRM is about managing THE relationship with THE customer, and I completely agree with Clayton Christensen (via Sloan) that this isn't enough. What we really need to focus on is the job the customers are trying to get done when they use your product or service. <br><br>Who is good at CRM? Peter cites an example of a professor of marketing who got a personalized service at a certain chain of hotels and has been talking about it ever since. (That's a pretty good coup for the hotel, if we take the story at face value.) Mark cites the video game market, where both the console manufacturers and the large game publishers are able to collect and analyse huge quantities of consumer behaviour.<br><br>Is CRM with Big Data merely a new way of taking advantage of customers? Although most people seem oblivious to the privacy and trust risks, the Wall Street Journal this week suggested that the consumer is becoming more savvy and less susceptible to exploitative loyalty schemes and promotions. This might help to explain why Tesco, once a master of the science of retail, now seems to be faltering.<br><br>If there is a sustainable business model based on CRM and Big Data, it must surely involve using these technologies to engage intelligently, authentically and ethically with customers, rather than imagining that these technologies can provide a quick fix for stupid organizations to take advantage of compliant customers.<br><br><br><hr><b>Related Blogs</b><br><br><a href="http://rvsoapbox.blogspot.co.uk/2009/05/customer-orientation.html">Customer Orientation</a> (May 2009)<br><br><a href="http://demandingchange.blogspot.co.uk/2012/04/science-of-retail.html">The Science of Retail</a> (April 2012) <br><br><b>Other Articles</b><br><br>Martha Mangelsdorf, <a href="http://sloanreview.mit.edu/improvisations/2009/05/07/understanding-your-customer-isnt-enough/">Understanding your customer isn't enough</a> (Sloan Review May 2009) <br><br>Shelly Banjo and Sara Germano, <a href="http://online.wsj.com/articles/the-end-of-the-impulse-shopper-1416872108">The End of the Impulse Shopper</a> (Wall Street Journal 25 November 2014)<br><br><b>Intelligent CRM</b><br><br><a href="http://ai-crm.sourceforge.net/">AI-CRM</a> "An intelligent CRM system with atuo-learning-tunning engine (sic), Aichain  offers the most widely used open source business intelligence software  in the world." Last updated March 2013<br><br><a href="http://www.computerworld.com/article/2589117/crm/ca-rolling-out-customer-relationship-management-software.html">CA rolling out customer relationship management software</a> (ComputerWorld October 2000)<br><br><a href="http://ibagroupit.com/en/about/">IBA Group</a> "maintains its focus on IT outsourcing that has become a  strategy for many organizations seeking to improve their business  processes"<br><br>]]></summary>
    <content type="html"><![CDATA[Listening to @peter_w_ryan, @markhillary and Alexey Minkevich talking about #CRM and #BigData at the Institute of Directors, sponsored by <a href="http://blog.ibagroupit.com/?p=1090">IBA Group</a>.<br><br>Peter cites an Ovum survey showing that Customer Satisfaction is now the number one concern of management, and argues for what Ovum calls Intelligent CRM. (CA announced something under this label back in October 2000. Other products are available.)<br><br>Mark says that CRM and Big Data are widely misunderstood, which is certainly true. My own opinion is the first misunderstanding is to think CRM is about managing THE relationship with THE customer, and I completely agree with Clayton Christensen (via Sloan) that this isn't enough. What we really need to focus on is the job the customers are trying to get done when they use your product or service. <br><br>Who is good at CRM? Peter cites an example of a professor of marketing who got a personalized service at a certain chain of hotels and has been talking about it ever since. (That's a pretty good coup for the hotel, if we take the story at face value.) Mark cites the video game market, where both the console manufacturers and the large game publishers are able to collect and analyse huge quantities of consumer behaviour.<br><br>Is CRM with Big Data merely a new way of taking advantage of customers? Although most people seem oblivious to the privacy and trust risks, the Wall Street Journal this week suggested that the consumer is becoming more savvy and less susceptible to exploitative loyalty schemes and promotions. This might help to explain why Tesco, once a master of the science of retail, now seems to be faltering.<br><br>If there is a sustainable business model based on CRM and Big Data, it must surely involve using these technologies to engage intelligently, authentically and ethically with customers, rather than imagining that these technologies can provide a quick fix for stupid organizations to take advantage of compliant customers.<br><br><br><hr><b>Related Blogs</b><br><br><a href="http://rvsoapbox.blogspot.co.uk/2009/05/customer-orientation.html">Customer Orientation</a> (May 2009)<br><br><a href="http://demandingchange.blogspot.co.uk/2012/04/science-of-retail.html">The Science of Retail</a> (April 2012) <br><br><b>Other Articles</b><br><br>Martha Mangelsdorf, <a href="http://sloanreview.mit.edu/improvisations/2009/05/07/understanding-your-customer-isnt-enough/">Understanding your customer isn't enough</a> (Sloan Review May 2009) <br><br>Shelly Banjo and Sara Germano, <a href="http://online.wsj.com/articles/the-end-of-the-impulse-shopper-1416872108">The End of the Impulse Shopper</a> (Wall Street Journal 25 November 2014)<br><br><b>Intelligent CRM</b><br><br><a href="http://ai-crm.sourceforge.net/">AI-CRM</a> "An intelligent CRM system with atuo-learning-tunning engine (sic), Aichain  offers the most widely used open source business intelligence software  in the world." Last updated March 2013<br><br><a href="http://www.computerworld.com/article/2589117/crm/ca-rolling-out-customer-relationship-management-software.html">CA rolling out customer relationship management software</a> (ComputerWorld October 2000)<br><br><a href="http://ibagroupit.com/en/about/">IBA Group</a> "maintains its focus on IT outsourcing that has become a  strategy for many organizations seeking to improve their business  processes"<br><br>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-1254315679163990153.post-4987095738639194752</id>
    <title type="html">Working for the Machine</title>
    <author>
      <name>Richard Veryard</name>
      <uri>https://plus.google.com/107891026040206160712</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2014-11-06T00:15:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://demandingchange.blogspot.com/2014/11/working-for-machine.html"/>
    <summary type="html"><![CDATA[#<a href="https://twitter.com/hashtag/orgintelligence?src=hash">orgintelligence</a> The recent appointment of an algorithm to a Board of Directors raises the spectre of science fiction becoming fact. Although many commentators regarded the appointment as a publicity stunt, there has always been an undercurrent of fear about machine intelligence. Even the BBC (following <a href="http://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines" title="Wikipedia: Betteridge's Law of Headlines">Betteridge's Law of Headlines</a>) succumbed to the alarmist headline <a href="http://t.co/AEu3jN5lgC">Could a big data-crunching machine be your boss one day?</a><br><br>There are several useful ways that an algorithm might contribute to the collective intelligence of a Board of Directors. One is to provide an automated judgement on some topic, which can be put into the pot together with a number of human judgements. This is what seems to be planned by the company Deep Knowledge Ventures, whose Board of Directors is faced with a series of important investment decisions. Although each decision is unique, there are some basic similarities in the decision process that may be amenable to automation and machine learning.<br><br>Another possible contribution is to evaluate other board members. According to the BBC article, IBM Watson could be programmed to analyse the contributions made by each board member for usefulness and accuracy. There are several ways such a feedback loop could enhance the collective intelligence of the Board.<br><br><ul><li>Retrain individuals to improve their contributions in specific contexts.</li><li>Identify and eliminate individuals whose contribution is weak.</li><li>Identify and eliminate individuals whose contribution is similar to other members. In other words, promote greater diversity.</li><li>Enable trial membership of individuals from a wider range of backgrounds, to see whether they can make a valuable contribution.</li></ul><br><br>Organizational Intelligence is about an effective combination of human/social intelligence and  machine intelligence. Remember this when people try to develop an  either-us-or-them narrative.<br><br><br><hr>#<a href="https://twitter.com/hashtag/qtwtain">QTWTAIN</a><br><br>Jamie Bartlett, <a href="http://blogs.spectator.co.uk/coffeehouse/2014/06/will-artificial-intelligence-put-my-job-at-risk/">Will Artificial Intelligence put my job at risk?</a> (Spectator 6 June 2014)<br><br>Adrian Chen, <a href="http://www.newyorker.com/tech/elements/can-an-algorithm-solve-twitters-credibility-problem">Can an Algorithm Solve Twitter&rsquo;s Credibility Problem?</a> (New Yorker 5 May 2014)<br><br>John Rentoul, <a href="http://blogs.independent.co.uk/2014/06/06/will-artificial-intelligence-put-my-job-at-risk/">Will Artificial Intelligence put my job at risk?</a> (Independent 6 June 2014)<br><br>Richard Veryard, <a href="http://rvsoftware.blogspot.co.uk/2013/01/does-camerons-dashboard-app-improve.html">Does Cameron's Dashboard App Improve the OrgIntelligence of Government?</a> (23 January 2013)<br><br>Matthew Wall, <a href="http://www.bbc.co.uk/news/business-29456257">Could a big data-crunching machine be your boss one day?</a> (BBC News 9 October 2014)<br><br><hr><b>Other Sources</b><br><br><a href="http://www.bbc.co.uk/news/technology-27426942">Algorithm appointed board director</a> (BBC News 16 May 2014)<br><br>Bud Caddell, <a href="https://qz.com/1130095/your-boss-might-be-better-as-an-algorithm/">Your boss might be better as an algorithm</a> (Quartz, 16 November 2017)<br><br><br><b>Related Posts</b><br><br><a href="https://demandingchange.blogspot.co.uk/2013/02/intelligence-and-governance.html">Intelligence and Governance</a> (Feb 2013)<br><br><br><span>Link added 11 December 2017</span>]]></summary>
    <content type="html"><![CDATA[#<a href="https://twitter.com/hashtag/orgintelligence?src=hash">orgintelligence</a> The recent appointment of an algorithm to a Board of Directors raises the spectre of science fiction becoming fact. Although many commentators regarded the appointment as a publicity stunt, there has always been an undercurrent of fear about machine intelligence. Even the BBC (following <a href="http://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines" title="Wikipedia: Betteridge's Law of Headlines">Betteridge's Law of Headlines</a>) succumbed to the alarmist headline <a href="http://t.co/AEu3jN5lgC">Could a big data-crunching machine be your boss one day?</a><br><br>There are several useful ways that an algorithm might contribute to the collective intelligence of a Board of Directors. One is to provide an automated judgement on some topic, which can be put into the pot together with a number of human judgements. This is what seems to be planned by the company Deep Knowledge Ventures, whose Board of Directors is faced with a series of important investment decisions. Although each decision is unique, there are some basic similarities in the decision process that may be amenable to automation and machine learning.<br><br>Another possible contribution is to evaluate other board members. According to the BBC article, IBM Watson could be programmed to analyse the contributions made by each board member for usefulness and accuracy. There are several ways such a feedback loop could enhance the collective intelligence of the Board.<br><br><ul><li>Retrain individuals to improve their contributions in specific contexts.</li><li>Identify and eliminate individuals whose contribution is weak.</li><li>Identify and eliminate individuals whose contribution is similar to other members. In other words, promote greater diversity.</li><li>Enable trial membership of individuals from a wider range of backgrounds, to see whether they can make a valuable contribution.</li></ul><br><br>Organizational Intelligence is about an effective combination of human/social intelligence and  machine intelligence. Remember this when people try to develop an  either-us-or-them narrative.<br><br><br><hr>#<a href="https://twitter.com/hashtag/qtwtain">QTWTAIN</a><br><br>Jamie Bartlett, <a href="http://blogs.spectator.co.uk/coffeehouse/2014/06/will-artificial-intelligence-put-my-job-at-risk/">Will Artificial Intelligence put my job at risk?</a> (Spectator 6 June 2014)<br><br>Adrian Chen, <a href="http://www.newyorker.com/tech/elements/can-an-algorithm-solve-twitters-credibility-problem">Can an Algorithm Solve Twitter&rsquo;s Credibility Problem?</a> (New Yorker 5 May 2014)<br><br>John Rentoul, <a href="http://blogs.independent.co.uk/2014/06/06/will-artificial-intelligence-put-my-job-at-risk/">Will Artificial Intelligence put my job at risk?</a> (Independent 6 June 2014)<br><br>Richard Veryard, <a href="http://rvsoftware.blogspot.co.uk/2013/01/does-camerons-dashboard-app-improve.html">Does Cameron's Dashboard App Improve the OrgIntelligence of Government?</a> (23 January 2013)<br><br>Matthew Wall, <a href="http://www.bbc.co.uk/news/business-29456257">Could a big data-crunching machine be your boss one day?</a> (BBC News 9 October 2014)<br><br><hr><b>Other Sources</b><br><br><a href="http://www.bbc.co.uk/news/technology-27426942">Algorithm appointed board director</a> (BBC News 16 May 2014)<br><br>Bud Caddell, <a href="https://qz.com/1130095/your-boss-might-be-better-as-an-algorithm/">Your boss might be better as an algorithm</a> (Quartz, 16 November 2017)<br><br><br><b>Related Posts</b><br><br><a href="https://demandingchange.blogspot.co.uk/2013/02/intelligence-and-governance.html">Intelligence and Governance</a> (Feb 2013)<br><br><br><span>Link added 11 December 2017</span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-8865774453325207109</id>
    <title type="html">Does Big Data Release Information Energy?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>https://plus.google.com/107891026040206160712</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2014-04-26T10:13:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2014/04/does-big-data-release-information-energy.html"/>
    <summary type="html"><![CDATA[@<a href="https://twitter.com/michael_saylor">michael_saylor</a> of #MicroStrategy says that the Information Revolution is about harnessing "information energy" (<a href="http://www2.microstrategy.com/the-mobile-wave/">The Mobile Wave</a>, p 221). He describes information as a kind of fuel that generates "decision motion", driving people - and machines - to make a decision and take a course of action.<br><br>We already know that putting twice as much fuel into a vehicle doesn't make it twice as fast or twice as reliable. (Indeed, aeroplanes sometimes dump fuel to enable a safer landing.) But Saylor explains that information energy is not the same as physical energy.<br><br>1. Information energy doesn't follow conservation laws. Information can be created, consumed repeatedly, but never depleted or destroyed. (Unless it is lost or forgotten.)<br><br>2. Whereas physical energy is additive, the energy content of information is exponential.<br><br>3. The value of information depends on its use, and who is using it.<br><br><br>Let's look at his example.<br><br><blockquote>"Total wheat production for a single year is valuable information; but total wheat production for ten years, combined ten years of rainfall data and ten years of fertilizer represents thirty times more data droplets, but probably contains one hundred times more information energy, because it shows trends and correlations that will drive a greater number of decisions." (pp 221-2).</blockquote><br>In other words, thirty times as much data produces a hundred times more information. He doesn't say this extra information MAY drive more decisions, he says it WILL drive more decisions. In other words, the Information Revolution (and our increasing reliance on tools such as MicroStrategy's products) is a historical inevitability.<br><br>But is it really true that more data produces more information in this exponential way? In practice, there is a depreciation effect for historical or remote data, because an accumulation of small changes in working practices and technologies can make direct comparison misleading or impossible. So even if the farmer had twenty years' worth of data, or shared data from thousands of other farmers, it would not necessarily help her to make better decisions. Five years' data might be almost as good as ten years'.<br><br>Data is moving faster than ever before; we're also storing and processing more and more of it. But that  doesn't mean we're just hoarding data, says Duncan Ross, director of data sciences at Teradata, "The pace of change of  markets generally is so rapid that it doesn't make sense to retain  information for more than a few years." (<a href="https://twitter.com/charlesarthur">Charles Arthur<span></span></a>, <a href="http://www.theguardian.com/technology/2013/aug/23/tech-giants-data">Tech giants may be huge, but nothing matches big data</a>, Guardian 23 August 2013)<br><br>According to Saylor, the key to releasing information energy is mobile technology.<br><br><blockquote>"The shocking thing about information is not how much there is, but how inaccessible it is despite the immense value it represents. ... Mobile computing puts information energy in hands of individuals during all waking hours and everywhere they are." (p 224)</blockquote><br>What kind of decisions does Saylor imagine the farmer needs to make while sitting on a tractor or milking the cows? Obvious it would be useful to get an early warning of some emerging problem - for example an outbreak of disease further down the valley, or possible contamination of a batch of feed or fertilizer at the factory. But complex information needs interpretation, and most decisions require serious reflection, not instant reaction.<br><br>So it is not clear that providing instant access to large quantities of information is going to improve the quality of decision-making. And giving people twice as much information often leads to further procrastination. Surely the challenge for MicroStrategy is to help people deal with information overload, not just add to it?<br><br>Furthermore, as I said in my post <a href="http://rvsoftware.blogspot.co.uk/2013/02/tablets-and-hyperactivity.html">Tablets and Hyperactivity</a> (Feb 2013), being "always on" means that you never have long enough to think through  something difficult before you are interrupted by another event. There  is always another email to attend to, there is always something  happening on Twitter or Facebook, and mobile devices encourage and  reinforce this kind of hyperactivity.<br><br>Saylor concludes that "the acid of technology etches away the unnecessary" (p 237). If only this were true.<br><br><hr>Related posts<br><br><a href="http://rvsoapbox.blogspot.co.uk/2005/09/service-oriented-business-intelligence_22.htm">Service-Oriented Business Intelligence</a> (September 2005) <br><a href="http://demandingchange.blogspot.co.uk/2014/04/on-true-nature-of-knowledge.html">On The True Nature of Knowledge</a> (April 2014)<br><br><br><span>Updated 19 June 2014 </span>]]></summary>
    <content type="html"><![CDATA[@<a href="https://twitter.com/michael_saylor">michael_saylor</a> of #MicroStrategy says that the Information Revolution is about harnessing "information energy" (<a href="http://www2.microstrategy.com/the-mobile-wave/">The Mobile Wave</a>, p 221). He describes information as a kind of fuel that generates "decision motion", driving people - and machines - to make a decision and take a course of action.<br><br>We already know that putting twice as much fuel into a vehicle doesn't make it twice as fast or twice as reliable. (Indeed, aeroplanes sometimes dump fuel to enable a safer landing.) But Saylor explains that information energy is not the same as physical energy.<br><br>1. Information energy doesn't follow conservation laws. Information can be created, consumed repeatedly, but never depleted or destroyed. (Unless it is lost or forgotten.)<br><br>2. Whereas physical energy is additive, the energy content of information is exponential.<br><br>3. The value of information depends on its use, and who is using it.<br><br><br>Let's look at his example.<br><br><blockquote>"Total wheat production for a single year is valuable information; but total wheat production for ten years, combined ten years of rainfall data and ten years of fertilizer represents thirty times more data droplets, but probably contains one hundred times more information energy, because it shows trends and correlations that will drive a greater number of decisions." (pp 221-2).</blockquote><br>In other words, thirty times as much data produces a hundred times more information. He doesn't say this extra information MAY drive more decisions, he says it WILL drive more decisions. In other words, the Information Revolution (and our increasing reliance on tools such as MicroStrategy's products) is a historical inevitability.<br><br>But is it really true that more data produces more information in this exponential way? In practice, there is a depreciation effect for historical or remote data, because an accumulation of small changes in working practices and technologies can make direct comparison misleading or impossible. So even if the farmer had twenty years' worth of data, or shared data from thousands of other farmers, it would not necessarily help her to make better decisions. Five years' data might be almost as good as ten years'.<br><br>Data is moving faster than ever before; we're also storing and processing more and more of it. But that  doesn't mean we're just hoarding data, says Duncan Ross, director of data sciences at Teradata, "The pace of change of  markets generally is so rapid that it doesn't make sense to retain  information for more than a few years." (<a href="https://twitter.com/charlesarthur">Charles Arthur<span></span></a>, <a href="http://www.theguardian.com/technology/2013/aug/23/tech-giants-data">Tech giants may be huge, but nothing matches big data</a>, Guardian 23 August 2013)<br><br>According to Saylor, the key to releasing information energy is mobile technology.<br><br><blockquote>"The shocking thing about information is not how much there is, but how inaccessible it is despite the immense value it represents. ... Mobile computing puts information energy in hands of individuals during all waking hours and everywhere they are." (p 224)</blockquote><br>What kind of decisions does Saylor imagine the farmer needs to make while sitting on a tractor or milking the cows? Obvious it would be useful to get an early warning of some emerging problem - for example an outbreak of disease further down the valley, or possible contamination of a batch of feed or fertilizer at the factory. But complex information needs interpretation, and most decisions require serious reflection, not instant reaction.<br><br>So it is not clear that providing instant access to large quantities of information is going to improve the quality of decision-making. And giving people twice as much information often leads to further procrastination. Surely the challenge for MicroStrategy is to help people deal with information overload, not just add to it?<br><br>Furthermore, as I said in my post <a href="http://rvsoftware.blogspot.co.uk/2013/02/tablets-and-hyperactivity.html">Tablets and Hyperactivity</a> (Feb 2013), being "always on" means that you never have long enough to think through  something difficult before you are interrupted by another event. There  is always another email to attend to, there is always something  happening on Twitter or Facebook, and mobile devices encourage and  reinforce this kind of hyperactivity.<br><br>Saylor concludes that "the acid of technology etches away the unnecessary" (p 237). If only this were true.<br><br><hr>Related posts<br><br><a href="http://rvsoapbox.blogspot.co.uk/2005/09/service-oriented-business-intelligence_22.htm">Service-Oriented Business Intelligence</a> (September 2005) <br><a href="http://demandingchange.blogspot.co.uk/2014/04/on-true-nature-of-knowledge.html">On The True Nature of Knowledge</a> (April 2014)<br><br><br><span>Updated 19 June 2014 </span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-9197334965563726660</id>
    <title type="html">Predictive Analytics for the Smart Consumer?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>https://plus.google.com/107891026040206160712</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2014-04-23T23:42:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2014/04/predictive-analytics-for-smart-consumer.html"/>
    <summary type="html"><![CDATA[<span>#CW500 </span>If merchants can use predictive analytics to get more out of the customer, why can't the customer use predictive analytics to get more out of the merchant?<br><br>In December 2012, I reported on a subscription-based service from <a href="http://decide.com/">decide.com</a>,  which predicted future retail price changes (based on retailers' past  behaviour) and encouraged its members to use these predictions to  optimize the timing of key purchases.<br><br>Many retailers have fairly regular patterns of seasonal price changes and promotions, which are designed to maximize the lifetime profitability of a product. This is particularly important for fashion goods and high-tech, which tend to have a high initial price and a low clearance price. However, if customers (with the help of advisory services such as decide.com) start to game these price changes, then profit optimization becomes a lot harder to calculate. So this kind of advisory service represents a significant threat to retail profitability.<br><br>In September 2013, decide.com was acquired by eBay and effectively closed down. &ldquo;This is an exciting opportunity to bring Decide&rsquo;s expertise in data and  predictive analytics to the worldwide commerce leader and empower over  25 million eBay sellers,&rdquo; said Mike Fridgen, CEO of Decide.com. &ldquo;We  believe teaming up with eBay allows us to realize our mission of  leveling the playing field in commerce.&rdquo; (<a href="http://blog.ebay.com/ebay-inc-acquires-price-research-firm-decide-com/">eBay 6 September 2013</a>, <a href="http://www.geekwire.com/2013/ebay-acquires-decidecom-shopping-research-site-shut-sept-30/">Geekwire 6 September 2013</a>)<br><br>In other words, taking the advantage away from the customers and giving it back to the sellers.<br><br>However, other customer-side predictive services may be still available, including <a href="http://gaspredictor.com/">GasPredictor.com</a> (for Gasoline) and <a href="http://www.kayak.com/">Kayak</a> (for air travel).<br><hr><br><a href="http://rvsoftware.blogspot.co.uk/2012/12/predictive-showrooming.html">Predictive Showrooming Dec 2012</a><br><br>Tricia Duryee, <a href="http://allthingsd.com/20120419/decide-com-says-it-will-accurately-predict-prices-or-your-money-back/">Decide.com Says It Will Accurately Predict Prices or Your Money Back</a> (All Things D, 19 April 2012)<br><br>Thorin Klosowski, <a href="http://lifehacker.com/5976095/kayak-adds-price-forecasting-to-predict-price-drops-and-increases">Kayak Adds Price Forecasting to Predict Price Drops and Increases</a> (Lifehacker, 15 Jan 2013)]]></summary>
    <content type="html"><![CDATA[<span>#CW500 </span>If merchants can use predictive analytics to get more out of the customer, why can't the customer use predictive analytics to get more out of the merchant?<br><br>In December 2012, I reported on a subscription-based service from <a href="http://decide.com/">decide.com</a>,  which predicted future retail price changes (based on retailers' past  behaviour) and encouraged its members to use these predictions to  optimize the timing of key purchases.<br><br>Many retailers have fairly regular patterns of seasonal price changes and promotions, which are designed to maximize the lifetime profitability of a product. This is particularly important for fashion goods and high-tech, which tend to have a high initial price and a low clearance price. However, if customers (with the help of advisory services such as decide.com) start to game these price changes, then profit optimization becomes a lot harder to calculate. So this kind of advisory service represents a significant threat to retail profitability.<br><br>In September 2013, decide.com was acquired by eBay and effectively closed down. &ldquo;This is an exciting opportunity to bring Decide&rsquo;s expertise in data and  predictive analytics to the worldwide commerce leader and empower over  25 million eBay sellers,&rdquo; said Mike Fridgen, CEO of Decide.com. &ldquo;We  believe teaming up with eBay allows us to realize our mission of  leveling the playing field in commerce.&rdquo; (<a href="http://blog.ebay.com/ebay-inc-acquires-price-research-firm-decide-com/">eBay 6 September 2013</a>, <a href="http://www.geekwire.com/2013/ebay-acquires-decidecom-shopping-research-site-shut-sept-30/">Geekwire 6 September 2013</a>)<br><br>In other words, taking the advantage away from the customers and giving it back to the sellers.<br><br>However, other customer-side predictive services may be still available, including <a href="http://gaspredictor.com/">GasPredictor.com</a> (for Gasoline) and <a href="http://www.kayak.com/">Kayak</a> (for air travel).<br><hr><br><a href="http://rvsoftware.blogspot.co.uk/2012/12/predictive-showrooming.html">Predictive Showrooming Dec 2012</a><br><br>Tricia Duryee, <a href="http://allthingsd.com/20120419/decide-com-says-it-will-accurately-predict-prices-or-your-money-back/">Decide.com Says It Will Accurately Predict Prices or Your Money Back</a> (All Things D, 19 April 2012)<br><br>Thorin Klosowski, <a href="http://lifehacker.com/5976095/kayak-adds-price-forecasting-to-predict-price-drops-and-increases">Kayak Adds Price Forecasting to Predict Price Drops and Increases</a> (Lifehacker, 15 Jan 2013)]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-3250489855449399072</id>
    <title type="html">On Customer Insight</title>
    <author>
      <name>Richard Veryard</name>
      <uri>https://plus.google.com/107891026040206160712</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2014-02-26T14:40:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2014/02/on-customer-insight.html"/>
    <summary type="html"><![CDATA[  <br><div><b> <a href="https://www.slideshare.net/RichardVeryard/on-customer-insight" target="_blank" title="On Customer Insight">On Customer Insight</a> </b> from <b><a href="https://www.slideshare.net/RichardVeryard" target="_blank">Richard Veryard</a></b> </div>]]></summary>
    <content type="html"><![CDATA[  <br><div><b> <a href="https://www.slideshare.net/RichardVeryard/on-customer-insight" target="_blank" title="On Customer Insight">On Customer Insight</a> </b> from <b><a href="https://www.slideshare.net/RichardVeryard" target="_blank">Richard Veryard</a></b> </div>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-4782162782935564907</id>
    <title type="html">Who owns data management strategy?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2013-02-25T16:34:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2013/02/who-owns-data-management-strategy.html"/>
    <summary type="html"><![CDATA[@<a href="http://twitter.com/joel_schectman" rel="nofollow" target="_blank">joel_schectman</a> exposes an apparent divergence of opinion among #Gartner analysts - whether CEO or CIO should be in charge of data management strategy.<br><br><br>@<a href="http://twitter.com/ted_friedman" rel="nofollow" target="_blank">ted_friedman</a> says that taking out IT as the gatekeeper of centrally stored data can promote &ldquo;better fact based decision making across the organization&rdquo;. <br><br>@<a href="http://twitter.com/merv" rel="nofollow" target="_blank">merv adrian</a> says that bypassing the CIO can have unintended side effects like risks to privacy and the quality of the analysis.<br><br><br>Merv explains further &ldquo;If you don&rsquo;t have to go through a procurement process and IT, you&rsquo;re a lot freer to do what you want,&rdquo; said Mr. Adrian. &ldquo;But all of that carefully constructed governance is completely undermined, you can be drawing incorrect conclusions, and exposing risks to privacy because they are doing things IT hasn&rsquo;t vetted.&rdquo;<br><br>Merv's concern about quality also applies to the  widespread and often uncontrolled use of spreadsheets and other end-user  tools. For example, we can find @JamesYKwak and @alexhern discussing  whether we can blame Microsoft Excel for $9bn losses at JPMorgan?<br><br>What exactly do we mean by data management strategy? Joel says it includes how to best utilize customer information to leverage growth. Most CIOs seem to think their responsibility for data finishes when they deliver data and information to the user's device. They seem uninterested in how these users actually use the data, and whether better or faster data genuinely improve decisions and policies, and produce better business outcomes.<br><br>In other words, the CIO doesn't operate as a Chief Information Officer but as a Chief Information Systems and Technology Officer.<br><br>True information strategy includes a closed feedback and learning loop, so that the use of the information can be monitored. Are these expensively collected and elaborately processed data analytics actually influencing decisions, or are the users mostly ignoring them? <br><br><br><hr>Alex Hern, <a href="http://www.newstatesman.com/technology/2013/02/excel-most-dangerous-piece-software-world">Is Excel the most dangerous piece of software in the world?</a> (New Statesman Feb 2013)<br><br>James Kwak, <a href="http://baselinescenario.com/2013/02/09/the-importance-of-excel/">The Importance of Excel</a> (Baseline Scenario Feb 2013) <br><br>Joel Schectman, <a href="http://blogs.wsj.com/cio/2013/02/20/democratizing-data-analysis-has-risk/">Democratizing Data Analysis Has Risk</a> (WSJ Feb 2013)<br><br><br><span>Updated 20 February 2016</span>]]></summary>
    <content type="html"><![CDATA[@<a href="http://twitter.com/joel_schectman" rel="nofollow" target="_blank">joel_schectman</a> exposes an apparent divergence of opinion among #Gartner analysts - whether CEO or CIO should be in charge of data management strategy.<br><br><br>@<a href="http://twitter.com/ted_friedman" rel="nofollow" target="_blank">ted_friedman</a> says that taking out IT as the gatekeeper of centrally stored data can promote &ldquo;better fact based decision making across the organization&rdquo;. <br><br>@<a href="http://twitter.com/merv" rel="nofollow" target="_blank">merv adrian</a> says that bypassing the CIO can have unintended side effects like risks to privacy and the quality of the analysis.<br><br><br>Merv explains further &ldquo;If you don&rsquo;t have to go through a procurement process and IT, you&rsquo;re a lot freer to do what you want,&rdquo; said Mr. Adrian. &ldquo;But all of that carefully constructed governance is completely undermined, you can be drawing incorrect conclusions, and exposing risks to privacy because they are doing things IT hasn&rsquo;t vetted.&rdquo;<br><br>Merv's concern about quality also applies to the  widespread and often uncontrolled use of spreadsheets and other end-user  tools. For example, we can find @JamesYKwak and @alexhern discussing  whether we can blame Microsoft Excel for $9bn losses at JPMorgan?<br><br>What exactly do we mean by data management strategy? Joel says it includes how to best utilize customer information to leverage growth. Most CIOs seem to think their responsibility for data finishes when they deliver data and information to the user's device. They seem uninterested in how these users actually use the data, and whether better or faster data genuinely improve decisions and policies, and produce better business outcomes.<br><br>In other words, the CIO doesn't operate as a Chief Information Officer but as a Chief Information Systems and Technology Officer.<br><br>True information strategy includes a closed feedback and learning loop, so that the use of the information can be monitored. Are these expensively collected and elaborately processed data analytics actually influencing decisions, or are the users mostly ignoring them? <br><br><br><hr>Alex Hern, <a href="http://www.newstatesman.com/technology/2013/02/excel-most-dangerous-piece-software-world">Is Excel the most dangerous piece of software in the world?</a> (New Statesman Feb 2013)<br><br>James Kwak, <a href="http://baselinescenario.com/2013/02/09/the-importance-of-excel/">The Importance of Excel</a> (Baseline Scenario Feb 2013) <br><br>Joel Schectman, <a href="http://blogs.wsj.com/cio/2013/02/20/democratizing-data-analysis-has-risk/">Democratizing Data Analysis Has Risk</a> (WSJ Feb 2013)<br><br><br><span>Updated 20 February 2016</span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-5050661576569029894</id>
    <title type="html">Using Analytics Correctly</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2013-01-25T22:54:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2013/01/using-analytics-correctly.html"/>
    <summary type="html"><![CDATA[@<a href="http://twitter.com/gcharlton">gcharlton</a> quotes a survey from @<a href="http://twitter.com/dbdsearch">dbdsearch</a> claiming that <a href="http://econsultancy.com/uk/blog/10925-80-of-online-retailers-are-using-google-analytics-incorrectly">80% of online retailers are using @GoogleAnalytics incorrectly</a> (October 2012), via @<a href="http://twitter.com/Freshnick/status/294887470011674625">FreshNick</a> @<a href="http://twitter.com/haydens30/status/294896391241728000">hayden30</a>.<br><br><br>Clearly Google wants online retailers to use all the features of the Google Analytics platform, which entails integrating with various other Google products and services (e.g. Google Adwords) as well as implementing all the necessary tracking codes and cookies according to Google's requirements. Any online retailer that fails to conform to Google's requirements is deemed to be using the platform incorrectly.<br><br>But what does "incorrectly" mean? Not doing what Google thinks you should be doing? Since when has Google been the ultimate arbiter of correct action?<br><br>We have been here many times before. There is often a significant gap between the designed product (how its designers expect it to be used) and the product-in-use (what the users actually do with the product). A designed product may have a number of sophisticated features that most users never get around to using, perhaps never actually need. On the other hand, the users trying to do a real job of work often display remarkable ingenuity in getting the stupid product to do something much more interesting than it was designed to do.<br><br>And sometimes there is a considerable delay until users discover the more sophisticated features. To cite a historical example, most early users of Lotus Notes used it as a substitute for technologies they already had, before they started to appreciate what it had really been designed for.<br><br>So there may be many ways people could learn to use Google Analytics better. As @<a href="http://twitter.com/haydens30/status/294904311719288832">haydens30</a> says, "there are basic best practice things that a lot of sites don't do - these are easy wins for any consultant".  <br><br>And there may be many ways Google itself could make Analytics better and easier to use. In announcing some <a href="http://analytics.blogspot.co.uk/2013/01/analytics-ui-improvements.html">UI improvements</a> yesterday,  Nikhil Roy of the Google Analytics Team said "We hope you find these improvements useful and always feel free to let us know how we can make Analytics even more usable for you to get the information you need to take action faster."<br><br>What, we have to tell them? Don't they already know?<br>&nbsp;]]></summary>
    <content type="html"><![CDATA[@<a href="http://twitter.com/gcharlton">gcharlton</a> quotes a survey from @<a href="http://twitter.com/dbdsearch">dbdsearch</a> claiming that <a href="http://econsultancy.com/uk/blog/10925-80-of-online-retailers-are-using-google-analytics-incorrectly">80% of online retailers are using @GoogleAnalytics incorrectly</a> (October 2012), via @<a href="http://twitter.com/Freshnick/status/294887470011674625">FreshNick</a> @<a href="http://twitter.com/haydens30/status/294896391241728000">hayden30</a>.<br><br><br>Clearly Google wants online retailers to use all the features of the Google Analytics platform, which entails integrating with various other Google products and services (e.g. Google Adwords) as well as implementing all the necessary tracking codes and cookies according to Google's requirements. Any online retailer that fails to conform to Google's requirements is deemed to be using the platform incorrectly.<br><br>But what does "incorrectly" mean? Not doing what Google thinks you should be doing? Since when has Google been the ultimate arbiter of correct action?<br><br>We have been here many times before. There is often a significant gap between the designed product (how its designers expect it to be used) and the product-in-use (what the users actually do with the product). A designed product may have a number of sophisticated features that most users never get around to using, perhaps never actually need. On the other hand, the users trying to do a real job of work often display remarkable ingenuity in getting the stupid product to do something much more interesting than it was designed to do.<br><br>And sometimes there is a considerable delay until users discover the more sophisticated features. To cite a historical example, most early users of Lotus Notes used it as a substitute for technologies they already had, before they started to appreciate what it had really been designed for.<br><br>So there may be many ways people could learn to use Google Analytics better. As @<a href="http://twitter.com/haydens30/status/294904311719288832">haydens30</a> says, "there are basic best practice things that a lot of sites don't do - these are easy wins for any consultant".  <br><br>And there may be many ways Google itself could make Analytics better and easier to use. In announcing some <a href="http://analytics.blogspot.co.uk/2013/01/analytics-ui-improvements.html">UI improvements</a> yesterday,  Nikhil Roy of the Google Analytics Team said "We hope you find these improvements useful and always feel free to let us know how we can make Analytics even more usable for you to get the information you need to take action faster."<br><br>What, we have to tell them? Don't they already know?<br>&nbsp;]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-5186015593560945437</id>
    <title type="html">Opening the Black Box: Analytics and Admissions</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2013-01-23T21:01:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2013/01/opening-black-box-analytics-and.html"/>
    <summary type="html"><![CDATA[@<a href="http://twitter.com/peteyMIT/status/294170985215709185">peteyMIT</a> via @<a href="http://twitter.com/EthanZ/status/294172120718639104">EthanZ</a> explains how technology is changing the university admissions process.<br><br>When kids apply to university in the USA, it is becoming increasingly common to include a link with supplementary information about the applicant - for example a project tumblr, a YouTube video, a Flickr album of artwork. The links are typically coded to track visitors, giving the applicant some idea about the level of interest the universities are showing. Chris Peterson finds this an uncomfortable experience: "As admissions officers, we are accustomed to reading applications; now, applications are reading us. ... Applicants are now armed with unprecedented insight into the processes that decide their fate."<br><br>There are several problems with this. Applicants and their parents may be misled by the tracking signals collected by these digital supplements, which may yield an entirely false picture of the university process. And yet applicants may attempt to use these signals as evidence that an application has not been properly considered. Even if the university attempts to block the analytics, this may still send the wrong message. (The absence of a signal is still a signal.)<br><br>In the past, analytics were a tool used by large organizations to monitor and control their customers. We are now seeing analytic platforms that seem to allow customers to monitor and control large organizations. Large organizations now need to understand how much information they are exposing to these platforms, and what conclusions their customers may draw. We can expect similar examples to appear in many other sectors. <br><br><br>Chris Peterson, <a href="http://chronicle.com/blogs/headcount/opening-the-black-box-analytics-and-admissions">Opening the Black Box: Analytics and Admissions</a> (Chronicle of Higher Education, January 2013)<br><br><span>Updated 25 June 2015</span>]]></summary>
    <content type="html"><![CDATA[@<a href="http://twitter.com/peteyMIT/status/294170985215709185">peteyMIT</a> via @<a href="http://twitter.com/EthanZ/status/294172120718639104">EthanZ</a> explains how technology is changing the university admissions process.<br><br>When kids apply to university in the USA, it is becoming increasingly common to include a link with supplementary information about the applicant - for example a project tumblr, a YouTube video, a Flickr album of artwork. The links are typically coded to track visitors, giving the applicant some idea about the level of interest the universities are showing. Chris Peterson finds this an uncomfortable experience: "As admissions officers, we are accustomed to reading applications; now, applications are reading us. ... Applicants are now armed with unprecedented insight into the processes that decide their fate."<br><br>There are several problems with this. Applicants and their parents may be misled by the tracking signals collected by these digital supplements, which may yield an entirely false picture of the university process. And yet applicants may attempt to use these signals as evidence that an application has not been properly considered. Even if the university attempts to block the analytics, this may still send the wrong message. (The absence of a signal is still a signal.)<br><br>In the past, analytics were a tool used by large organizations to monitor and control their customers. We are now seeing analytic platforms that seem to allow customers to monitor and control large organizations. Large organizations now need to understand how much information they are exposing to these platforms, and what conclusions their customers may draw. We can expect similar examples to appear in many other sectors. <br><br><br>Chris Peterson, <a href="http://chronicle.com/blogs/headcount/opening-the-black-box-analytics-and-admissions">Opening the Black Box: Analytics and Admissions</a> (Chronicle of Higher Education, January 2013)<br><br><span>Updated 25 June 2015</span>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-4396737508710923696</id>
    <title type="html">Does Cameron's Dashboard App Improve the OrgIntelligence of Government?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2013-01-23T13:43:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2013/01/does-camerons-dashboard-app-improve.html"/>
    <summary type="html"><![CDATA[In November 2012, it was announced that a mobile app to aid in decision-making and day-to-day government affairs was being trialled by the prime minister. <br><br><div><span><a href="http://www.bbc.co.uk/news/technology-20240874">UK Trialling App to Aid Government Decisions</a> (BBC News 8 November 2012) </span></div><br><br>Here are some quick comments from Twitter <br><i><br></i><i>@lesteph PM's dashboard is at best pointless, at worst dangerous, unless his briefing system has fundamentally collapsed </i><br><i><br></i><i>@dominiccampbell he may as well have it, but pretending it's anything other than a partial view and mostly for PR is daft </i><br><i><br></i><i>@willperrin rather an antediluvian counsel of despair there then. back to 'ringbinders full of..' briefing </i><br><i><br></i><i>@6loss The "dashboard vs intelligence" debate? IMHO dashboards are useless without fast feedback on action. </i><br><br>In a <a href="http://lnkd.in/Wx45At">subsequent discussion on Linked-In</a>, @6loss and I discussed some of the intriguing questions raised by this news story. <br><br>Firstly, we were missing the imperative for real-time action and feedback. Obviously the Prime Minister needs to know whether job vacancies are going up or down, but the idea of real-time update is just ridiculous. Suppose that seventeen new job vacancies have been posted in Smartchester in the past twenty minutes, Are we supposed to believe that these seventeen vacancies urgently need to be communicated to the PM so that he can take appropriate action? <br><br>What does make sense is a dashboard that supports an OODA loop. A well-designed dashboard should not only provide aggregated data, but also provide some way of making sense of the data. (It is possible that the data visualization may help here.) And then taking rapid action. <br><br>But in a well-designed organization, the responsibility for rapid action is delegated to the people in the front line, who are given the real-time intelligence and the resources/tools and the authority to solve problems effectively and efficiently. This is what the military call "Power to the Edge". A completely different order of intelligence is required at the centre, usually operating at a much slower tempo. <br><br>And since managers are often tempted to meddle with randomly varying processes (Deming called this "tampering"), a well-designed control system deliberately hides much of the volatility from senior management. (In cybernetics, this is called "attenuation".) <br><br>Secondly, I'm wondering what kind of statistics we are talking about here. When people talk  about "statistics", they often mean the kind of statistics kids learn in  primary school (totals and averages) rather than the kind of statistics  kids learn in high school (correlation and significance). I wonder how  many ministers could cope with high school statistics (let alone degree  level) without a civil servant or adviser there to explain it to them?  The danger of the "dashboard" is that it may eliminate the vital step of  interpretation and sense-making, which is surely essential to  evidence-based management.&nbsp; <br><br>Thirdly, I'm wondering about the planned rollout of this App. Are we to suppose that all ministers and senior civil servants are going to be watching the same set of indicators, or does collective responsibility entail that each minister is watching a different set of indicators? In a typical control room, there are many people each watching a different dashboard or controlling a different sector: it would seem a bit redundant if they were all watching the same one. Meanwhile, the supervisor sits in his cubicle playing Angry Birds, or sending texts to his neighbours.<br><br>A few weeks after this discussion, writing in the New York Times, Will Wiles compared this dashboard with the Viable Systems Model implementation in Chile under Salvador Allende. He pointed out that the dashboard is not truly cybernetic because it lacks a mechanism to translate all that data into action. Quite so.<br><br><div><span>Will Wiles, <a href="http://www.nytimes.com/2012/11/30/opinion/the-no-10-dashboard-and-cybernetics.html?_r=0">Before Fruit Ninja, Cybernetics</a> (New York Times, 30 November 2012)</span></div>]]></summary>
    <content type="html"><![CDATA[In November 2012, it was announced that a mobile app to aid in decision-making and day-to-day government affairs was being trialled by the prime minister. <br><br><div><span><a href="http://www.bbc.co.uk/news/technology-20240874">UK Trialling App to Aid Government Decisions</a> (BBC News 8 November 2012) </span></div><br><br>Here are some quick comments from Twitter <br><i><br></i><i>@lesteph PM's dashboard is at best pointless, at worst dangerous, unless his briefing system has fundamentally collapsed </i><br><i><br></i><i>@dominiccampbell he may as well have it, but pretending it's anything other than a partial view and mostly for PR is daft </i><br><i><br></i><i>@willperrin rather an antediluvian counsel of despair there then. back to 'ringbinders full of..' briefing </i><br><i><br></i><i>@6loss The "dashboard vs intelligence" debate? IMHO dashboards are useless without fast feedback on action. </i><br><br>In a <a href="http://lnkd.in/Wx45At">subsequent discussion on Linked-In</a>, @6loss and I discussed some of the intriguing questions raised by this news story. <br><br>Firstly, we were missing the imperative for real-time action and feedback. Obviously the Prime Minister needs to know whether job vacancies are going up or down, but the idea of real-time update is just ridiculous. Suppose that seventeen new job vacancies have been posted in Smartchester in the past twenty minutes, Are we supposed to believe that these seventeen vacancies urgently need to be communicated to the PM so that he can take appropriate action? <br><br>What does make sense is a dashboard that supports an OODA loop. A well-designed dashboard should not only provide aggregated data, but also provide some way of making sense of the data. (It is possible that the data visualization may help here.) And then taking rapid action. <br><br>But in a well-designed organization, the responsibility for rapid action is delegated to the people in the front line, who are given the real-time intelligence and the resources/tools and the authority to solve problems effectively and efficiently. This is what the military call "Power to the Edge". A completely different order of intelligence is required at the centre, usually operating at a much slower tempo. <br><br>And since managers are often tempted to meddle with randomly varying processes (Deming called this "tampering"), a well-designed control system deliberately hides much of the volatility from senior management. (In cybernetics, this is called "attenuation".) <br><br>Secondly, I'm wondering what kind of statistics we are talking about here. When people talk  about "statistics", they often mean the kind of statistics kids learn in  primary school (totals and averages) rather than the kind of statistics  kids learn in high school (correlation and significance). I wonder how  many ministers could cope with high school statistics (let alone degree  level) without a civil servant or adviser there to explain it to them?  The danger of the "dashboard" is that it may eliminate the vital step of  interpretation and sense-making, which is surely essential to  evidence-based management.&nbsp; <br><br>Thirdly, I'm wondering about the planned rollout of this App. Are we to suppose that all ministers and senior civil servants are going to be watching the same set of indicators, or does collective responsibility entail that each minister is watching a different set of indicators? In a typical control room, there are many people each watching a different dashboard or controlling a different sector: it would seem a bit redundant if they were all watching the same one. Meanwhile, the supervisor sits in his cubicle playing Angry Birds, or sending texts to his neighbours.<br><br>A few weeks after this discussion, writing in the New York Times, Will Wiles compared this dashboard with the Viable Systems Model implementation in Chile under Salvador Allende. He pointed out that the dashboard is not truly cybernetic because it lacks a mechanism to translate all that data into action. Quite so.<br><br><div><span>Will Wiles, <a href="http://www.nytimes.com/2012/11/30/opinion/the-no-10-dashboard-and-cybernetics.html?_r=0">Before Fruit Ninja, Cybernetics</a> (New York Times, 30 November 2012)</span></div>]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-7415430.post-206261083757385798</id>
    <title type="html">OrgIntelligence - Are Better Tools the Answer?</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2013-01-22T13:17:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoftware.blogspot.com/2013/01/orgintelligence-are-better-tools-answer.html"/>
    <summary type="html"><![CDATA[<h4>Information Gathering</h4>Managers spend up to two hours a day searching for information, and  more than 50 percent of the information they obtain has no value to  them.&nbsp; In addition, only half of all managers believe their  companies do a good job in governing information distribution or have  established adequate processes to determine what data each part of an  organization needs.<br><br><div>Source: <a href="http://newsroom.accenture.com/article_display.cfm?article_id=4484">Accenture January 2007</a> </div><br>The average interaction worker spends an estimated 28 percent of the  workweek managing e-mail and nearly 20 percent looking for internal  information or tracking down colleagues who can help with specific  tasks. <br><br><div>Source: <a href="http://www.mckinsey.com/insights/mgi/research/technology_and_innovation/the_social_economy">McKinsey July 2012</a></div><div>See also <a href="http://blogs.hbr.org/cs/2012/08/social_medias_productivity_pay.html">HBR Blog August 2012</a></div><br><h4>Knowledge Management</h4><br>Traditional knowledge management has failed to address the problem of  knowledge worker productivity. Tools that have been developed in KM  focused on information management and do not support many of the key  knowledge work processes. Knowledge workers have therefore adpated the  email client to suit their needs. It has become the most successful  knowledge work tool because it combines personal control with  personalisability and integrates communication.<br><br><div>Source: <a href="http://www.roell.net/publikationen/distributedkm.shtml">Martin Roell, August 2004 </a></div><br><h4>Big Data</h4><br>By 2018, the United States alone could face a shortage of 140,000 to  190,000 people with deep analytical skills as well as 1.5 million  managers and analysts with the know-how to use the analysis of big data  to make effective decisions.<br><br><div>Source: <a href="http://www.mckinsey.com/insights/mgi/research/technology_and_innovation/big_data_the_next_frontier_for_innovation">McKinsey May 2011</a></div><br>Big data can create big value. But like all the big-data predecessors &ndash;  i.e., databases, data warehousing, data mining, data analytics and  business intelligence &ndash; you need to know what you&rsquo;re looking for, why  you&rsquo;re looking for it, what&rsquo;s it worth to you, and how will you take  advantage of it BEFORE you start. Otherwise, big data will just be a big  waste of money.<br><br><div>Source: <a href="http://blog.silver-peak.com/is-big-data-a-big-waste-of-money">Silver Peak Systems, May 2012</a> </div><br><br><h4>Social Media</h4><br><span>Social media is addictive. And if you&rsquo;re not too careful, it can seriously eat into your productivity.</span><br><br><div>Source: <a href="http://www.mediabistro.com/alltwitter/social-media-vs-productivity_b30629">MediaBistro All-Twitter October 2012</a></div><br><hr>Places are still available on my <a href="http://unicom.co.uk/orgintelligence/">Organizational Intelligence Workshop</a> (Feb 1st).]]></summary>
    <content type="html"><![CDATA[<h4>Information Gathering</h4>Managers spend up to two hours a day searching for information, and  more than 50 percent of the information they obtain has no value to  them.&nbsp; In addition, only half of all managers believe their  companies do a good job in governing information distribution or have  established adequate processes to determine what data each part of an  organization needs.<br><br><div>Source: <a href="http://newsroom.accenture.com/article_display.cfm?article_id=4484">Accenture January 2007</a> </div><br>The average interaction worker spends an estimated 28 percent of the  workweek managing e-mail and nearly 20 percent looking for internal  information or tracking down colleagues who can help with specific  tasks. <br><br><div>Source: <a href="http://www.mckinsey.com/insights/mgi/research/technology_and_innovation/the_social_economy">McKinsey July 2012</a></div><div>See also <a href="http://blogs.hbr.org/cs/2012/08/social_medias_productivity_pay.html">HBR Blog August 2012</a></div><br><h4>Knowledge Management</h4><br>Traditional knowledge management has failed to address the problem of  knowledge worker productivity. Tools that have been developed in KM  focused on information management and do not support many of the key  knowledge work processes. Knowledge workers have therefore adpated the  email client to suit their needs. It has become the most successful  knowledge work tool because it combines personal control with  personalisability and integrates communication.<br><br><div>Source: <a href="http://www.roell.net/publikationen/distributedkm.shtml">Martin Roell, August 2004 </a></div><br><h4>Big Data</h4><br>By 2018, the United States alone could face a shortage of 140,000 to  190,000 people with deep analytical skills as well as 1.5 million  managers and analysts with the know-how to use the analysis of big data  to make effective decisions.<br><br><div>Source: <a href="http://www.mckinsey.com/insights/mgi/research/technology_and_innovation/big_data_the_next_frontier_for_innovation">McKinsey May 2011</a></div><br>Big data can create big value. But like all the big-data predecessors &ndash;  i.e., databases, data warehousing, data mining, data analytics and  business intelligence &ndash; you need to know what you&rsquo;re looking for, why  you&rsquo;re looking for it, what&rsquo;s it worth to you, and how will you take  advantage of it BEFORE you start. Otherwise, big data will just be a big  waste of money.<br><br><div>Source: <a href="http://blog.silver-peak.com/is-big-data-a-big-waste-of-money">Silver Peak Systems, May 2012</a> </div><br><br><h4>Social Media</h4><br><span>Social media is addictive. And if you&rsquo;re not too careful, it can seriously eat into your productivity.</span><br><br><div>Source: <a href="http://www.mediabistro.com/alltwitter/social-media-vs-productivity_b30629">MediaBistro All-Twitter October 2012</a></div><br><hr>Places are still available on my <a href="http://unicom.co.uk/orgintelligence/">Organizational Intelligence Workshop</a> (Feb 1st).]]></content>
  </entry>
  <entry>
    <id>tag:blogger.com,1999:blog-6106782.post-69447632226110878</id>
    <title type="html">What's Wrong with the Single Version of Truth</title>
    <author>
      <name>Richard Veryard</name>
      <uri>http://www.blogger.com/profile/04499123397533975655</uri>
      <email>noreply@blogger.com</email>
    </author>
    <updated>2010-03-19T15:04:00+00:00</updated>
    <link rel="alternate" type="text/html" href="http://rvsoapbox.blogspot.com/2010/03/whats-wrong-with-single-version-of.html"/>
    <summary type="html"><![CDATA[As @<a href="http://twitter.com/tonyrcollins/status/10716072556">tonyrcollins</a> reports, a confidential report currently in preparation on the NHS Summary Care Records (SCR) database will reveal serious flaws in a massively expensive database (<a href="http://www.computerweekly.com/blogs/tony_collins/2010/03/confidential-report-on-summary.html">Computer Weekly, March 2010</a>). Well knock me down with a superbug, whoever would have guessed this might happen?<br><br><blockquote>"The final report may conclude that the success of SCRs will depend on whether the NHS, Connecting for Health and the Department of Health can bridge the deep cultural and institutional divides that have so far characterised the NPfIT. It may also ask whether the government founded the SCR on an unrealistic assumption: that the centralised database could ever be a single source of truth."</blockquote><br>There are several reasons to be ambivalent about the twin principles Single Version of Truth (SVOT) and Single Source of Truth (SSOT), and this kind of massive failure must worry even the most fervent advocates of these principles.<br><br>Don't get me wrong, I have served my time in countless projects trying to reduce the proliferation and fragmentation of data and information in large organizations, and I am well aware of the technical costs and business risks associated with data duplication. However, I have some serious concerns about the dogmatic way these principles are often interpreted and implemented, especially when this dogmatism results (as seems to be the case here) in a costly and embarrassing failure.<br><br>The first problem is that Single-Truth only works if you have absolute confidence in the quality of the data. In the SCR example, there is evidence that doctors simply don't trust the new system - and with good reason. There are errors and omissions in the summary records, and doctors prefer to double-check details of medications and allergies, rather than take the risk of relying on a single source. <br><br>The technical answer to this data quality problem is to implement rigorous data validation and cleansing routines, to make sure that the records are complete and accurate. But this would create more work for the GP practices uploading the data. Officials at the Department of Health fear that setting the standards of data quality too high would kill the scheme altogether. (And even the most rigorous quality standards would only reduce the number of errors, could never eliminate them altogether.)<br><br>There is a fundamental conflict of interest here between the providers of data and the consumers - even though these may be the same people - and between quality and quantity. If you measure the success of the scheme in terms of the number of records uploaded, then you are obviously going to get quantity at the expense of quality.<br><br>So the pusillanimous way out is to build a database with imperfect data, and defer the quality problem until later. That's what people have always done, and will continue to do, and the poor quality data will never ever get fixed.<br><br>The second problem is that even if perfectly complete and accurate data are possible, the validation and data cleansing step generally introduces some latency into the process, especially if you are operating a <a href="http://rvsoapbox.blogspot.com/2008/11/post-before-processing.html">post-before-processing</a> system (particularly relevant to environments such as military and healthcare where, for some strange reason, matters of life-and-death seem to take precedence over getting the paperwork right). So there is a design trade-off between two dimensions of quality - timeliness and accuracy. See my post on <a href="http://rvsoapbox.blogspot.com/2007/05/joined-up-healthcare.htm">Joined-Up Healthcare</a>.<br><br>The third problem is complexity. Data cleansing generally works by comparing each record with a fixed schema, which defines the expected structure and rules (metadata) to which each record must conform, so that any information that doesn't fit into this fixed schema will be barred or adjusted. Thus the richness of information will be attenuated, and useful and meaningful information may be filtered out. (See Jon Udell's piece on <a href="http://jonudell.net/bytecols/2000-03-29.html">Object Data and the Procrustean Bed</a> from March 2000. See also my presentation on <a href="http://www.slideshare.net/RichardVeryard/soa-for-data-management">SOA for Data Management</a>.)<br><br>The final problem is that a single source of information represents a single source of failure. If something is really important, it is better to have two independent sources of information or intelligence, as I pointed out in my piece on <a href="http://rvsoapbox.blogspot.com/2008/03/information-algebra.html">Information Algebra</a>. This follows Bateson's slogan that "two descriptions are better than one". Doctors using the SCR database appear to understand this aspect of real-world information better than the database designers.<br><br>It may be a very good idea to build an information service that provides improved access to patient information, for those who need this information. But if this information service is designed and implemented according to some simplistic dogma, then it isn't going to work properly.<br><br><hr>Update. The Health Secretary has announced that NHS regulation will be based on a single version of the truth.<br><br><blockquote>"in the future the chief inspector will ensure that there is a single  version of the truth about how their hospitals are performing, not just  on finance and targets, but on a single assessment that fully reflects  what matters to patients" </blockquote><br>Roger Taylor, <a href="http://www.guardian.co.uk/commentisfree/2013/mar/26/jeremy-hunt-hospitals-mid-staffs">Jeremy Hunt's dangerous belief in a single 'truth' about hospitals</a> (Guardian 26 March 2013)<br><br><br><br><span>Updated 28 March 2013</span>]]></summary>
    <content type="html"><![CDATA[As @<a href="http://twitter.com/tonyrcollins/status/10716072556">tonyrcollins</a> reports, a confidential report currently in preparation on the NHS Summary Care Records (SCR) database will reveal serious flaws in a massively expensive database (<a href="http://www.computerweekly.com/blogs/tony_collins/2010/03/confidential-report-on-summary.html">Computer Weekly, March 2010</a>). Well knock me down with a superbug, whoever would have guessed this might happen?<br><br><blockquote>"The final report may conclude that the success of SCRs will depend on whether the NHS, Connecting for Health and the Department of Health can bridge the deep cultural and institutional divides that have so far characterised the NPfIT. It may also ask whether the government founded the SCR on an unrealistic assumption: that the centralised database could ever be a single source of truth."</blockquote><br>There are several reasons to be ambivalent about the twin principles Single Version of Truth (SVOT) and Single Source of Truth (SSOT), and this kind of massive failure must worry even the most fervent advocates of these principles.<br><br>Don't get me wrong, I have served my time in countless projects trying to reduce the proliferation and fragmentation of data and information in large organizations, and I am well aware of the technical costs and business risks associated with data duplication. However, I have some serious concerns about the dogmatic way these principles are often interpreted and implemented, especially when this dogmatism results (as seems to be the case here) in a costly and embarrassing failure.<br><br>The first problem is that Single-Truth only works if you have absolute confidence in the quality of the data. In the SCR example, there is evidence that doctors simply don't trust the new system - and with good reason. There are errors and omissions in the summary records, and doctors prefer to double-check details of medications and allergies, rather than take the risk of relying on a single source. <br><br>The technical answer to this data quality problem is to implement rigorous data validation and cleansing routines, to make sure that the records are complete and accurate. But this would create more work for the GP practices uploading the data. Officials at the Department of Health fear that setting the standards of data quality too high would kill the scheme altogether. (And even the most rigorous quality standards would only reduce the number of errors, could never eliminate them altogether.)<br><br>There is a fundamental conflict of interest here between the providers of data and the consumers - even though these may be the same people - and between quality and quantity. If you measure the success of the scheme in terms of the number of records uploaded, then you are obviously going to get quantity at the expense of quality.<br><br>So the pusillanimous way out is to build a database with imperfect data, and defer the quality problem until later. That's what people have always done, and will continue to do, and the poor quality data will never ever get fixed.<br><br>The second problem is that even if perfectly complete and accurate data are possible, the validation and data cleansing step generally introduces some latency into the process, especially if you are operating a <a href="http://rvsoapbox.blogspot.com/2008/11/post-before-processing.html">post-before-processing</a> system (particularly relevant to environments such as military and healthcare where, for some strange reason, matters of life-and-death seem to take precedence over getting the paperwork right). So there is a design trade-off between two dimensions of quality - timeliness and accuracy. See my post on <a href="http://rvsoapbox.blogspot.com/2007/05/joined-up-healthcare.htm">Joined-Up Healthcare</a>.<br><br>The third problem is complexity. Data cleansing generally works by comparing each record with a fixed schema, which defines the expected structure and rules (metadata) to which each record must conform, so that any information that doesn't fit into this fixed schema will be barred or adjusted. Thus the richness of information will be attenuated, and useful and meaningful information may be filtered out. (See Jon Udell's piece on <a href="http://jonudell.net/bytecols/2000-03-29.html">Object Data and the Procrustean Bed</a> from March 2000. See also my presentation on <a href="http://www.slideshare.net/RichardVeryard/soa-for-data-management">SOA for Data Management</a>.)<br><br>The final problem is that a single source of information represents a single source of failure. If something is really important, it is better to have two independent sources of information or intelligence, as I pointed out in my piece on <a href="http://rvsoapbox.blogspot.com/2008/03/information-algebra.html">Information Algebra</a>. This follows Bateson's slogan that "two descriptions are better than one". Doctors using the SCR database appear to understand this aspect of real-world information better than the database designers.<br><br>It may be a very good idea to build an information service that provides improved access to patient information, for those who need this information. But if this information service is designed and implemented according to some simplistic dogma, then it isn't going to work properly.<br><br><hr>Update. The Health Secretary has announced that NHS regulation will be based on a single version of the truth.<br><br><blockquote>"in the future the chief inspector will ensure that there is a single  version of the truth about how their hospitals are performing, not just  on finance and targets, but on a single assessment that fully reflects  what matters to patients" </blockquote><br>Roger Taylor, <a href="http://www.guardian.co.uk/commentisfree/2013/mar/26/jeremy-hunt-hospitals-mid-staffs">Jeremy Hunt's dangerous belief in a single 'truth' about hospitals</a> (Guardian 26 March 2013)<br><br><br><br><span>Updated 28 March 2013</span>]]></content>
  </entry>
</feed>
