<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>TrendMiner Blog</title>
    <link>https://1838475.hs-sites.com/blog</link>
    <description>big data analytics and trend discovery for industrial process optimization  Blog update mail:</description>
    <language>en-us</language>
    <pubDate>Wed, 30 Nov 2016 13:49:26 GMT</pubDate>
    <dc:date>2016-11-30T13:49:26Z</dc:date>
    <dc:language>en-us</dc:language>
    <item>
      <title>Transparency is a verb</title>
      <link>https://1838475.hs-sites.com/blog/transparency-is-a-verb</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/transparency-is-a-verb" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/Transparency-Strategy.jpg" alt="Transparency-Strategy.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;em&gt;When we started building the 6 pillars of &lt;a href="https://1838475.hs-sites.com/joint-innovation/"&gt;JOINT INNOVATION&lt;/a&gt; about a year ago, transparency came up as one &lt;/em&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/transparency-is-a-verb" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/Transparency-Strategy.jpg" alt="Transparency-Strategy.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;em&gt;When we started building the 6 pillars of &lt;a href="https://1838475.hs-sites.com/joint-innovation/"&gt;JOINT INNOVATION&lt;/a&gt; about a year ago, transparency came up as one &lt;/em&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=1838475&amp;amp;k=14&amp;amp;r=https%3A%2F%2F1838475.hs-sites.com%2Fblog%2Ftransparency-is-a-verb&amp;amp;bu=https%253A%252F%252F1838475.hs-sites.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Mon, 18 Jul 2016 08:54:00 GMT</pubDate>
      <author>hans@trendminer.com (Hans De Leenheer)</author>
      <guid>https://1838475.hs-sites.com/blog/transparency-is-a-verb</guid>
      <dc:date>2016-07-18T08:54:00Z</dc:date>
    </item>
    <item>
      <title>Self-service analytics for the subject matter expert</title>
      <link>https://1838475.hs-sites.com/blog/self-service-analytics-for-the-subject-matter-expert-1</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/self-service-analytics-for-the-subject-matter-expert-1" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/ai_0-1024x683.jpg" alt="ai_0-1024x683.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;em&gt;Recently I came across an article by Peter Reynolds (Analyst, ARC Advisory Group), where he asks, “&lt;/em&gt;&lt;a href="http://industrial-iot.com/2016/06/will-machine-learning-eat-historian"&gt;&lt;em&gt;Will Machine Learning eat&lt;/em&gt;&lt;em&gt; Historian?&lt;/em&gt;&lt;/a&gt;&lt;em&gt;”. His conclusion was; “Yes, for breakfast”. As usual, Peter’s comments are insightful and well educated. Today I would like to take the opportunity to add a couple of my own thoughts on the matter.&lt;/em&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/self-service-analytics-for-the-subject-matter-expert-1" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/ai_0-1024x683.jpg" alt="ai_0-1024x683.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;em&gt;Recently I came across an article by Peter Reynolds (Analyst, ARC Advisory Group), where he asks, “&lt;/em&gt;&lt;a href="http://industrial-iot.com/2016/06/will-machine-learning-eat-historian"&gt;&lt;em&gt;Will Machine Learning eat&lt;/em&gt;&lt;em&gt; Historian?&lt;/em&gt;&lt;/a&gt;&lt;em&gt;”. His conclusion was; “Yes, for breakfast”. As usual, Peter’s comments are insightful and well educated. Today I would like to take the opportunity to add a couple of my own thoughts on the matter.&lt;/em&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=1838475&amp;amp;k=14&amp;amp;r=https%3A%2F%2F1838475.hs-sites.com%2Fblog%2Fself-service-analytics-for-the-subject-matter-expert-1&amp;amp;bu=https%253A%252F%252F1838475.hs-sites.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>ARC</category>
      <category>Data Historian</category>
      <category>Machine Learning</category>
      <category>Peter Reynolds</category>
      <category>Self-Service Analytics</category>
      <pubDate>Thu, 07 Jul 2016 12:17:00 GMT</pubDate>
      <guid>https://1838475.hs-sites.com/blog/self-service-analytics-for-the-subject-matter-expert-1</guid>
      <dc:date>2016-07-07T12:17:00Z</dc:date>
      <dc:creator>Bert Baeck</dc:creator>
    </item>
    <item>
      <title>Development for and with the end-users</title>
      <link>https://1838475.hs-sites.com/blog/development-for-and-with-the-end-users</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/development-for-and-with-the-end-users" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/shutterstock_392188633-1024x684.jpg" alt="shutterstock_392188633-1024x684.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;i&gt;In a first of 6 posts about our pillars of &lt;strong&gt;JOINT INNOVATION&lt;/strong&gt;, I talked about how we want to &lt;a href="https://1838475.hs-sites.com/lowering-barrier-collaboration/"&gt;lower and eliminate the barriers of collaboration&lt;/a&gt; with our customers in order to get as much feedback as possible. In this second post I want to shed some light on how that collaboration trickles down into our development cycle. If there is one place where JOINT INNOVATION should shine, it is here of course.&lt;/i&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/development-for-and-with-the-end-users" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/shutterstock_392188633-1024x684.jpg" alt="shutterstock_392188633-1024x684.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;i&gt;In a first of 6 posts about our pillars of &lt;strong&gt;JOINT INNOVATION&lt;/strong&gt;, I talked about how we want to &lt;a href="https://1838475.hs-sites.com/lowering-barrier-collaboration/"&gt;lower and eliminate the barriers of collaboration&lt;/a&gt; with our customers in order to get as much feedback as possible. In this second post I want to shed some light on how that collaboration trickles down into our development cycle. If there is one place where JOINT INNOVATION should shine, it is here of course.&lt;/i&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=1838475&amp;amp;k=14&amp;amp;r=https%3A%2F%2F1838475.hs-sites.com%2Fblog%2Fdevelopment-for-and-with-the-end-users&amp;amp;bu=https%253A%252F%252F1838475.hs-sites.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Mon, 04 Jul 2016 12:20:00 GMT</pubDate>
      <author>hans@trendminer.com (Hans De Leenheer)</author>
      <guid>https://1838475.hs-sites.com/blog/development-for-and-with-the-end-users</guid>
      <dc:date>2016-07-04T12:20:00Z</dc:date>
    </item>
    <item>
      <title>Lowering the barriers of collaboration</title>
      <link>https://1838475.hs-sites.com/blog/lowering-the-barriers-of-collaboration</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/lowering-the-barriers-of-collaboration" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/road-blocks3.jpg" alt="road-blocks3.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;When we started defining our 6 pillars of &lt;a href="https://1838475.hs-sites.com/joint-innovation/#tabs3"&gt;JOINT INNOVATION&lt;/a&gt;, I knew that &lt;u&gt;#3 The Lowest Barrier of collaboration&lt;/u&gt; was the one that would really set us apart from [all] other players in the market. Looking at the dynamics of the &lt;i&gt;software for industrial manufacturers&lt;/i&gt; market, the majority of the suppliers are Goliaths that have been around for a couple of decades. A natural result of these players is that they have internal structures for collaboration that are based on operational efficiency. At TrendMiner we are a young and agile team that want to do this differently and &lt;u&gt;&lt;strong&gt;focus our processes on the delivery to the customer&lt;/strong&gt;&lt;/u&gt;.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/lowering-the-barriers-of-collaboration" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/road-blocks3.jpg" alt="road-blocks3.jpg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;When we started defining our 6 pillars of &lt;a href="https://1838475.hs-sites.com/joint-innovation/#tabs3"&gt;JOINT INNOVATION&lt;/a&gt;, I knew that &lt;u&gt;#3 The Lowest Barrier of collaboration&lt;/u&gt; was the one that would really set us apart from [all] other players in the market. Looking at the dynamics of the &lt;i&gt;software for industrial manufacturers&lt;/i&gt; market, the majority of the suppliers are Goliaths that have been around for a couple of decades. A natural result of these players is that they have internal structures for collaboration that are based on operational efficiency. At TrendMiner we are a young and agile team that want to do this differently and &lt;u&gt;&lt;strong&gt;focus our processes on the delivery to the customer&lt;/strong&gt;&lt;/u&gt;.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=1838475&amp;amp;k=14&amp;amp;r=https%3A%2F%2F1838475.hs-sites.com%2Fblog%2Flowering-the-barriers-of-collaboration&amp;amp;bu=https%253A%252F%252F1838475.hs-sites.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Joint Innovation</category>
      <pubDate>Fri, 01 Apr 2016 12:24:00 GMT</pubDate>
      <author>hans@trendminer.com (Hans De Leenheer)</author>
      <guid>https://1838475.hs-sites.com/blog/lowering-the-barriers-of-collaboration</guid>
      <dc:date>2016-04-01T12:24:00Z</dc:date>
    </item>
    <item>
      <title>Musings on the ARC Analyst Conferences</title>
      <link>https://1838475.hs-sites.com/blog/musings-on-the-arc-analyst-conferences</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/musings-on-the-arc-analyst-conferences" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/Screenshot-2016-02-25-20.51.18-e1457616147872-1024x519.png" alt="Screenshot-2016-02-25-20.51.18-e1457616147872-1024x519.png" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;the ARC Conferences&lt;/h2&gt; 
