◦ Node-RED for data processing and visualization
◦ Dronekit for drone control
◦ Sensortag for environmental data
Pilot E: Port Area Monitoring
Innovation
- Real-time monitoring of port areas using drones and sensors
- Early detection of incidents like fires or explosions
- Improved situational awareness for emergency responders
- Automated data collection from hard to reach areas
- Integration of multiple sensor types (thermal, gas, video etc)
- Processing of sensor data to detect anomalies
Benefits:
- Faster response times in emergencies
- Improved safety for emergency workers
- Detection of environmental hazards
- Continuous monitoring for security
Pilot
The document summarizes an AGILE M18 review meeting on security research. It discusses demos of role-based access control and identity management. It maps the security work package to the overall AGILE structure and architecture. The goals of the security work package are outlined. Research on security aspects is summarized, along with practical security aspects relevant to AGILE like identity management, data usage control, and secure data sharing. The security implementation status and integration with various components is reviewed. Future steps including ongoing work on usage control and secure data sharing are discussed.
AGILE software, devices and wider ecosystemAGILE IoT
This document summarizes an AGILE software, devices, and ecosystem review meeting that took place on October 20, 2017 in Brussels, Belgium. It provides an overview of the AGILE project goals, work package structure and architecture, software stack components, device and protocol support, user interface framework, and fleet management capabilities. The document outlines achievements in selecting and integrating software components, operating system support, protocol integration, and local and remote gateway management features. It also previews upcoming demonstrations of the development environment, recommender system, cloud integration, and pilot applications.
This document summarizes work on integrating IoT, storage, and platform as a service (PaaS) cloud services with AGILE workflows. It outlines objectives like sharing sensor data with cloud services and deploying AGILE workflows remotely. Several IoT, storage, and PaaS services are supported through Node-RED nodes developed, including Xively, FIWARE, Dropbox, and Heroku. Demos show uploading sensor data to OwnCloud and deploying workflows to cloud services. Next steps include a cloud storage backend, integrating the PaaS deployer, and supporting pilots' use of cloud services.
The document provides an agenda and summary of the AGILE M18 Review meeting in Brussels on October 20, 2017. It discusses the main achievements of the AGILE project including hardware and software innovations as well as community engagement. The agenda covers presentations on topics like IoT hardware, rapid prototyping tools, the AGILE development environment, research activities, IoT/cloud services, and pilots. It also maps the agenda and innovations to the overall AGILE work package structure and architecture. In closing, it assesses the current project status and needs for ongoing maintenance, integration, dissemination activities and addressing security issues following a lack of contribution from the expected Canonical partner.
The document provides an overview of IoT hardware innovation within the AGILE project. It discusses the development of modular gateway hardware based on a design for modularity (DFM) methodology. This includes the specification, design, and implementation of two gateway platforms - a "makers" version based on Raspberry Pi and an industrial version with a new design based on Intel architecture. The gateway uses a set of core and expansion modules compliant with COM Express and HAT standards. Hardware prototypes were developed for both gateways and expansion modules. The DFM methodology aims to design sustainable standard and customized products through high reuse of modules. This reduces costs and time to market compared to traditional approaches.
The document discusses the Agile IoT Project, which aims to create an open source Internet of Things (IoT) ecosystem. It includes:
- An Agile modular hardware and software gateway that supports protocol interoperability, device and data management, IoT application execution, and cloud communication.
- Open source IoT software components to enable easy IoT application prototyping and control of connected devices.
- Five pilot use cases that will test the Agile IoT components, including quantified self-tracking, open field monitoring with drones, air quality monitoring, enhanced retail services, and port area monitoring.
- Plans to solicit additional projects through an open call, providing up to €50
This document provides an agenda for an AGILE M18 Review meeting on October 20, 2017 in Brussels, Belgium. The agenda includes presentations on topics such as IoT hardware innovation, the AGILE development environment, research results, IoT and cloud interactions, AGILE pilots, innovations, impact, and administrative/financial items. There will also be discussions of dissemination, partnerships, and feedback from reviewers. The meeting aims to report on the project's progress and receive input after 18 months of work.
Building IoT Mashups for Industry 4.0 with Eclipse Kura and Kura WiresEclipse Kura
The presentation contains a real Industry 4.0 use cases that will take advantage of sensors connected through Modbus and mapped in Kura Wires with corresponding Assets. A complete dataflow model will also be presented
The document summarizes an AGILE M18 review meeting on security research. It discusses demos of role-based access control and identity management. It maps the security work package to the overall AGILE structure and architecture. The goals of the security work package are outlined. Research on security aspects is summarized, along with practical security aspects relevant to AGILE like identity management, data usage control, and secure data sharing. The security implementation status and integration with various components is reviewed. Future steps including ongoing work on usage control and secure data sharing are discussed.
AGILE software, devices and wider ecosystemAGILE IoT
This document summarizes an AGILE software, devices, and ecosystem review meeting that took place on October 20, 2017 in Brussels, Belgium. It provides an overview of the AGILE project goals, work package structure and architecture, software stack components, device and protocol support, user interface framework, and fleet management capabilities. The document outlines achievements in selecting and integrating software components, operating system support, protocol integration, and local and remote gateway management features. It also previews upcoming demonstrations of the development environment, recommender system, cloud integration, and pilot applications.
This document summarizes work on integrating IoT, storage, and platform as a service (PaaS) cloud services with AGILE workflows. It outlines objectives like sharing sensor data with cloud services and deploying AGILE workflows remotely. Several IoT, storage, and PaaS services are supported through Node-RED nodes developed, including Xively, FIWARE, Dropbox, and Heroku. Demos show uploading sensor data to OwnCloud and deploying workflows to cloud services. Next steps include a cloud storage backend, integrating the PaaS deployer, and supporting pilots' use of cloud services.
The document provides an agenda and summary of the AGILE M18 Review meeting in Brussels on October 20, 2017. It discusses the main achievements of the AGILE project including hardware and software innovations as well as community engagement. The agenda covers presentations on topics like IoT hardware, rapid prototyping tools, the AGILE development environment, research activities, IoT/cloud services, and pilots. It also maps the agenda and innovations to the overall AGILE work package structure and architecture. In closing, it assesses the current project status and needs for ongoing maintenance, integration, dissemination activities and addressing security issues following a lack of contribution from the expected Canonical partner.
The document provides an overview of IoT hardware innovation within the AGILE project. It discusses the development of modular gateway hardware based on a design for modularity (DFM) methodology. This includes the specification, design, and implementation of two gateway platforms - a "makers" version based on Raspberry Pi and an industrial version with a new design based on Intel architecture. The gateway uses a set of core and expansion modules compliant with COM Express and HAT standards. Hardware prototypes were developed for both gateways and expansion modules. The DFM methodology aims to design sustainable standard and customized products through high reuse of modules. This reduces costs and time to market compared to traditional approaches.
The document discusses the Agile IoT Project, which aims to create an open source Internet of Things (IoT) ecosystem. It includes:
- An Agile modular hardware and software gateway that supports protocol interoperability, device and data management, IoT application execution, and cloud communication.
- Open source IoT software components to enable easy IoT application prototyping and control of connected devices.
- Five pilot use cases that will test the Agile IoT components, including quantified self-tracking, open field monitoring with drones, air quality monitoring, enhanced retail services, and port area monitoring.
- Plans to solicit additional projects through an open call, providing up to €50
This document provides an agenda for an AGILE M18 Review meeting on October 20, 2017 in Brussels, Belgium. The agenda includes presentations on topics such as IoT hardware innovation, the AGILE development environment, research results, IoT and cloud interactions, AGILE pilots, innovations, impact, and administrative/financial items. There will also be discussions of dissemination, partnerships, and feedback from reviewers. The meeting aims to report on the project's progress and receive input after 18 months of work.
Building IoT Mashups for Industry 4.0 with Eclipse Kura and Kura WiresEclipse Kura
The presentation contains a real Industry 4.0 use cases that will take advantage of sensors connected through Modbus and mapped in Kura Wires with corresponding Assets. A complete dataflow model will also be presented
RA TechED 2019 - IN03 - Develop Analytics That Scale Using FactoryTalk Innova...Rockwell Automation
The document outlines an agenda for a discussion on FactoryTalk InnovationSuite. The agenda includes:
1. An overview of key discussions and labs about FactoryTalk InnovationSuite components.
2. An overview of the FactoryTalk InnovationSuite.
3. Discussions on extracting data and insights from industrial assets and how FactoryTalk InnovationSuite supports this process.
4. A review of FactoryTalk InnovationSuite components and architectures.
The document provides information to attendees about the content that will be covered in the discussion.
The document discusses the status and design of the modular gateways being developed as part of Work Package 1 (WP1) of the AGILE project. It provides an overview of the makers gateway, including the initial design which features a shield for the Raspberry Pi and connectivity options. Specifications for the makers gateway are also outlined. The status of the industrial gateway design is summarized, including the reference design, general purpose consolidated design, and preliminary design for a monitoring station. Key modules being developed for the industrial gateway are also described, such as the CPU and storage modules.
The document provides an overview of the u2 Toolbox, which is an integrated and open platform as a service for cities. It summarizes new components, enhanced components, and status of the toolbox. It then describes the key components of the toolbox including ucR-Light for platform federation, OPaaS.io personal data store, u2 Open Data Catalog, IoT Engine, and use cases involving Sapporo, Yokosuka, and Tokyo. It concludes with new use cases for fishery, forestry and emergency medical services.
This document discusses connecting IoT devices and systems to the FIWARE Lab ecosystem. It provides an overview of the FIWARE IoT proposal and community. It then describes the most common scenarios for connecting IoT providers and consumers to the FIWARE Context Broker using the IDAS/SBC Ultralight 2.0 protocol. Step-by-step instructions are provided for registering models and devices and sending measurements and commands. Additional options for connecting IoT systems like MQTT and LWM2M are also mentioned.
OSGi -Simplifying the IoT Gateway - Walt Bowersmfrancis
OSGi Community Event 2015
Why do IoT gateways have to be so difficult? Currently the fragmentation, complexity, and potential lock-in of the gateway make picking an IoT gateway solution appear difficult. Add to that developer integration challenges and the gateway picture seems overly complex. Enter OSGi to simplify the development and deployment of the IoT Gateway.</p>
Built on OSGi, Eclipse Kura provides an open platform for developing and deploying IoT gateways. Combining live demonstrations on the Raspberry Pi and Eurotech Reliagate with real world Eurotech use cases, this talk will provide an overview of Kura demonstrating how it leverages OSGi to simplify IoT gateway solutions.
- The document discusses the planned software architecture for the AGILE gateway, including functional architecture, micro modules, libraries and tools, and example workflows
- The functional architecture diagram shows the high-level components and APIs for the gateway software, including device and data management, apps, and cloud services integration
- The micro modules architecture defines autonomous pluggable components that interface via APIs and IPC to provide reusable functionality
- Example libraries and tools are identified that could be used to implement components like IoT device communication, data storage, and app development
- Example workflows are described for Bluetooth device discovery and connection of a thermostat app to retrieve and control device
Gateway Design with Eclipse Kura - Taking Kura to heightsRajesh Sola
The document discusses Eclipse Kura, an open source IoT gateway framework. It describes Kura's architecture, services, APIs and how it bridges devices, gateways and cloud platforms. It also covers how to develop custom bundles and services for Kura, build Kura from source, and deploy it on devices or in Docker containers.
Building an IoT Monitoring App with InfluxDB and LoRaInfluxData
This document outlines a workshop for building an IoT monitoring application with InfluxDB and LoRa. The workshop includes setting up an environment with VS Code, a LoRa device, and The Things Network. It then covers connecting the platforms by setting up InfluxDB and Telegraf, developing a custom application for querying and visualizing data, transforming data with downsampling, and creating alerts with thresholds and Slack notifications. The document provides steps and screenshots to guide participants through each portion of the workshop.
The document describes a tutorial for creating an arcade shooter game simulator called Shoot-A-Pi using the Eclipse Kura IoT application framework on a Raspberry Pi. The tutorial will cover setting up the hardware, creating OSGi bundles to interface with sensors and actuators, implementing the game logic, and deploying the bundles to the Raspberry Pi. Attendees will work through building the game over the course of the tutorial session.
This document is the final report for a senior design project involving the development of a smart board. A group of students were tasked with making an existing smart board prototype fully autonomous and controlled via a LabView interface and gesture control using a MYO armband and NI myRio microcontroller. The report describes the initial design specifications, components used, integration of the MYO and LabView, mechanical improvements made to the board, and testing done to achieve the goal of gesture controlled autonomous function without physical connections.
RA TechED 2019 - IN02 - Empower Your Connected Enterprise with FactoryTalk In...Rockwell Automation
FactoryTalk InnovationSuite is a suite of IIoT solutions including ThingWorx, an IIoT platform. ThingWorx includes capabilities like asset management, analytics, and mobile/AR applications. It allows users to connect devices and machines, create digital twins using a "ThingModel", develop applications using a visual mashup tool, and engage users through mobile and augmented reality. DataAnalytics solutions like DataView allow self-service data exploration and storyboarding to gain insights without extensive IT or data science expertise.
RA TechED 2019 - CL02 - Integrated Architecture System Software What's NewRockwell Automation
The document provides an overview of new and updated system software from Rockwell Automation, including Studio 5000 Logix Designer, View Designer, Application Code Manager, Logix Emulate, and connectivity to CAD software packages. Key updates include expanded controller support, enhanced Logix tag-based alarming, productivity improvements, and digital engineering tools to enable virtual commissioning and operator training.
Enabling IoT Devices’ Hardware and Software Interoperability, IPSO Alliance (...Open Mobile Alliance
Presentation delivered during the Internet of Things World, Santa Clara pre-event workshop by Christian Legare - IPSO Alliance Chairman, Chief of Software Engineering, Micrium (Part of Silicon Labs)
Internet Protocol for Smart Objects (IPSO) is an alliance that, among other things, defines a data model to represent sensor values and attributes. OMA uses IPSO Smart Objects v1.0 as its resource model to expose sensor information to a remote LwM2M Server. From the speaker from IPSO Alliance, you will learn:
● What is an IPSO Smart Object data model
● What do these Objects and Resources look like
● How to create and register your own resources
● What is next for IPSO Alliance
The document discusses WSO2's platform for IoT and connected devices. It describes the challenges of IoT platforms around device registration, integration, security, scalability and event management. It then outlines WSO2's reference architecture for IoT and its IoT Server product, which aims to address these challenges. Key capabilities of the WSO2 IoT Platform include device management, modeling devices as APIs, support for protocols like MQTT and HTTP, and integrating devices with analytics tools like WSO2 Data Analytics Server.
FIWARE is an open source platform that provides core digital infrastructure and a library of APIs to enable the development of Future Internet applications. The FIWARE platform includes Generic Enablers that provide common functions through APIs, allowing applications to be built in a modular way. Context information from IoT devices and other sources can be managed through the FIWARE NGSI API. This provides a standard way to retrieve and update attribute values that characterize real-world entities. FIWARE aims to foster an open ecosystem for entrepreneurs, technology providers, and data owners to build innovative applications.
This presentation was given at the Auckland API and Microservices MeetUp, 2016-MAR-03. The connected world is increasingly reaching from the virtual domain into the physical, through the rapid evolution of connected devices. What are the behavior and business patterns that are shaping this convergence? Where are the sources of innovation, what forces are shaping investments and value creation? What is the role of the enterprise? We explore the landscape with an eye for technology gaps and business opportunity.
RA TechED 2019 - IN03 - Develop Analytics That Scale Using FactoryTalk Innova...Rockwell Automation
The document outlines an agenda for a discussion on FactoryTalk InnovationSuite. The agenda includes:
1. An overview of key discussions and labs about FactoryTalk InnovationSuite components.
2. An overview of the FactoryTalk InnovationSuite.
3. Discussions on extracting data and insights from industrial assets and how FactoryTalk InnovationSuite supports this process.
4. A review of FactoryTalk InnovationSuite components and architectures.
The document provides information to attendees about the content that will be covered in the discussion.
The document discusses the status and design of the modular gateways being developed as part of Work Package 1 (WP1) of the AGILE project. It provides an overview of the makers gateway, including the initial design which features a shield for the Raspberry Pi and connectivity options. Specifications for the makers gateway are also outlined. The status of the industrial gateway design is summarized, including the reference design, general purpose consolidated design, and preliminary design for a monitoring station. Key modules being developed for the industrial gateway are also described, such as the CPU and storage modules.
The document provides an overview of the u2 Toolbox, which is an integrated and open platform as a service for cities. It summarizes new components, enhanced components, and status of the toolbox. It then describes the key components of the toolbox including ucR-Light for platform federation, OPaaS.io personal data store, u2 Open Data Catalog, IoT Engine, and use cases involving Sapporo, Yokosuka, and Tokyo. It concludes with new use cases for fishery, forestry and emergency medical services.
This document discusses connecting IoT devices and systems to the FIWARE Lab ecosystem. It provides an overview of the FIWARE IoT proposal and community. It then describes the most common scenarios for connecting IoT providers and consumers to the FIWARE Context Broker using the IDAS/SBC Ultralight 2.0 protocol. Step-by-step instructions are provided for registering models and devices and sending measurements and commands. Additional options for connecting IoT systems like MQTT and LWM2M are also mentioned.
OSGi -Simplifying the IoT Gateway - Walt Bowersmfrancis
OSGi Community Event 2015
Why do IoT gateways have to be so difficult? Currently the fragmentation, complexity, and potential lock-in of the gateway make picking an IoT gateway solution appear difficult. Add to that developer integration challenges and the gateway picture seems overly complex. Enter OSGi to simplify the development and deployment of the IoT Gateway.</p>
Built on OSGi, Eclipse Kura provides an open platform for developing and deploying IoT gateways. Combining live demonstrations on the Raspberry Pi and Eurotech Reliagate with real world Eurotech use cases, this talk will provide an overview of Kura demonstrating how it leverages OSGi to simplify IoT gateway solutions.
- The document discusses the planned software architecture for the AGILE gateway, including functional architecture, micro modules, libraries and tools, and example workflows
- The functional architecture diagram shows the high-level components and APIs for the gateway software, including device and data management, apps, and cloud services integration
- The micro modules architecture defines autonomous pluggable components that interface via APIs and IPC to provide reusable functionality
- Example libraries and tools are identified that could be used to implement components like IoT device communication, data storage, and app development
- Example workflows are described for Bluetooth device discovery and connection of a thermostat app to retrieve and control device
Gateway Design with Eclipse Kura - Taking Kura to heightsRajesh Sola
The document discusses Eclipse Kura, an open source IoT gateway framework. It describes Kura's architecture, services, APIs and how it bridges devices, gateways and cloud platforms. It also covers how to develop custom bundles and services for Kura, build Kura from source, and deploy it on devices or in Docker containers.
Building an IoT Monitoring App with InfluxDB and LoRaInfluxData
This document outlines a workshop for building an IoT monitoring application with InfluxDB and LoRa. The workshop includes setting up an environment with VS Code, a LoRa device, and The Things Network. It then covers connecting the platforms by setting up InfluxDB and Telegraf, developing a custom application for querying and visualizing data, transforming data with downsampling, and creating alerts with thresholds and Slack notifications. The document provides steps and screenshots to guide participants through each portion of the workshop.
The document describes a tutorial for creating an arcade shooter game simulator called Shoot-A-Pi using the Eclipse Kura IoT application framework on a Raspberry Pi. The tutorial will cover setting up the hardware, creating OSGi bundles to interface with sensors and actuators, implementing the game logic, and deploying the bundles to the Raspberry Pi. Attendees will work through building the game over the course of the tutorial session.
This document is the final report for a senior design project involving the development of a smart board. A group of students were tasked with making an existing smart board prototype fully autonomous and controlled via a LabView interface and gesture control using a MYO armband and NI myRio microcontroller. The report describes the initial design specifications, components used, integration of the MYO and LabView, mechanical improvements made to the board, and testing done to achieve the goal of gesture controlled autonomous function without physical connections.
RA TechED 2019 - IN02 - Empower Your Connected Enterprise with FactoryTalk In...Rockwell Automation
FactoryTalk InnovationSuite is a suite of IIoT solutions including ThingWorx, an IIoT platform. ThingWorx includes capabilities like asset management, analytics, and mobile/AR applications. It allows users to connect devices and machines, create digital twins using a "ThingModel", develop applications using a visual mashup tool, and engage users through mobile and augmented reality. DataAnalytics solutions like DataView allow self-service data exploration and storyboarding to gain insights without extensive IT or data science expertise.
RA TechED 2019 - CL02 - Integrated Architecture System Software What's NewRockwell Automation
The document provides an overview of new and updated system software from Rockwell Automation, including Studio 5000 Logix Designer, View Designer, Application Code Manager, Logix Emulate, and connectivity to CAD software packages. Key updates include expanded controller support, enhanced Logix tag-based alarming, productivity improvements, and digital engineering tools to enable virtual commissioning and operator training.
Enabling IoT Devices’ Hardware and Software Interoperability, IPSO Alliance (...Open Mobile Alliance
Presentation delivered during the Internet of Things World, Santa Clara pre-event workshop by Christian Legare - IPSO Alliance Chairman, Chief of Software Engineering, Micrium (Part of Silicon Labs)
Internet Protocol for Smart Objects (IPSO) is an alliance that, among other things, defines a data model to represent sensor values and attributes. OMA uses IPSO Smart Objects v1.0 as its resource model to expose sensor information to a remote LwM2M Server. From the speaker from IPSO Alliance, you will learn:
● What is an IPSO Smart Object data model
● What do these Objects and Resources look like
● How to create and register your own resources
● What is next for IPSO Alliance
The document discusses WSO2's platform for IoT and connected devices. It describes the challenges of IoT platforms around device registration, integration, security, scalability and event management. It then outlines WSO2's reference architecture for IoT and its IoT Server product, which aims to address these challenges. Key capabilities of the WSO2 IoT Platform include device management, modeling devices as APIs, support for protocols like MQTT and HTTP, and integrating devices with analytics tools like WSO2 Data Analytics Server.
FIWARE is an open source platform that provides core digital infrastructure and a library of APIs to enable the development of Future Internet applications. The FIWARE platform includes Generic Enablers that provide common functions through APIs, allowing applications to be built in a modular way. Context information from IoT devices and other sources can be managed through the FIWARE NGSI API. This provides a standard way to retrieve and update attribute values that characterize real-world entities. FIWARE aims to foster an open ecosystem for entrepreneurs, technology providers, and data owners to build innovative applications.
This presentation was given at the Auckland API and Microservices MeetUp, 2016-MAR-03. The connected world is increasingly reaching from the virtual domain into the physical, through the rapid evolution of connected devices. What are the behavior and business patterns that are shaping this convergence? Where are the sources of innovation, what forces are shaping investments and value creation? What is the role of the enterprise? We explore the landscape with an eye for technology gaps and business opportunity.
by Mr. Ananth Subba, Co-founder & CTO, SpaceAge Labs, at NUS-ISS SkillsFuture Series Seminar: Secured IoTs and Secured Cloud – Partners in ensuring a Secured Smart Nation (3 Oct)
The document summarizes discussions from an AGILE project meeting regarding pilot design, execution, and evaluation (WP8). Five pilots were proposed: 1) Quantified Self, 2) Open Field & Cattle Monitoring using UAVs, 3) Air Quality Monitoring, 4) Enhanced Retail Services, and 5) Port Area Monitoring for Public Safety using UAVs. Requirements, use cases, and architectures were discussed for each pilot. Next steps include finalizing requirements analysis, pilot descriptions, and evaluation methodologies ahead of pilot component development and deployment.
The Best of Both Worlds: Introducing WSO2 API Manager 4.0.0WSO2
APIs now serve as the primary building blocks for assembling data, events, and services from within the organization, throughout ecosystems, and across devices. Integrated legacy systems and support for modern event-driven architectures, on the other hand, are critical in allowing timely, relevant digital experiences in response to customer behavior. To support these demands, WSO2 has added significant new capabilities to WSO2 API Manager 4.0.0.
Complete support for streaming APIs and event-driven architecture (EDA)
The first solution to support full implementation of the AsyncAPI specification
A Service Catalog to enable developers to discover a given service seamlessly
API / API product revisioning to keep track of the changes
Feature-rich, cloud-based analytics for easy integration
You will gain a full understanding of WSO2 API Manager 4.0.0 features and how they cater to current API Management demands by attending this webinar.
DURING THE WEBINAR, WE WILL COVER:
Experience the power and synergy of Service Integration and API Management in a fully functional API ecosystem
Understand the motivation behind WSO2 API Manager 4.0.0 release
New streaming and event-driven architecture support available in API Manager 4.0.0
Learn the importance of catering all API Management and integration demands with one connected platform
Explore other new features and enhancements to the product
Extensible, server-side, open IoT architecture for device management, complete with integration capabilities, IoT analytics, and security for devices and data.
The document discusses cloud APIs within NextGEOSS. It includes:
1. An introduction on using cloud APIs in NextGEOSS by Hervé Caumont of Terradue.
2. A discussion of the EGI Federated Cloud APIs and unified user experience across distributed clouds by Bjorn Backeberg of EGI.eu.
3. An overview of the NextGEOSS Cloud Bursting Service and Terradue's support for multi-cloud deployment of pilot applications by Hervé Caumont.
New ThousandEyes Product Features and Release Highlights: March 2024ThousandEyes
ThousandEyes has released several new features and enhancements in February 2024, including a new API monitoring test type, platform innovations like dashboard filters, and improvements to endpoint monitoring. The presentation provides demonstrations of the new API test type, AWS API Gateway recommendations, Cisco Secure Access experience insights integration, enhanced endpoint test creation workflow, and event detection capabilities.
Self condition monitoring mobile machinery 1st generation demonstrationArrowheadProject
This document discusses a project to demonstrate self-monitoring of mobile machinery. The objectives are to demonstrate key self-monitoring technologies at the machine level, including self-condition monitoring using a wireless monitoring node connected to the cloud. This will be implemented in three generations: the first will integrate a smart bearing in a wheel loader in a lab environment; the second will integrate the smart bearing into the wheel loader with services connecting it to the loader controller; and the third will integrate the wheel loader system into a site maintenance system.
This document summarizes a webinar presentation about managing resources and services in a cloud federation using FIWARE Lab solutions. The presentation discusses:
- The FIWARE Lab open innovation platform and its distributed cloud infrastructure across Europe.
- Key components that enable deployment of applications across the federation, including the Pegasus platform-as-a-service and Deployment and Configuration Adapter.
- A federation monitoring system that collects data from the distributed infrastructure and provides aggregated metrics through a standardized API.
- A case study example of deploying a multi-tier weather application across two cloud infrastructures using these solutions.
Complete Visibility into Docker Containers with AppDynamicsAppDynamics
This document discusses AppDynamics' capabilities for monitoring Docker containers:
- AppDynamics provides unified monitoring of applications running in Docker containers, allowing visibility into both application and Docker metrics from a single interface.
- An extension is available that collects Docker metrics using the Docker Remote API and displays them alongside application data in AppDynamics' dashboards.
- A demo environment on GitHub contains an example of an application deployed in Docker containers that can be monitored end-to-end using AppDynamics.
Cymbal Direct is an online retailer that wants to modernize its technical infrastructure to improve customer experience, leverage analytics, and improve marketing. This includes scaling services to handle demand surges, facilitating large B2B orders, processing drone telemetry data, and integrating social media applications while avoiding inappropriate content. The solution proposes moving to managed Kubernetes on Google Cloud, standardizing on containers, enabling secure partner integration through APIs, and processing IoT data streams from drones.
Oliot daeyoungkim-kaist-2015 - final - shortDaeyoung Kim
This document provides an overview of the Oliot (Open Language for Internet of Things) IoT platform and its applications. It discusses the Internet of Things ecosystem and requirements. It then describes the Oliot platform, which is based on GS1 standards for identifying smart objects. The platform includes EPC Information Services to store and share visibility data. It also extends services like Object Naming Service for IoT discovery. Several ongoing Oliot applications are highlighted, including healthcare monitoring, smart agriculture/food safety, and bridge management.
Dive into a reference architecture that demonstrates the patterns and practices for securely connecting microservices together using Apigee Edge integration for Pivotal Cloud Foundry.
We will discuss:
- basics for building cloud-native applications as microservices on - Pivotal Cloud Foundry using Spring Boot and Spring Cloud Services
- patterns and practices that are enabling small autonomous microservice teams to provision backing services for their applications
- how to securely expose microservices over HTTP using Apigee Edge for PCF
Watch the webcast here: https://youtu.be/ETT6WP-3me0
The 2021 Interactive Cargo Webinar presents the progress of the IATA Interactive Cargo project. More details at www.iata.org/interactive-cargo.
14:00-14:30 The IATA Interactive Cargo project achievements and next steps
This presentation will give an overview of the Interactive Cargo project’s achievements: (1) The recommended practice on IoT device data sharing in air cargo, (2) The recommended practice on the approval of the use of portable electronic devices onboard aircraft for air cargo, and (3) the amendment to the conditions of carriage for cargo.
Sonia Ben Hamida, Project Manager Interactive Cargo, IATA
Carlos Tornero, Deputy General Counsel, IATA
14:30-14:45 Safely and efficiently approving the use of cargo tracking devices
The presentation will share the progress of the pilot project “Approval of the use of Portable Electronic Devices (PEDs) approval for air cargo”. The goals of this pilot are to adopt the IATA recommended practice and checklists for the approval of Portable Electronic Devices (PEDs) onboard aircraft for air cargo in order to standardize information required for approval and decrease the total duration required for carriers to complete an approval request.
Jeff Clark, Founder & CEO, 7PSolutions, LLC
14:45-15:00 Sharing IoT device data in air cargo with ONE Record: Outcomes and lessons learnt
The presentation will share the progress of the pilot project “Visibility, Tracking and Alerts at the Piece Level”. The goals of this pilot are to demonstrate autonomous delivery of in-shipment status messaging and sensor-based alerts, mirror Cargo iQ milestones in cargo facilities, and track ULDs integrated with tracking devices.
Tomal Sohoral, Manager, Cargo Solutions Strategy and Business Development, Air Canada Cargo
15:00-15:15 The handling of interactive cargo: Main challenges and potential solutions
The use of smart tracking devices presents shippers and cargo owners with the ability to monitor not just the whereabouts of air cargo shipments but also their physical condition and their immediate environment. But these are sophisticated devices, often powered by lithium batteries with some models capable of interacting with local devices and transmitting data in-flight. Shippers respect and appreciate the need for clear rules for the use of these devices yet they sit in a hybrid regulatory environment - part-dangerous goods, part-perishable load, part-radio communications device and part-data logger able to interact with third party systems. So, there is a data privacy and protection issue too.
GSF has been supporting and encouraging the air cargo community in its development of processes and procedures for the handling and acceptance of these devices and this presentation will set out the shippers’ perspectives and expectations of procedures that will make the use of these devices as seamless and trouble-free as possible.
James Hookham, Secretary General, Global Shippers Forum
#SAFIRE-Project is presented at #ConnectedFactories Event in the „Horizontal (automation) and vertical (Cloud) Cyber-security in I4.0” Session #FOF_EU #DigitiseEU
Cymbal Direct is migrating some legacy applications from virtual machines to containers to take advantage of the scalability and portability benefits of containers. The client has an application that stores significant data on the file system of its virtual machines. The assistant recommends using Migrate for Anthos to automate the creation of a GKE cluster and import of the virtual machines, then convert them to containers with persistent storage, in order to migrate this application with minimal rewriting.
IMGS 2015 - Transport for London - Alun PearseyIMGS
An overview of the first geospatial project for Intergraph UK that deployed a hosted service on the Amazon Cloud. The presentation will cover the business and IT considerations that underpinned the clients (Transport for London) decision to move from an internal IT provided system to SaaS hosted solution. It will share some of the lessons learnt from the project and an update on benefits realised by the client.
Similar to Pilot Design, Execution & Evaluation (20)
The document summarizes an Eclipse Meet & Greet session on the Eclipse AGAIL project. It introduces the project leads Philippe Krief and Csaba Kiraly. Eclipse AGAIL is developing an open source, modular IoT gateway stack to empower decentralized IoT with features like local device control and data storage, application creation and extensibility, interoperability across protocols and platforms, and ease of use through cloud-like DevOps tools. The stack uses Docker containers, a Yocto-based OS, and is designed through several pilot projects and an open call for developers.
AGILE is an open gateway for IoT that aims to build a modular and extensible ecosystem for IoT applications and data management. It focuses on community engagement and exploitation through diverse pilots that address privacy, provenance of data, and integration with external clouds. AGILE provides a gateway operating system, IoT framework, and API to facilitate graphical app development and recommendation of workflows.
The AgriAware solution aims to help farmers produce high quality food sustainably through an app and platform. The Farmer Assistant app will suggest treatments, operations, and optimal picking times based on climate data from field sensors. This will help farmers produce more with fewer resources. The AgriAware backend will integrate different sensor data to provide customized treatment suggestions influenced by environmental factors. The initial focus will be on olive growers, collecting requirements around daily plant treatments, pest traps, fungal therapies, pruning, and harvesting phases. The AgriAware architecture will connect sensors, data, apps, and platforms to offer an effective traceability and decision support tool for conscious food production and marketing.
The document summarizes a presentation on configuration and recommendation technologies from AGILE. It discusses:
1. The goals of developing configuration technologies to enable flexible knowledge representation and efficient reasoning for solving configuration problems, and recommendation technologies to recommend IoT workflows, cloud services, and apps.
2. Key achievements including developing answer set programming approaches for configuration knowledge bases and prototypes for air pollution monitoring and smart homes, as well as hybrid recommendation systems and learning cluster-based search heuristics.
3. Ongoing work including increasing efficiency of answer set programming, extending knowledge bases, improving recommender prediction, and knowledge compilation for gateways.
Recommendation Technologies for IoT Edge DevicesAGILE IoT
Seda Polat Erdeniz presents an overview of recommendation approaches and how they could be applied in the AGILE Project. The document discusses content-based, collaborative filtering, and knowledge-based recommendation technologies. It also outlines four recommendation scenarios for the AGILE Project involving recommending apps, workflows/nodes, devices, and cloud services based on a user's gateway profile and similar other gateway profiles. The goal is to increase flexibility for IoT infrastructures and application development using recommendation technologies. Future work includes optimizing the recommender engine to operate locally on gateways and offline.
AGILE is an open gateway for IoT that aims to build a modular and extensible ecosystem for IoT applications and data management. It focuses on community engagement and exploitation through diverse pilots that address privacy, provenance of data, and integration with external clouds. AGILE provides a gateway operating system, IoT framework, and API to facilitate graphical app development and recommendation of workflows.
The document summarizes progress on Work Package 7 (WP7) of the AGILE project, which focuses on community management and dissemination. It provides an overview of WP7 objectives, tasks, events conducted in Q2 2016 to promote AGILE, growth of the AGILE community website and social media presence, and partner commitments to WP7 tasks. It outlines plans for upcoming events and deliverables, including the launch of an Eclipse IoT project proposal, workshops at EclipseCon Europe, and increasing blog content to communicate AGILE's goals.
This document outlines a proposal for an Eclipse project called AGILE. The proposal discusses establishing an open source IoT platform hosted by the Eclipse Foundation. The first year would involve formalizing the platform's scope and connections to other projects, and creating the initial AGILE open source project. Subsequent time would be spent publishing new components, improving existing ones, and growing the community. The document reviews Eclipse's development process phases and provides a template for project proposals, highlighting what should be included such as background, scope, description, licensing, and key people involved.
Juan David Parra presented an identity management prototype at the AGILE kick-off meeting from 12-14 January 2016 in Trento, Italy. The prototype allows AGILE users to log in using existing authentication mechanisms like Pam-Auth, GitHub, and Web-ID. It also manages user and device keys and supports authentication of devices and users. Parra demonstrated the prototype and discussed next steps of integrating it with AGILE components like device management, the user interface, and data management.
This document summarizes work being done on Work Package 4 (WP4) of the AGILE project. WP4 aims to provide connectors for extending the capabilities of an IoT gateway by managing data and deploying apps in various cloud systems. It will integrate both public clouds like Google Drive and private clouds like those used in the AGILE pilots. The work involves identifying relevant cloud APIs, integrating selected cloud infrastructures between months 13-20, and integrating with the pilot projects between months 19-36. Key tasks include classifying cloud providers, assigning partners responsibilities, and addressing terminology and modularity issues to define how different cloud systems will interface with the gateway.
The document discusses an AGILE meeting and demo sessions held in Berlin on July 20-21, 2016 between Resin.io and CREATE-NET. It provides an overview of Resin's objectives for the meeting including cross-partner integration, assisting with software and language selection for demos, and developing a device management UI. It also notes challenges faced including finalizing the underlying technologies and completing the API in time for the demos. A proposed solution is to use a VirtualBox virtual machine to enable faster iteration for the AGILE community.
The document discusses issues of data ownership and trust in the Internet of Things. It notes that while IoT devices can provide benefits like maintenance, distribution and cost reduction, users may not truly have control over their data which is often sent to clouds without a trusted point of collection or way to share data. There is also a lack of proper legislation regarding IoT data ownership. It promotes a project called AGILE IoT that has created a testbed of over 2,500 sensor nodes to help address these issues of data ownership and trust in IoT systems.
The document summarizes an artistic event being organized by AGILE in Berlin in Summer 2017 to involve the public with IoT technologies. Artists will be invited to submit proposals for interactive art installations involving quantified self, smart cities, interactive spaces, and representing externalities. Four winners will be selected in different categories to create installations using sensors and data from areas like bio-monitoring, environmental monitoring, mobile technologies and the port of Antwerp. The goal is to bring the public and artists closer to IoT and encourage dialogue through immersive experiences.
The cellular network: a vital link in the world of dronesAGILE IoT
Tom Sorgeloos of Orange Group presented on the role of cellular networks in enabling drones. Orange Group has 6.2 million IoT SIM cards across 220 countries and provides mobile coverage to 99% of Belgium territory with average download speeds of 16 Mbps. Sorgeloos discussed Orange's network capabilities and increasing interest from industries in using drones for surveillance. He outlined various test cases needed to further develop 4G and 5G networks for reliable, low-latency drone control and connectivity.
This document describes plans to integrate an AGILE IoT gateway into the IoT-LAB testbed. The IoT-LAB testbed currently provides remote access to over 2700 IoT devices for experimentation. The plans aim to connect AGILE gateways indirectly to these devices through the Open A8 nodes in the testbed. This would allow users to access AGILE interfaces and interfaces connected to the IoT devices through an SSH tunnel. Several approaches are discussed for integrating the AGILE gateway including adding new devices or modifying existing nodes to function as gateways. Key requirements, open issues, and next steps are also outlined.
This document summarizes discussions from an AGILE meeting regarding several IoT pilots being developed as part of the AGILE project. It describes 5 pilots focused on various application domains including quantified self, environmental monitoring, and retail. For each pilot, it outlines the requirements, use cases, open issues, and next steps. The goals are to finalize pilot designs and develop a framework to enable integration and evaluation of the different pilots across the project.
The Rising Future of CPaaS in the Middle East 2024Yara Milbes
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
UI5con 2024 - Bring Your Own Design SystemPeter Muessig
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...The Third Creative Media
"Navigating Invideo: A Comprehensive Guide" is an essential resource for anyone looking to master Invideo, an AI-powered video creation tool. This guide provides step-by-step instructions, helpful tips, and comparisons with other AI video creators. Whether you're a beginner or an experienced video editor, you'll find valuable insights to enhance your video projects and bring your creative ideas to life.
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
How Can Hiring A Mobile App Development Company Help Your Business Grow?ToXSL Technologies
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Odoo releases a new update every year. The latest version, Odoo 17, came out in October 2023. It brought many improvements to the user interface and user experience, along with new features in modules like accounting, marketing, manufacturing, websites, and more.
The Odoo 17 update has been a hot topic among startups, mid-sized businesses, large enterprises, and Odoo developers aiming to grow their businesses. Since it is now already the first quarter of 2024, you must have a clear idea of what Odoo 17 entails and what it can offer your business if you are still not aware of it.
This blog covers the features and functionalities. Explore the entire blog and get in touch with expert Odoo ERP consultants to leverage Odoo 17 and its features for your business too.
An Overview of Odoo ERP
Odoo ERP was first released as OpenERP software in February 2005. It is a suite of business applications used for ERP, CRM, eCommerce, websites, and project management. Ten years ago, the Odoo Enterprise edition was launched to help fund the Odoo Community version.
When you compare Odoo Community and Enterprise, the Enterprise edition offers exclusive features like mobile app access, Odoo Studio customisation, Odoo hosting, and unlimited functional support.
Today, Odoo is a well-known name used by companies of all sizes across various industries, including manufacturing, retail, accounting, marketing, healthcare, IT consulting, and R&D.
The latest version, Odoo 17, has been available since October 2023. Key highlights of this update include:
Enhanced user experience with improvements to the command bar, faster backend page loading, and multiple dashboard views.
Instant report generation, credit limit alerts for sales and invoices, separate OCR settings for invoice creation, and an auto-complete feature for forms in the accounting module.
Improved image handling and global attribute changes for mailing lists in email marketing.
A default auto-signature option and a refuse-to-sign option in HR modules.
Options to divide and merge manufacturing orders, track the status of manufacturing orders, and more in the MRP module.
Dark mode in Odoo 17.
Now that the Odoo 17 announcement is official, let’s look at what’s new in Odoo 17!
What is Odoo ERP 17?
Odoo 17 is the latest version of one of the world’s leading open-source enterprise ERPs. This version has come up with significant improvements explained here in this blog. Also, this new version aims to introduce features that enhance time-saving, efficiency, and productivity for users across various organisations.
Odoo 17, released at the Odoo Experience 2023, brought notable improvements to the user interface and added new functionalities with enhancements in performance, accessibility, data analysis, and management, further expanding its reach in the market.
Enhanced Screen Flows UI/UX using SLDS with Tom KittPeter Caitens
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
Oracle Database 19c New Features for DBAs and Developers.pptx
Pilot Design, Execution & Evaluation
1. AGILE M18 Review, 20 October 2017, Brussels (Belgium)
WP8 - Pilot Design, Execution &
Evaluation
ANDREAS MENYCHTAS - BIOASSIST - WP8 LEADER
2. Overview
AGILE PilotsReal-time, drone based, multi-
sensor emergency and
maintenance support in port
environments.
Improved shopping experience
for consumers and sustainable,
attractive and differentiating
solution for traders.
UAV and ground based
wildlife real-time monitoring
and data collection in wide,
inaccessible and wild areas.
Quantified-self application for
monitoring and analyzing
biosignals and activity data
IoT Testbed for
experimenting with
AGILE Components
Low cost, high precision, multi-
sensor, highly pervasive,
sustainable air quality &
pollution monitoring.
3. Methodology
Pilots Implementation Pilots Evaluation
Delivery of
HW & SW
components
Integration
Storylines
Use Case
Scenarios
Project-level
requirements
Pilot-specific
requirements
Deployment
of AGILE and
collection of
feedback
Pilots Definition and
Requirements Analysis
Now
4. M18 Status / Work Done
Design and Implementation of Pilots
◦ Definition of the architecture of each pilot
◦ Development of plan for integration with the AGILE components
◦ Continuous feedback to AGILE technical WPs (using the project tools:
github, slack, teleconferences etc.) and interactive development of AGILE
components
◦ Assessment of requirements fulfillment
◦ Implementation of Pilot Application Prototypes using AGILE
Pilots Operation
◦ Definition of the operational plan of each pilot
◦ Procurement of equipment and sensors
◦ User recruitment
◦ Evaluation guidelines
5. AGILE Components and Pilots
AGILE Components
Pilot A Pilot B Pilot C Pilot D Pilot E
Makers GW
Industrial GW
GW Management
Device and Protocol Management
Developers UI
Data/Storage API
Security API
Cloud Integration
Recommender/Configurator
Integrated In progress
HW
SW
7. Overview
Home / Daily use by non-experts
Simplified Integration of
◦ Biosignal Sensors and Wearables
◦ Communication Protocols (BLE)
Effective Data Exchange and
Management
Data Security and Privacy by Design
Support of Cloud APIs for Activity and
eHealth Data Synchronization
Data Analysis in the Gateway
Customization and Extensibility with
Data- and Event-driven Workflows
Pilot A: Quantified-Self
8. Implementation
Agile Core Device Hooks
AgileBLEnetworkcontainer
Device Register
Device
Publish/Subscribe
Device Stream Data
Device Poll Data
Device Driver
Configure BLE GATT
characteristics
Connect and
Run device init
Map Device
BLE
notifications
to
Agile data
endpoints
Stream data
Filter
data
ReadData
AGILE Drivers for Activity Trackers and Biosignal Sensors Quantified-self Application UI
Pilot A: Quantified-Self
10. AGILE Components Used
• Restful API is used for the accessing AGILE Services/Components
• UI:
• Device Management UI is used for the device discovery and setup. In future, the
functionality of this UI will be embedded in the Quantified-self application and will
be realized by communicating directly with the Device API.
• IoT App Developers UI is used for implementing experimental data processing
workflows for real-time and historical data.
• IoT Gateway Management UI (OS.js) is used for integrating the web UI of the
Quantified-self application.
• Device API and Protocol API are used for the BLE communication with the activity
trackers and biosignal measurement devices.
• Data Management Cloud plugins are used for accessing users’ activity data from the
cloud based APIs of app providers and devices manufactures such as Google Fit, Fitbit
etc.
• Security API is used for authentication to the Quantified-self application
Pilot A: Quantified-Self
11. Innovation - KPIs
• Holistic Approach
• Beyond the limitations of a self-managed mobile
application
• Fully Automated
• Suitable for people unfamiliar with technology such as
seniors
• Advanced Data Management
• Support different approaches for data acquisition
• Use of standards in the overall data lifecycle facilitating
data import/export
• Enhanced Security and Privacy
• Local storage of data and sharing through policies
• Extensibility and High Customization
• Modular Hardware and Container-based Software Stack
• Reduced Cost
Added Value
Minimum support of Devices
• Four different types of
devices (activity tracker,
blood pressure monitor,
pulse oximeter, weighing
scale) are locally
integrated
Minimum support of Clouds
• Two smartphone
applications (Google Fit
and FitBit) are supported
via their Cloud Platforms
KPIs
Pilot A: Quantified-Self
12. Deployment and Operation Plan
Location and user recruitment
◦ Recruitment from BioAssist’s user base (Athens)
◦ IMEC is also actively involved and users from the Living Labs will participate (Belgium).
◦ Crowdfunding Campaign
Preparation of documents such as user consent, questionnaires, training
material, etc.
Equipment procurement is progressing
Evaluation Cycles
◦ Involve only friendly users until the first stable release
◦ 1st Cycle: M23 – M27
◦ 2nd Cycle: M27 – M36
Pilot A: Quantified-Self
14. Overview
Pilot B: Open Field and Cattle Monitoring
• Monitoring of sensor stations in areas
beyond the established communication
infrastructure in real time
• No need for fixed gateway deployment and
wireless network coverage
• AGILE gateway will be deployed in UAVs
manufactured by Sky-Watch and used for
monitoring water quality through remote
sensor stations
15. Implementation
Pilot B: Open Field and Cattle Monitoring
Ground Control Station (GCS) and UAV
• Custom Flight Plans
• Monitoring and supervision of the
UAV during flight
• IP based protocol between UAV and
GCS to support AGILE
16. Implementation
Pilot B: Open Field and Cattle Monitoring
Sky-Watch AGILE Application
• Node.js application deployed in docker
container
• Interfacing with AGILE API using agile-sdk
• Interfacing with AGILE Node-RED using
MQTT
• Includes webserver for hosting
frontend/UI
• Currently communicating directly with
LoRaWAN module for sensor input
17. Implementation
Pilot B: Open Field and Cattle Monitoring
Developers UI – AGILE Node-RED flow
• Interfaces with Node.js Application
using MQTT
• Using AGILE Cloud components –
currently ownCloud
18. Mapping to AGILE Architecture
Pilot B: Open Field and Cattle Monitoring
19. AGILE Components Used
Current Status
◦ AGILE REST API via agile-sdk for implementing the interface with AGILE
microservices
◦ AGILE Node-RED Cloud Node for data upload to ownCloud
◦ Docker-based deployment infrastructure of AGILE
Pilot B: Open Field and Cattle Monitoring
Next Steps
◦ Device/Protocol API for communication with ground based sensors
◦ AGILE Data for retrieving stored sensor data
◦ AGILE Security for keeping collected data private
◦ AGILE UI components for configuration of users, devices, etc.
20. Innovation
AGILE is intended to offer quick development and time-to-market for
applications where secure data collection and cloud connectivity is of
prime concern.
Sky-Watch already specializes in data collection by UAV, and foresee
increasing demand for cloud connectivity and data offloading in our
UAV solutions. In this context, AGILE is considered as an important
technology enabler for our future product range.
Pilot B: Open Field and Cattle Monitoring
21. KPIs
A1: Designated users will be allowed to log into a cloud storage and retrieve data
◦ An ownCloud server has been setup
◦ Users permissions will be granted during the Pilot deployment phase
A2: Sensor data will be collected in flight by the AGILE Gateway
◦ Collection of sensor data from LoRaWAN ground stations is working
◦ The Sky-Watch application interfaces directly with a LoRaWAN module
◦ When LoRa/LoRaWAN support is added to the AGILE stack, Sky-Watch will switch to use the AGILE REST
API/agile-sdk
A3: Data from AGILE gateway is uploaded automatically to cloud storage upon connection to internet
◦ Data is already uploaded to ownCloud using the Agile Node-RED Cloud Node
A4: UI must be viewable on the gateway’s Ethernet interface
◦ The UI is currently displaying live/historical data. Remaining functionality will be added during the next
phases
A5: Data from more than one sensor shall be present
◦ Currently the setup includes a single station with multiple sensors attached. This will be extended to
include more stations/sensors early in the deployment phase
Pilot B: Open Field and Cattle Monitoring
22. Deployment and Operation Plan
Pilot B: Open Field and Cattle Monitoring
Demonstrator A: Local Air Field Test 1 (Nov 2017 – Feb 2018)
◦ In-flight sensor data collection via data link from UAV to multiple ground stations
◦ Data offloading to cloud using AGILE APIs
◦ Data visible on application UI
Demonstrator B: Local Air Field Test 2 (Feb – Jul 2018)
◦ Includes Demonstrator A items
◦ Integration with remaining AGILE core components - Data/Device/Security APIs
Demonstrator C: Long Range Field Test (Jul – Dec 2018)
◦ Includes Demonstrator A and B items
◦ UAV needs to travel to move into sensor-range
◦ Final Test & Evaluation
23. Demo Components
Pilot B: Open Field and Cattle Monitoring
UAV containing AGILE Gateway, flight controller, and LoRa receiver
Sensor element with LoRa transmitter
Ground Station consisting of a Linksys Router (for demo)
PC for displaying the UI
26. Overview
• Provide a low cost/high quality solution for
pollution monitoring based on:
• pervasive/IoT philosophy;
• Agile platform (both HW & SW);
• small, low cost and high precision
monitoring stations.
• Demonstrate the reduction of the time to
market for the development of a vertical
solution based on Agile-IoT approach.
• Adopt Design for Modularity approach for the
design of the hardware platform.
• Design and develop a set of prototypes of:
• the monitoring station;
• the device-to-cloud infrastructure;
• a mobile application for the final user.
Pilot C: Air Quality and Pollution Monitoring
27. The monitoring station
GW
+
The user can select up to 10
sensors from a library of sensorsConfigurable sensing
through modularity
Pilot C: Air Quality and Pollution Monitoring
Consolidated design of the AGILE Industrial Gateway hardware reference design.
Main board Configurable
sensing through
modularity
Connectivity &
maintenance panel
28. Mapping to AGILE Architecture
Pilot C: Air Quality and Pollution Monitoring
29. Innovation - KPIs
The adoption of the DFM design methodology introduces a new sustainable and certified
solution in the market of air quality and pollution monitoring:
◦ solution tailored on customer requirements (thanks to DFM and configurator);
◦ cheap solution:
◦ cert. sys.: 200K€ for installation and 200k€/year for maintenance;
◦ 5K€-7K€ device cost, <2K€ for installation and 3K€/year for maintenance (Bosh-Intel solution is not certified and certifiable!).
◦ small dimension and high territorial coverage (180 x 360 x 150 mm vs 1-3 m3);
◦ easy to integrate, install and maintain; open and easy to extend;
◦ fully remotely controlled.
The platform allows managing heterogeneity and diversity: more than 150 sensors can be
plugged in the monitoring station, depending on the specific application context.
Time to market reduction: just 6 months to develop the monitoring station hardware, starting
from the industrial gateway reference design.
Pilot C: Air Quality and Pollution Monitoring
30. Deployment and Operation Plan
Phase 1 (M12-M18) - basic use cases setup and laboratory tests: concluded.
Phase 2 (M18-M26) - industrial and private demonstrator setup and test:
◦ hardware design and development (first release available);
◦ AGILE software stack porting and integration (ongoing);
◦ focused on the first test and evaluation of the AGILE hardware & software solution
(ongoing).
Phase 3 (M18-M36) - small rural town setup and test:
◦ Amaro (IT) and Martignacco (IT), plan ongoing.
Pilot C: Air Quality and Pollution Monitoring
Phase 4 (M24-M36) - metropolitan areas setup and
test: Udine, Milano (already agreed) and Dubay
(under discussion).
Phase 5 (M30-M36) - final pervasive demonstrator
setup and test: still to be defined.
Martignacco, Udine, IT
32. Overview
Objective: IoT technology can help optimize the shop operation and
management by monitoring the machines in order to provide a good
service to the clients.
Pilot D: Enhanced Retail Services
Temperature
Electricity
Distance
Light
Presence
33. Overview
Deploy a set of sensors to monitor and gather service KPIs to guarantee
the quality.
Pilot D: Enhanced Retail Services
Cold chain
Cold Chain
maintenance
Follow up and
temperature
alerts
Stock
Management
Alerts and stock
replenishment
Business
continuity
Power
consumption
and availability
alerts
Opening hours
Shutter
opening/closing
detection
Availability
Alert when
there are clients
in the check-out
point
Temperature
Sensors
Distance sensors Electricity
sensors
Light sensors Presence
sensors
36. AGILE Components Used
Agile-core
◦ ProtocolManager: To register and manage Zigbee protocol.
◦ DeviceManager: To register all devices used by the pilot.
◦ DeviceFactory: Used by the DeviceManager.
HTTP, api REST to interact with AGILE components.
Agile-OSJS, development and monitoring environment.
Agile-node-red, Development of monitoring flows.
Agile-protocol-zb, communication between devices.
Agile-sdk, library to access the AGILE API from NodeJS.
Pilot D: Enhanced Retail Services
37. Advantages of using AGILE
Facilitate the orchestration of all the events generated by the different
devices.
Facilitate the connection of different systems with the nodes offered by
node-red.
Standardize the implementation of applications to manage data
obtained by a different kind of devices.
Remote system management with all functions provided by RESIN.IO.
Pilot D: Enhanced Retail Services
38. Innovation benefits
AGILE can help our customer by:
◦ Improving customer experience
◦ Enabling real-time decisions through live monitoring
◦ Reducing cost through process automation
◦ Improving the brand image as being innovative by using IoT technologies
◦ In the future monitoring all the shops from a central console that displays
real-time information
Pilot D: Enhanced Retail Services
39. KPIs
Minimum support of Devices: Eight different types of devices to be
deployed and connected: Light sensor, Stock sensor, Proximity sensor,
Electricity sensor, Temperature sensor, Light alarm in the store, Beacon
detector, IoT display).
◦ The pilot D will use the 8 types of devices.
◦ For the demo we will use 4: Stock sensor, Proximity sensor, Temperature
sensor and IoT display.
Minimum development of applications: One AGILE application to
visualize the monitoring of the different sensors.
◦ We will develop:
◦ The node-red flow for monitoring
◦ TENTO AGILE Application in Node-JS using AGILE SDK.
40. Deployment and Operation Plan
Pilot Preparation: Define strategy to run the pilot (Oct 2017)
◦ Agree on physical scenario
◦ Define activities needed by employees to support operations.
◦ Agree on the physical devices to be deployed.
Venue Set-up (Jan 2018)
◦ Prepare the shop for the pilot, deploying and configuring the AGILE Gateway and the
IoT devices.
◦ Train employees.
Pilot Monitoring (Feb-Sep 2018)
◦ Monitor the execution of the Pilot in the shop.
◦ Gather data and KPIs to allow measuring the impact of the Pilot in the business.
Pilot Evaluation (Oct-Dec 2018)
◦ Evaluate the impact of the pilot based on the data gathered during monitoring phase.
Pilot A: Quantified-Self
43. Port Area Monitoring
We will examine how drones can be deployed in the event of a fire, explosion or other
incident and get a good view on the situation even before the emergency services arrive at
the spot. Time is crucial in these situations. Other applications around safety and the
environment are within reach. The incidents would be specific to emergency situations for
the fire department.
Pilot E: Port Area Monitoring
45. AGILE Components Used
Components used
◦ agile-rest,
◦ agile-dbus,
◦ agile-core,
◦ agile-ble,
◦ agile-dronekit (own dronekit)
Integration: Interfaces used/implemented
◦ BLE -> read sensortag
◦ WIFI -> read drone flightcontroller
◦ LTE/4G -> Long Distance Remote Connection to the GW
Pilot E: Port Area Monitoring
46. Innovation
Extensibility
◦ Multiple sensors can be added to the drone depending on the needs.
◦ Standardize the implementation of applications to manage data obtained by
a different kind of devices.
◦ Enhanced connection possibilities (4G, 3G, wifi, ble,…).
◦ Multiple communication protocols available.
Pilot E: Port Area Monitoring
47. KPIs
Stability
◦ Feedback is provided to the development team for the implementation of
the latest version of the AGILE Stack
Latency & reactivity
◦ Latency is ok for viewing cameras.
◦ Over 4G reactivity of the drone is not good enough. With drone legislation it
is not allowed since the drone has to be in line of sight all the time and has
to react immediately to the commands of the pilot.
Power consumption
◦ Not yet evaluated since the drone market evolves constantly.
Pilot E: Port Area Monitoring
48. Deployment and Operation Plan
Pilot Preparation: Define strategy to run the pilot (Oct 2017)
◦ Prepare PoC.
◦ Integrate Agile.
Pilot Integration(Jan-Sep 2018)
◦ Integration and use in other projects.
◦ The drone & Agile will be used in another project, results from the PoC will be
integrated there.
Pilot Evaluation (Oct-Dec 2018)
◦ Evaluate the impact of the pilot based on the data gathered during test phase.
Pilot E: Port Area Monitoring
51. Approach
51
• Goal: pre-field tests to validate AGILE software
before actual deployments
• Approach: Building upon the IoT-lab testbed
• Bare-metal access to 2700+ IoT devices
• Multiple deployments & heterogeneous nodes
• Single managing interface, common tools
• See www.iot-lab.info
AGILE IoT Testbed
52. Operation in AGILE
Usefulness: the IoT testbed is useful to experiment interplay of AGILE
gateway hardware/software with ”arbitrary” numbers of IoT devices
Advantage: lowering the bar of entry with remote access, hence no
need for local hardware deployment to test/experiment/debug an
AGILE deployment
Targets:
◦ Prior: testbed used daily by constrained IoT application/stack developers &
researchers
◦ In a 1st phase: extended testbed open to AGILE partners
◦ In a 2nd phase: extended testbed open to AGILE Open-Call winners
◦ Beyond: extended testbed open to other external developers/users of AGILE
AGILE IoT Testbed
53. Work Done
Added hardware: several prototype AGILE gateways (Makers version)
are now permanently deployed on IoT-Lab
Backend extension: The backend now enables AGILE partners to
securely & remotely access to AGILE gateways deployed on IoT-Lab, via
CLI (with SSH) and via a web browser
Added software: the AGILE gateways run the latest version of AGILE OS
on Raspbian
Documentation: we have documented how AGILE partners can use the
testbed in a tutorial available online
AGILE IoT Testbed
55. IoT-Lab AGILE Extension 1
IoT-LAB server
(AGILE frontend)
Gateway
IoT-LAB
sensor
(public frontend)
Sensortag
Web
SSH
User
AGILE IoT Testbed
56. IoT-Lab AGILE Extension 2
IoT-LAB server
(AGILE frontend)
IoT-LAB
sensor
(public frontend)
Web
SSH
User
Gateway
AGILE IoT Testbed
57. M19-M36 Planning
AGILE stack: further integration with AGILE stack, once it supports IEEE
802.15.4
Access: enable access/usage for 3rd party users such as AGILE Open-Call
winners
Hardware: deploy additional AGILE hardware on the IoT testbed,
including PiHat + shields for Xbee, LoRa
Software: on the AGILE gateways deployed in the IoT testbed, switch
from Raspbian to ResinOS
End-to-end mode of operation: enable use of AGILE hardware as IPv6
border router to enable secure end-to-end transport of data from IoT
devices to arbitrary remote location on the Internet
AGILE IoT Testbed
61. Pilots Evaluation
Each pilot has developed a pilot execution scenario and an evaluation
plan, including timing and milestones
Alignment with Crowdfunding Campaign and Open Call
KPIs have been identified and will be evaluated
Monitoring of pilots technical and operational risks
Apply the evaluation methodology and instruments of each pilot and
provide feedback to the technical WPs.
◦ Analytics
◦ Surveys
◦ Questionnaires