<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[TimeSeries - Medium]]></title>
        <description><![CDATA[We leverage cutting edge technology in the field of Big Data and Rapid Application Development (RAD) to create smart apps, and next generation applications. - Medium]]></description>
        <link>https://medium.com/timeseries?source=rss----6d3bd69b4d63---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>TimeSeries - Medium</title>
            <link>https://medium.com/timeseries?source=rss----6d3bd69b4d63---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:31:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/timeseries" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Mendix acquisition by Siemens — a view from a Mendix MVP]]></title>
            <link>https://medium.com/timeseries/the-mendix-acquisition-by-siemens-a-view-from-a-mendix-mvp-2697b1fffb7a?source=rss----6d3bd69b4d63---4</link>
            <guid isPermaLink="false">https://medium.com/p/2697b1fffb7a</guid>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[siemens]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[big-data]]></category>
            <dc:creator><![CDATA[Paul Ketelaars]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 06:53:16 GMT</pubDate>
            <atom:updated>2018-08-13T06:54:01.125Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week it was announced, and widely picked up by news sites that <a href="https://www.linkedin.com/company/siemens/">Siemens</a> will acquire <a href="https://www.linkedin.com/company/mendix/">Mendix</a> for approximately 730M USD. Mendix’ CEO Derek Roos <a href="https://www.mendix.com/blog/siemens-to-acquire-mendix/">wrote a blog</a> about what the acquisition entails, Johan Den Haan’s (Mendix CTO) <a href="https://www.mendix.com/blog/mendix-and-siemens-to-re-define-the-future-of-application-development/">blog </a>focusses more on the vision of the product, and other blogs describing their view on the move by Siemens to acquire Mendix. I encourage everyone to read these blogs as they give a good insight in the how and what of Siemens ❤ Mendix.</p><p>There are a lot of great blogs out there, detailing the acquisition (see some links below) but we haven’t read anything about what this might mean for a Mendix developer; someone who uses the Mendix platform daily to create innovative smart apps. That’s where this blog comes in. A small disclaimer is that this blog is written from a personal view; I don’t have any inside information about things that will happen; this is just a blog about what I feel it might mean.</p><h3>Mindsphere &amp; Mendix</h3><p>At Mendix World 2016, Smart Apps were introduced as “the new generation of apps” using, among others, Big Data, IoT and Machine Learning. Since then, a bunch of Connectors have been added to the <a href="https://appstore.home.mendix.com/index3.html">Mendix App Store</a>. These connectors allow us to connect to various IoT/ML services such as IBM Watson, MQTT, AWS and more. <a href="https://siemens.mindsphere.io/">MindSphere</a>, being Siemens’ Open IoT platform, seems like a perfect fit for Mendix as we could use the Mindsphere APIs to enrich our apps. Imagine this being integrated in a single platform…</p><p>The combination could prove very powerful, making it <em>even </em>easier for developers to build <em>even </em>better Smart Apps.</p><h3>Low Code IoT &amp; Machine Learning</h3><p>Currently implementing IoT sensors and using its data still requires a bit of technical know-how. IoT is mainly focused on the hardware, with new sensors being developed and released every hour (or so it seems). The same goes for Machine Learning; there’s no out-of-the-box solution for getting started with Machine Learning, and integrating it in your apps has a hefty technical component to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QmLL5v3BBzdKUPMS" /></figure><p>That’s why combining Mendix and Mindsphere seems like the only logical next step. It could be seen as the first low-code IoT/ML platform! Which in its turn is <strong>huge</strong>. Removing the technical ‘barrier’ from IoT allows for a much broader adoption. Even smarter apps, more developers, more resources; the possibilities are endless!</p><p>Besides this, being part of the Siemens family gives an influx of new money. As Siemens stated it will keep investing in Mendix’ R&amp;D it will gain even more momentum. This commitment is a sign that being a part of Mendix, whether as a developer or anything else, was the right choice!</p><p>As Derek Roos stated in his blog:</p><blockquote><em>“…</em> <strong><em>you now have the benefit of working with a leader in the low-code market, who has the might of a multi-billion-dollar, global enterprise behind them.</em></strong> <em>If you’ve ever wondered which low-code platform will have the viability to invest and win in the long term, you no longer have to guess. This commitment and investment from Siemens will allow us to accelerate R&amp;D and geo-expansion investments significantly. You’re going to see faster innovation, more reach and an even better customer experience from us.”</em></blockquote><p>And me? I’m just excited for what the future will bring. Starting with Mendix almost 6 years ago is still one of the best decisions I’ve made, and I’m not close to being done!</p><p>Interesting articles / blogs about the acquisition:</p><ul><li><a href="https://www.mendix.com/blog/siemens-to-acquire-mendix/">https://www.mendix.com/blog/siemens-to-acquire-mendix/</a> — <a href="https://www.linkedin.com/in/derekroos/">Derek Roos</a> (Mendix CEO)</li><li><a href="https://www.mendix.com/blog/mendix-and-siemens-to-re-define-the-future-of-application-development/">https://www.mendix.com/blog/mendix-and-siemens-to-re-define-the-future-of-application-development/</a> — <a href="https://www.linkedin.com/in/johandenhaan/">Johan Den Haan</a> (Mendix CTO)</li><li><a href="https://www.linkedin.com/pulse/how-fits-bigger-picture-vincent-soek/">https://www.linkedin.com/pulse/how-fits-bigger-picture-vincent-soek/</a> — <a href="https://www.linkedin.com/in/vincentsoek/">Vincent Soek</a>(Global Lead Legal Affairs Mendix)</li><li><a href="https://www.linkedin.com/pulse/what-means-work-towards-major-exit-mendix-acquired-coen-van-duiven/">https://www.linkedin.com/pulse/what-means-work-towards-major-exit-mendix-acquired-coen-van-duiven/</a> <a href="https://www.linkedin.com/in/coen-van-duiven/">— Coen van Duiven</a> (HENQ Capital Partners, VC)</li><li><a href="https://overcast.fm/+JqEYrgtcg">https://overcast.fm/+JqEYrgtcg</a> — Podcast (Dutch) by <a href="https://www.linkedin.com/in/pimvdnoll/">Pim van der Noll</a> (fellow Mendix MVP)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2697b1fffb7a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeseries/the-mendix-acquisition-by-siemens-a-view-from-a-mendix-mvp-2697b1fffb7a">The Mendix acquisition by Siemens — a view from a Mendix MVP</a> was originally published in <a href="https://medium.com/timeseries">TimeSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How TimeSeries Uses React to Improve Performance and UX]]></title>
            <link>https://medium.com/timeseries/how-timeseries-uses-react-to-improve-performance-and-ux-ea3967ee3136?source=rss----6d3bd69b4d63---4</link>
            <guid isPermaLink="false">https://medium.com/p/ea3967ee3136</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[timeseries]]></category>
            <dc:creator><![CDATA[Freek Brinkhuis]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 08:04:02 GMT</pubDate>
            <atom:updated>2018-06-06T08:03:44.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m6rLGMIQ4PSJfG8pdygvoQ.png" /></figure><p>At <a href="http://timeseries.nl/">TimeSeries</a>, we believe in using new technologies to develop innovative solutions. The Mendix <a href="https://www.mendix.com/low-code-guide/">low-code</a> development platform enables us to experiment and achieve results quickly and to develop apps faster than if we were to build apps with traditional development.</p><p>One example is that Mendix provides developers with a Widget Development toolkit that can be used to create more complex interface components and functionality. These widgets can be utilized to enhance Mendix’ standard set of interface components. The Mendix App store is a good place to start when you are looking for components and modules that are developed by the community.</p><p>Developing custom widgets for Mendix enables us to create a balance between the Low-Code power of Mendix and mesmerizing user experiences created with the latest techniques in the world of Javascript and CSS for specific use cases. This can range from applying <a href="https://threejs.org/">three.js</a> (3d animations) to developing a <a href="https://appstore.home.mendix.com/link/app/106194/">Snake game</a>. Creating custom widgets for Mendix allows us to do what the platform can’t do out-of-the-box.</p><p>So how does <a href="https://reactjs.org/">React</a> fit into all this? Well, the Mendix front-end framework is based on the Dojo Toolkit, a framework that rose to greatness during the time when jQuery did not even exist yet. Dojo opened up the world of front-end development to a whole new audience and it is still used by a fair share of organizations. React, however, has some advantages over the Dojo framework. First of all, there are a lot more experienced React developers nowadays and therefore it is easier to find resources in this area of expertise.</p><p>Another advantage is the way that React handles DOM rendering by introducing the Virtual DOM. This means that React uses a component based UI structure. The developer splits up a complex interface into smaller components that can all manage their own state. In addition to the performance gains, these reusable and fast components can result in a significantly faster development time.</p><p>So what do you do when you want to develop complex widgets for Mendix but you don’t want to build it with Dojo? You start experimenting. There is already a lot of documentation available on using React in a Mendix widget. Even the Mendix R&amp;D department shared some thoughts and examples about Mendix and React back in 2017 with a <a href="https://github.com/cdcharlebois/gulp-react">code example</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*da7HmR4Q-r47fbFR.jpg" /><figcaption>The TimeSeries Automatic Planning demo build with React and Mendix</figcaption></figure><p>A good example of a React implementation at TimeSeries is the development of a visual planning tool. This tool had several requirements that would be difficult to achieve with 100 percent native Mendix. We needed a widget that allowed for the manipulation of a schedule and that was capable of visualizing this schedule in a timeline. The individual items on the schedule had to be movable by drag and drop features. The interface logic -like the drag and drop functionality- was built into the widget including the visualization of the whole schedule. All the validations and business logic for manipulating the schedule and assigning tickets to resources were handled by microflows in Mendix. This enabled us to keep the business logic in the backend and develop with the speed of Mendix while all the interface logic was handled by the widget.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6CYKE6UPiQAlp2Ph.jpg" /></figure><p>First, we created the Mendix domain model for the widget. Then we created the microflows that needed to be executed by the React widget to perform the backend tasks. Next, we started the development of the actual React widget. We first set up the React app in which we created a few objects that mimicked the behavior of the Dojo wrapper (exposing the <em>mx </em>object and <em>this.contextObj</em>). Once we were happy with the result, we created a production build and wrapped it in the Dojo widget by turning it into an AMD module and by modifying some of the minified code to work with the Dojo toolkit.</p><p>A few bug fixes later we were finished and the work had paid off: Our React widget had leveraged a lot that the framework has to offer. What had helped us the most is the handling of transitions between states in React. Since the single widget had to handle multiple actions and contained multiple views, we wanted smooth transitions and low loading times. Handling the data manipulations inside the widget also increased the performance of the app.</p><p>Overall it has proven to be a great way for us to create more immersive user experiences while not compromising on the speed and power of the Mendix platform and we will definitely keep experimenting with React in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea3967ee3136" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeseries/how-timeseries-uses-react-to-improve-performance-and-ux-ea3967ee3136">How TimeSeries Uses React to Improve Performance and UX</a> was originally published in <a href="https://medium.com/timeseries">TimeSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Riddle Me Mendix? A challenging puzzle for all developers!]]></title>
            <link>https://medium.com/timeseries/riddle-me-mendix-a-challenging-puzzle-for-all-developers-fb583a3a537c?source=rss----6d3bd69b4d63---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb583a3a537c</guid>
            <category><![CDATA[fun]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[puzzle]]></category>
            <category><![CDATA[challenge]]></category>
            <dc:creator><![CDATA[Willem van Zantvoort]]></dc:creator>
            <pubDate>Mon, 28 May 2018 09:33:35 GMT</pubDate>
            <atom:updated>2018-05-28T09:33:35.453Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi there! I’d like to introduce you all to Derrek.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFWYSOyOl1gQQZx9PSLCZA.png" /></figure><p>Derrek is a young, enthusiastic professional living in the Netherlands. With a background in marketing and commerce he has had multiple jobs, but as he got older he was feeling more in need of a new challenge. So, recently he decided he wanted a new career and found the perfect company to apply at. Innovation is what drives the organization; Derrek was sold.</p><p>As Mendix enables business and developers to work together closely, he figured that this might be an excellent tool for him to use. He knew however, that the company he was applying for only hired the best of the best, so the interview was probably not going to be easy.</p><p>As it turned out, he aced the first interview! He had the right mentality and his affinity for IT was a big plus. Quickly after his first interview he was invited to return for a second interview. Only this time he was asked to finish a puzzle beforehand, one which should separate the wheat from the chaff. Time to see if he’s really as good as he claimed to be.</p><p>Sooo, long story short: he might need some help with this last interview. Can you help him get the job of a lifetime? Click <a href="https://riddlememendix.mxapps.io/">here</a> to get started right away (or visit <a href="http://riddlememendix.mxapps.io/">http://riddlememendix.mxapps.io</a>)! If you help him finish it, he might even buy you a coffee as a thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb583a3a537c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeseries/riddle-me-mendix-a-challenging-puzzle-for-all-developers-fb583a3a537c">Riddle Me Mendix? A challenging puzzle for all developers!</a> was originally published in <a href="https://medium.com/timeseries">TimeSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SVB UWV Hackathon 2017: Blockchain + Facial Recognition + 24h? No problem!]]></title>
            <link>https://medium.com/timeseries/6am-saturday-morning-4a4205794138?source=rss----6d3bd69b4d63---4</link>
            <guid isPermaLink="false">https://medium.com/p/4a4205794138</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[timeseries]]></category>
            <category><![CDATA[facial-recognition]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Wieke Bouten]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 14:41:33 GMT</pubDate>
            <atom:updated>2018-01-15T14:41:33.391Z</atom:updated>
            <content:encoded><![CDATA[<p>6AM, Saturday morning. Half-asleep I start gathering my things (“what do I need to bring?!”) before quickly getting in my car: It’s Hackathon day! On the drive over to Eindhoven I start thinking about the e-mail I received last night, informing us on which case we were assigned.</p><p>What would the best approach be to tackle the issue?</p><p>Which techniques can we use?</p><p>Will it be feasible in 24 short hours?</p><p>We were assigned case two (out of five), asking us to provide an answer to the ‘alternative proof of life’ challenge. The government institution(s) at hand has the following problem:</p><p>Every day, thousands of people are entitled to various government benefits. When these people reside in the Netherlands, it is easy to check whether or not a person is still alive and should still be receiving his or her payments. In our surrounding countries this gets more difficult, as not every country can or wants to open up their registers to our government to check for this data. If you however know that this organization serves people in over 200 countries in every ‘corner’ of the globe, you see where a problem may arise. How do we know this person is still alive?</p><p>At this moment recipients are required to, once a year, go to a government official in their respective country. Who this government official is? We don’t know. What institution or organization? We don’t know that either. One of the ‘subject matter experts’ present at the hackathon could tell me there are several countries with surprisingly high numbers of clients that are well over 120 year old, and still receiving payments. Of course I believe the local climate could do wonders for a person’s health, but these numbers are understandably viewed with some skepticism.</p><p>In other words, fraud is a big problem. People pass away, and their partner/relatives/neighbors keep collecting their payments en masse.</p><p>Aside from this, there are more issues. People often have to spend much effort to visit such a government official, both time- and resource-wise. The process is cumbersome for all parties involved and imperfect at best. In this modern golden age of information technology, data revolutions and RAD development, surely there must be something better we can think of?</p><p><strong>&gt;&gt; ENTER UWV/SVB HACKATHON &lt;&lt;</strong></p><p>So that’s what we set out to fix. Easy enough, right?</p><p>Filled up on espresso and chicken wings –<em>I’m taking a moment here to express my full-blown love for the cantina-chef and his crew because wow, that was some good chicken. Tender, great crust, delicious seasoning, not too thick: just right</em> — me and my teammates from TimeSeries (Larn van de Vries, Richard Edens and Adnan Ramlawi) gathered ‘round a flipover and put on our thinking caps.</p><p>We all agreed we needed to solve the issues for both ends of the process: the end-user and the government employee. Employees now on average spend 6 minutes per case: a number we believe can be decreased significantly, while providing better information. A clear, easy-to-use screen on which reviewers get all relevant information and can efficiently make their decision. But what information would you want on this screen? Of course we have some personal details and perhaps even a phone number, but what would you need to know if someone is still in the land of the living?</p><p><strong>&gt;&gt;HERE’S WHAT WE CAME UP WITH&lt;&lt;</strong></p><p>According to us, there are two main concerns when requesting, receiving and reviewing think kind of information digitally.</p><p>1. Is this really the actual person I have to look into?</p><p>2. How do I know this has not been pre-recorded/prepared/digitally altered, i.e. how do I know it’s <em>recent</em>?</p><p>In our solution we addressed both questions. We created a personal environment for every end-user the issuing government wants a PoL (Proof of Life) from, in which he or she can see what the current status of the case is, and what is expected of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*mIoAUi9F5Td9iW8hj1yJsw.png" /><figcaption>User dashboard</figcaption></figure><p>After agreeing to the terms, a ‘wizard’ processflow starts, in which the user is asked to follow the instructions and perform some actions. We first ask the user to show his passport(-photo) and take a picture. In the next step a visual overlay helps the user to successfully perform the next action: take a selfie.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qEziw2A75kHm5mn0PH1UwA.png" /><figcaption>Step 1 and 2: picture time!</figcaption></figure><p><strong>Wait, but why?</strong></p><p>Fair question: I’ll explain. After taking these two pictures, we send them to a cognitive facial recognition and comparison API. Using these verification processing services, we can see the outcome of a number of questions, of which to us the most relevant are: Is what I am seeing in the second picture a real person (and not a photograph) and are these two photos depicting the same person (opposed to a sibling, offspring, crabperson or whatnot). This results in a score (0–100) that tells us how likely it this that the person in the two photos is in fact the same. What you can do with this score will be addressed later, but wait…</p><p>That’s not all of it.</p><p>Our third step deals with the question of how recent this material is. The person in front of the webcam might as well be an illicit illusional intellect, a digital deceptive desperado, a genuine- oh well you get the picture (pun intended).</p><p>To deal with this, we ask the user to record a short movie. In this he or she needs to do two things: read a randomly generated sentence out loud, while performing a (as far as the user knows) equally random task. This sentence and task is what tells us this recording is recent: there are so many variations, this cannot be pre-recorded. The combination is tied to today’s timestamp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/838/1*eVu28mQtEyieXeFR1tIXPg.png" /><figcaption>Step 3</figcaption></figure><p>Record, press, send: that’s it! Using an internet-enabled device with camera, the user can do in 2 minutes what previously would take him a day (or more): how’s that for convenience!</p><p>Now it’s up to the government employee to review the case.</p><p>Using a personalized dashboard and workload (I’m not going to keep spamming pictures, just believe me it exists) he can search for and start the review process of the supplied PoL. In this case detail screen they see the person’s personal details and contact data, a timeline of events, and more importantly: the sent information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1JiZV2bn63nIanteqrfq0g.png" /></figure><p>Here he instantly sees the result of the cognitive service, the video (which can be watched as well of course) and the text-to-speech transcription of the recorded sentence. Here he can proceed to Deny, Place in Review (which allows him to send a request to the user, to re-record the movie, provide additional information, etc.) or Approve the PoL case. Pretty cool right?</p><p><strong>But wait, where’s the Blockchain?</strong></p><p>You want Blockchain? We give you Blockchain! But first I’ll explain why it’s the perfect usecase, and not something we incorporated just because it ‘sounds cool’.</p><p>As you may have figured out, this process (and thus the application) deals with highly sensitive personal data. Privacy and Security are major, if not the biggest, worries surrounding this discussion. All of the above depicted and described information can be asked for by an agency and may be used, but can only remain in its possession and be stored as long as it is absolutely necessary. That is why immediately after a ‘decision’ has been made on a case, all sensitive information (recording, photo’s, etc.) is deleted. Gone! How then, you ask me, can we make use and share the gathered information? Well, with -wait for it- Blockchain of course! In our private hyperledger blockchain, a new entry is made with a timestamp, identification number, and a Yes or No on whether this person is still alive. This way at any point this chain can be consulted using our secure API, and it will tell you the moment this person was last verified to be alive (or not). A de-personalized entry, only containing derived information.</p><p>And to finish with our so-called ‘deal-maker’: This API can be made accessible to all other (selected/approved) government agencies which in their processes need this information as well, and now do not need to start a separate similar (costly) process! Clients do not have to go through the same steps for every institution over and over again, resulting in a happy client and a happy government.</p><p>Ow, and a happy TimeSeries Hackathon team, as this proposed (and fully functional) solution gave us the (almost unanimous — 6/7) win. Cheers!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y9vndbXdsasvDPdC-x-aUQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a4205794138" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeseries/6am-saturday-morning-4a4205794138">SVB UWV Hackathon 2017: Blockchain + Facial Recognition + 24h? No problem!</a> was originally published in <a href="https://medium.com/timeseries">TimeSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I monitor my Smart Meter using Mendix and Domoticz]]></title>
            <link>https://medium.com/timeseries/how-i-monitor-my-smart-meter-using-mendix-and-domoticz-e2439237b2e2?source=rss----6d3bd69b4d63---4</link>
            <guid isPermaLink="false">https://medium.com/p/e2439237b2e2</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[domoticz]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[smart-home]]></category>
            <dc:creator><![CDATA[Paul Ketelaars]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 11:01:47 GMT</pubDate>
            <atom:updated>2017-10-13T11:01:07.309Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K4Ntejtc6BpLNKJu.png" /></figure><h3>A little history</h3><p>Even before I was a home owner I wanted to automate the house and monitor energy usage, to the extent that it drove my parents mad. So when I bought a house a couple of years ago, I called my Energy provider and practically begged them to give me priority placement for a SmartMeter. Fast forward two weeks later, and I was all set to start my automation / monitoring project. Being the geek that I am, combining all my electronic gadgets makes for a somewhat large energy footprint, so not only monitoring, but reducing energy usage was an interesting topic for me.</p><p>I already had a Raspberry Pi to tinker with, so I installed <a href="http://domoticz.com/">Domoticz </a>as an easy and well-supported Home Automation package. Using a P1 to USB cable it was easy to get my SmartMeter data in Domoticz.</p><p>I added some CoCo (or KaKu in Dutch; Click On, Click Off) switches as well, to be able to control some of my lighting. To support the 433 Mhz signals used by CoCo I needed some additional hardware, but other than that, it worked really well!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5TRsg-wuz8_AJ2BUIJG2Iw.jpeg" /></figure><p>Recently I thought: I’m a Mendix Consultant, working with IoT and BigData. Wouldn’t it be awesome to create my own custom dashboard, combining Mendix and Domoticz? And voilà! DoMenticz was born!</p><h3>Baby steps</h3><p>Since I mainly wanted to have insight in my energy consumption, my first step was getting my Smart Meter data in Mendix: mapping the data to create a graph and maybe show my current Gas and Energy usage for the day so far.</p><p>Using Mendix I was able to quickly consume an API created in Domoticz, which returns my current Energy or Gas usage. Without too much trouble (I only had to deal with some authentication issues to get my data) I retrieved my data, and was able to map it in Mendix to populate a graph. Next, it was easy enough to create some nice looking cards to create my desired overview</p><p>Within a day (or night, rather) I was able to read my Smart Meter data in Mendix and show it in a graph. Most of that time was figuring out how the Domoticz API worked. The data is even refreshed every minute, to make sure I see the latest data possible!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*VnnQbuHsedZSMMHCIiAw4A.png" /></figure><h3>Next up</h3><p>Now that I figured out how the Domoticz API works, I can add some new features to my Dashboard, create some fancy styling and make the app more interactive. Once I have added some additional devices (lights and heating for example) I’ll be sure to create a new blogpost to keep you updated! Ideally I want to put up a tablet on a wall in our living room with this app on it and manage my entire house from there! One (important!) thing to keep in mind when working on home automation is the WAF (Wife Acceptance Factor) which can bring your entire project to its knees if not managed correctly ;-).</p><p>Lastly, I cannot tell you all about my effort, and not show you a bit of the results, right? So here it is!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*He5KfsiTWdojwQI1fKMqdA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2439237b2e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeseries/how-i-monitor-my-smart-meter-using-mendix-and-domoticz-e2439237b2e2">How I monitor my Smart Meter using Mendix and Domoticz</a> was originally published in <a href="https://medium.com/timeseries">TimeSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[World Port Hackathon 2017: Mendix, RFID and Blockchain — No buzzwords but real apps!]]></title>
            <link>https://medium.com/timeseries/world-port-hackathon-2017-mendix-rfid-and-blockchain-no-buzzwords-but-real-apps-2e03f740db88?source=rss----6d3bd69b4d63---4</link>
            <guid isPermaLink="false">https://medium.com/p/2e03f740db88</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[rfid]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[mendix]]></category>
            <category><![CDATA[logistics]]></category>
            <dc:creator><![CDATA[Freek Brinkhuis]]></dc:creator>
            <pubDate>Fri, 13 Oct 2017 08:42:20 GMT</pubDate>
            <atom:updated>2017-10-13T08:42:19.541Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Four team members, 24 hours and the Van Nelle Factory in Rotterdam, a perfect recipe for a hackathon</em></strong>.</p><p>On the 1st and 2nd of September, the Van Nelle Factory was the battleground for the fifth World Port Hackathon, organised by among others The Port of Rotterdam and the Dutch Customs. Our TimeSeries team participated with the goal to combine Blockchain technology, RFID and the Mendix Platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*D8yXqTwrzJ6Awuhb.png" /></figure><p>We succeeded to combine real world examples of RFID scanning and Blockchain with the Rapid Application Development platform Mendix, turning mere buzzwords into real apps running in the Cloud.</p><p><strong>The challenge: what’s in the container?</strong></p><p>The challenge we chose to tackle was one from the Port Authorities of the Port of Rotterdam. It described a situation in which few details are known of a container arriving in the Port of Rotterdam. Usually, only a small description of goods is known by the Port Authorities whenever a container gets unloaded. This description doesn’t provide information about possible harmful contents of a container, like explosives, medicine, livestock or hazardous materials.</p><p>This makes it hard to make a risk assessment in order to either let a container pass customs when it’s safe, or crack it open to examine the goods if it’s deemed a risk. The latter scenario would result in delays in most of the cases, in which the receiver of the container would probably miss their on-time delivery.</p><p>Since international regulations don’t require anyone to hand over more information about a specific cargo shipment, the Port of Rotterdam asked us via this challenge to come up with a solution where we could improve this complex process. And so we did…</p><p>In less than 24 hours, the TimeSeries team developed a Mendix Application usable by both the Port of Rotterdam Authorities, and the receiver of the containers in Rotterdam.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wllj48dBdfk7bYt1.png" /><figcaption>The log-in screen displaying all technologies we’ve used for this hackathon</figcaption></figure><p><strong>Receiving party app: shipment overview</strong></p><p>After logging in, a receiving party sees an overview of their upcoming shipments, as well as some real-time information about their containers in transit, total amount of containers shipped and total amount of containers inspected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r6cEiPNYoPexNp4h.png" /><figcaption>Receiving Party (consignee) dashboard</figcaption></figure><p><strong>Registration containers and their details</strong></p><p>The receiving party is able to register their containers in the app by adding a container number and specifying some default parameters about what the cargo might hold. This is then stored in the blockchain, making the information immutable and available for everybody with the right permissions. Whenever the receiver has additional information, like a Bill of Lading or Packing Lists (documents that are necessary for shipping your cargo with a carrier), the receiver is able to upload these documents per container as well, which is then added to that container in the blockchain as a separate event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ooiSIhwADhd12fin.png" /><figcaption>Add a new shipment in seconds and attach all documents that you can supply</figcaption></figure><p><strong>Everyone loves a good score!</strong></p><p>The application calculates a score per container which indicates how efficient the customs handling in the Port of Rotterdam will be executed, based on the information that is added to the container’s in the blockchain. More information means better understanding and communication about the shipment, and quicker handling and processing of the container.</p><p>Next to that, an aggregate performance score for the current customer/receiving party is calculated, which gives insight in quality of information provided by this customer, to both the receiver of the shipment and the Port of Rotterdam Authorities.</p><p>The overall performance score is also indicated on the receiver’s shipment overview screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0u-W-Ik5CL-ZXfzT.png" /><figcaption>Follow the progress of your shipment through the Shipment Details page</figcaption></figure><p><strong>Customs app: incoming containers overview</strong></p><p>Next comes the second app, aimed at Dutch Customs in the harbor. In this simple dashboard, a customs handler has an overview of all the containers that will arrive within the next three days (a threshold that is now used to assess which containers might be prone to extra checks). By selecting a container, a customs handler can see the past events of that specific container, like the documents and information provided by the receiving party in advance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N3yNg_u2bF4mhu5T.png" /><figcaption>The go to page for the Port Authorities, displaying the incomming containers</figcaption></figure><p><strong>One more thing…</strong></p><p>We envisioned an approach where containers might soon all be fitted with an RFID antenna. This very inexpensive, printable and weatherproof chip can be used to digitally identify the container, but can also tell you where a specific container has been. By using a smart RFID scanner that can match the scan event with a GPS location, every port is able to exchange information about the location of the container and the state it currently resides in, for instance if it is cracked open or does it look like it contains different cargo than the manifest explains?</p><p>All this information can be of great value, so by using our experience with RFID technology, we were able to connect RFID scanning events to a container combined with a GPS location and added this to the containers blockchain.</p><p>In the finals of the World Port Hackathon, we scanned a fictive container, which was simulated by putting an RFID antenna in a box, with a handheld scanner. The application then showed this event in the Customs Dashboard as a new event to that container, pulling this information from a real life blockchain that we built and connected to our Mendix app.</p><p>So in less than 24 hours we created a working application with Mendix that utilised our Blockchain and RFID platform and fitted it in a real world challenge. We finished in the World Port Hackathon finals and had a great learning experience, meeting contenders from all across the globe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_6G4pObWlF9Pwfh0.jpg" /><figcaption>The Hackathon warriors of TimeSeries the Smart App company</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e03f740db88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeseries/world-port-hackathon-2017-mendix-rfid-and-blockchain-no-buzzwords-but-real-apps-2e03f740db88">World Port Hackathon 2017: Mendix, RFID and Blockchain — No buzzwords but real apps!</a> was originally published in <a href="https://medium.com/timeseries">TimeSeries</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>