&lt;p&gt;&lt;em&gt;During the last month we have attended both the ARC conferences in Orlando Florida &amp;amp; Amsterdam as a sponsor. ARC Advisory Group [&lt;a href="http://www.arcweb.com/"&gt;link&lt;/a&gt;] is the leading analyst firm for the process &amp;amp; manufacturing industry. For &lt;strong&gt;Trend&lt;/strong&gt;Miner this was our first official appearance at an industry conference. One of my primary goals for these events was confirmation of our vision by peers in the industry. More on that at the end of this post. Secondly this was also my personal first attendance to public events in this industry since my previous ventures have been more focused in the datacenter technology space. In this post I will try to share a couple of my first musings on the subjects at hand.&lt;/em&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/musings-on-the-arc-analyst-conferences" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/Screenshot-2016-02-25-20.51.18-e1457616147872-1024x519.png" alt="Screenshot-2016-02-25-20.51.18-e1457616147872-1024x519.png" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;h2&gt;the ARC Conferences&lt;/h2&gt; 
&lt;p&gt;&lt;em&gt;During the last month we have attended both the ARC conferences in Orlando Florida &amp;amp; Amsterdam as a sponsor. ARC Advisory Group [&lt;a href="http://www.arcweb.com/"&gt;link&lt;/a&gt;] is the leading analyst firm for the process &amp;amp; manufacturing industry. For &lt;strong&gt;Trend&lt;/strong&gt;Miner this was our first official appearance at an industry conference. One of my primary goals for these events was confirmation of our vision by peers in the industry. More on that at the end of this post. Secondly this was also my personal first attendance to public events in this industry since my previous ventures have been more focused in the datacenter technology space. In this post I will try to share a couple of my first musings on the subjects at hand.&lt;/em&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=1838475&amp;amp;k=14&amp;amp;r=https%3A%2F%2F1838475.hs-sites.com%2Fblog%2Fmusings-on-the-arc-analyst-conferences&amp;amp;bu=https%253A%252F%252F1838475.hs-sites.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>ARC</category>
      <category>Conference</category>
      <pubDate>Thu, 10 Mar 2016 13:28:00 GMT</pubDate>
      <author>hans@trendminer.com (Hans De Leenheer)</author>
      <guid>https://1838475.hs-sites.com/blog/musings-on-the-arc-analyst-conferences</guid>
      <dc:date>2016-03-10T13:28:00Z</dc:date>
    </item>
    <item>
      <title>Why we built TrendMiner</title>
      <link>https://1838475.hs-sites.com/blog/why-we-built-trendminer</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/why-we-built-trendminer" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/BertTijd1.jpeg" alt="BertTijd1.jpeg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p class="p1"&gt;&lt;em&gt;&lt;span class="s1"&gt;When we started D square our BHAG (Big Hairy Audacious Goal) was to &lt;span style="text-decoration: underline;"&gt;&lt;strong&gt;change the way the process and manufacturing industry uses machine generated data, based on scientific research&lt;/strong&gt;&lt;/span&gt;. When I look today at what TrendMiner has become, I can separate the root causes of who we are and why we are here in 3 main segments:&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://1838475.hs-sites.com/blog/why-we-built-trendminer" title="" class="hs-featured-image-link"&gt; &lt;img src="https://1838475.hs-sites.com/hubfs/blog-assets/images/post-images/BertTijd1.jpeg" alt="BertTijd1.jpeg" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p class="p1"&gt;&lt;em&gt;&lt;span class="s1"&gt;When we started D square our BHAG (Big Hairy Audacious Goal) was to &lt;span style="text-decoration: underline;"&gt;&lt;strong&gt;change the way the process and manufacturing industry uses machine generated data, based on scientific research&lt;/strong&gt;&lt;/span&gt;. When I look today at what TrendMiner has become, I can separate the root causes of who we are and why we are here in 3 main segments:&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=1838475&amp;amp;k=14&amp;amp;r=https%3A%2F%2F1838475.hs-sites.com%2Fblog%2Fwhy-we-built-trendminer&amp;amp;bu=https%253A%252F%252F1838475.hs-sites.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Thoughts</category>
      <category>CEO</category>
      <pubDate>Wed, 06 Jan 2016 13:31:00 GMT</pubDate>
      <guid>https://1838475.hs-sites.com/blog/why-we-built-trendminer</guid>
      <dc:date>2016-01-06T13:31:00Z</dc:date>
      <dc:creator>Bert Baeck</dc:creator>
    </item>
  </channel>
</rss>
