Skip to main content


Porting EdgeX to Pivotal Cloud Foundry

By Blog, EdgeX Foundry

Guest blog post by Trevor Conn, Principal Software Engineer, Dell Technologies

A short while ago I was introduced to the EdgeX Foundry platform when I attended a local IoT Meetup in Austin, TX. The presentation was given by fellow Dell Technologies colleague Jim White and I went up to introduce myself afterwards. We discussed the future possibility of making the EdgeX Foundry services cloud ready and I told him of my experience using Pivotal Cloud Foundry (PCF) in a production environment. Given the popularity of PCF, we thought it would make sense to see what it would take to port a couple EdgeX services into the platform.

The proof of concept I present below involves porting two of the foundational EdgeX services to PCF and then calling those services from the Virtual Device service running on my local workstation. Basically, I took the scenario Jim presents in Session 1 of the EdgeX Foundry Tech talks as my scope of work for this proof of concept. If you’re going to follow along, then you will want to fork the Github repos for the following three services:

You will be making changes to the first two, deploying those to PCF and then running the last service on your local machine while pointing to your PCF deployments.

The changes to be made to core-data and core-metadata are essentially the same:

1.Add three new packages for Spring Cloud functionality with regard to configuration, as well as PCF integration. You accomplish this by adding the following to the pom.xml
















2. Next, add another configuration class which will be annotated with @Profile in order to differentiate which configuration to use when deployed to a PCF cloud environment versus the default local environment. In my case, I called this new class “CloudConfig” and inherited from AbstractCloudConfig.

3. As you can see in the screenshot above, a new property is necessary to indicate the name of the data service we need to connect to. In our case, this is a Mongo database hosted outside of PCF. However, we still need to provide the cloud infrastructure with a name and a connection string whereby the persistence layer can function. I’ll go into more details about that below. For now, add the following entries to the file:

#—————–Mongo Cloud Config——————————————    edgex-core-data mongodb-coredata

The data-service value will be injected into the private dataServiceName member.

4. Since we are now distinguishing our configuration by profile, I needed to also add an @Profile annotation to the existing AppConfig class.

5. In our case, connectivity to Mongo was a little challenging. The PCF infrastructure at our disposal does not have MongoDB available within the cloud marketplace. That is to say, Mongo for PCF is not enabled. The only option available was to set up a Mongo instance on an external VM and then configure a user provided service within PCF consisting of the service’s name and a connection string. This limitation unfortunately meant I could not utilize the auto-configuration that Spring Cloud Service Connectors

Once I had the user provided service created, I then implemented my Mongo client within the above CloudConfig class like so:

So as you can see, the dataServiceName is used to find the service within PCF. Since we know we’re trying to access a Mongo database, I then cast the ServiceInfo to a MongoServiceInfo which gives me access to the URI I specified when creating my user defined service.

6. With those changes in place you’re ready to deploy. PCF will require a manifest file during deployment that provides parameters for the definition of the container your service will run on. Rather than including all of the content here, I will just link to the manifest file I created for the core-data service. The core-metadata manifest is the same except for the application name.

For a thorough explanation of what all of these settings mean, I refer you to the Cloud Foundry manifest documentation.

7. For the actual deployment, I found that it required use of both the Cloud Foundry command line as well as the Boot Dashboard provided within the Spring Tool Suite editor. There is certainly a way to streamline this step, but I have not had time to dig into it further. You would want to eliminate reliance on the Boot Dashboard for any kind of real deployment pipeline.

The issues I faced here were as follows:

  • The CF command line would provision the container appropriately, download the necessary buildpacks, create the necessary mappings for the user provided service to my application, but then it could never successfully build the application.
  • The Boot Dashboard was unable to do any of the above if I was deploying the service for the first time. At the point where it should have created the initial mapping of the services, it would just hang and then time out.

The approach I took for deployment of new services was to use the command line tool first, which would establish the necessary scaffolding in PCF, and then use the Boot Dashboard to deploy the code and get it built correctly.

Again, a little more work needs to be done here to make this cleaner.

8. And with all of that done, you’re ready to test!

Again, the test scenario involves running the Virtual Device service locally and pointing it to the deployed PCF endpoints. There are two changes necessary to the properties of the device-virtual project

  • In the src/main/resources/ file, you will want to change all of the entries to point to the relevant PCF routes instead of localhost
  • In the src/main/resources/ file, you will want to change the “” value to either your IP address or your fully qualified host name

        ** NOTE: In our case we were running our tests on a VPN whereby our local machines were on the same network as the PCF cluster. If you are behind a firewall trying to hit an external PCF cluster, this reverse lookup will not work without some additional network configuration. **

9. Start the device-virtual project as a Java application and you should start seeing the core-data service’s event counter increment.

The above was a fun, brief initiative undertaken in order to gauge the amount of work necessary to move the whole EdgeX Foundry platform to a cloud infrastructure. Due to the modularity of Spring along with the flexibility in the design of the EdgeX services themselves, the changes needed to accomplish this were not at all extensive. With this effort somewhat quantified, I look forward to hopefully working more on these capabilities in the coming year.

Performance Vs Flexibility – EdgeX Microservices Could be Combined

By Blog, EdgeX Foundry

Written by Dell’s Jim White, EdgeX Foundry TSC Member and  Chair of Core Services Working Group

I was posed a great question recently by one of our EdgeX contributors.  As he suggested, he was “wrapping his head around EdgeX” when he wondered if it made sense to have the core microservice (those being core data, core metadata, and core command) all be different microservices.  As he commented: “I think the microservice design is a good option, allowing to separate some components outside of the core of EdgeX”, but as he further suggested, “it seems that a lot of time and CPU is spent with RPC between those microservices.”  Would it be better (both easier and faster), he mused, “to have only one core service implementing all those together?”

As I indicated to this developer – he can consider his head fully wrapped around the EdgeX architecture if he is coming to such questions.  Indeed, his question is a legitimate consideration.  Architecture is about tradeoffs.  EdgeX is about offering options to meet the potential tradeoff considerations.  In this case, performance versus flexibility.

We (the original creators of EdgeX) believe there are legitimate reasons why you may want to separate those concerns (core data, metadata and command).  As each is a different function, you may need to improve or significantly modify one of the functions.

For example, we envision a very different and more secure offering of command microservice in the future that checks authentication/authorization before actuation is allowed on a device.  The microservices may need/want to separate their repositories.  Both core data and metadata use MongoDB today, but we have seen situations at Dell (and actually done implementations) where for security, performance, or other reasons that the underlying persistent storage is different for each microservice.  The sensitivity of the incoming sensor data may be such that the core data microservice has to be constructed differently and completely isolated from metadata and command to meet legal or regulatory considerations.  There may also be cases where, due to availability of resources or need (or again to secure some data), that the various functions need to reside physically on different platforms (EdgeX on a more distributed layout).

Having said this, there are also other use cases where these core microservices (and others) may be combined – as indicated by the contributor, likely for optimal performance, to in order to reduce footprint, etc..  In fact, at Dell we conducted such an exercise to prove this out.  By combining core data, metadata and command, we were able to reduce the footprint and improve performance of the Java core services significantly and we envision going forward there will be, potentially, an offering of a single “combined” core microservice in EdgeX.  This will be at the expense of flexibility, but for those looking to productize EdgeX, this may be a perfectly acceptable trade off.

Productization of EdgeX and its use in real world edge/IoT use case scenarios are apt to uncover all sorts of interesting needs.  EdgeX is a collection of building blocks to create a solution.  Some refinements and adjustments to EdgeX may, and probably will, need to be made to accommodate a particular use case.  The flexibility of EdgeX is its strength.  And don’t forget, the flexibility allows those who adopt and embrace it to figure out ways to add value – and thereby generate potential revenue – from their adaptations.

So, the contributor that asked the question about potentially combining microservices was absolutely right on track with his thinking.  We will welcome combined core service (or other services) as alternatives as EdgeX marches forward – while at the same time maintaining separate core microservices to support other use cases.  The beauty of microservices is that they can be replaced and augmented in many ways – in some cases by collapsing them.

EdgeX Foundry Member Spotlight: IOTech

By Blog, EdgeX Foundry

Keith Steele, IOTech CEO, EdgeX Foundry Board member and Technical Steering Committee (TSC) Chair gives his views on why the EdgeX Foundry project has generated so much momentum in just six months and spotlighting the importance of credible commercialization partners.

Since the April launch, the EdgeX project has evolved into a growing and vibrant ecosystem of more than 60 companies contributing to the emergence of an open, secure platform to facilitate interoperability at the IoT edge.

The project dropped its first community release, dubbed ‘Barcelona’ in October, as part of a bi-annual release roadmap established by the project TSC and recently announced an alliance with the Industrial Internet Consortium (IIC) to collaborate on best practices and test beds.

The next release called ‘California’ will focus on security and manageability features as well as very significant performance and footprint improvements driven by the availability of new Golang based microservices.  There will be a California preview release in January with a full ‘California’ release in June 2018.

Many large technology providers are spinning up plans to adopt and end users are starting to incorporate EdgeX into their deployment roadmaps. Many POCs are also in progress.

EdgeX Momentum

What’s driving momentum?

First and foremost, there’s a market need. The Industrial Internet of Things (IIoT) market is projected to grow to $195B in the next few years (source Markets and Markets) , with at least 40% IoT data stored, processed, analyzed at or near the edge (source IDC).

Secondly, there’s a technology gap as identified by the IIC’s Edge Computing Task Group, the Open Fog Consortium and many other industry-leading companies. Peter Levine from Andreessen-Horowitz has provocatively suggested that the age of edge compute is taking over the cloud.

“The current model of cloud computing is too slow. A small difference in the time it takes to refresh a machine learning model for a drone or car could be the difference between life and death. Computation will move to the edge. The same drones, cars, and IoT devices that need their models updated quickly will form a peer-to-peer network with which to distribute time-sensitive tasks…cloud servers will still be around…responsible for doing offline computation across large data sets.”

The emergence of software platforms is recognized as vital to support this new paradigm at the Edge, having a pivotal strategic role to lowering barriers to IoT adoption to the larger market prize.  This means that EdgeX has hit the market at the right time to meet the growing needs for distributed computing to support the sheer scale of devices coming on steam and advanced analytics to produce business value.

The other big attraction is that it is truly open and vendor-neutral. The platform has been carefully architected to enable significant value-add around a lowest-common denominator interoperability framework, enabling companies of all sizes to innovate rather than reinvent.

EdgeX is a loosely-coupled, polyglot architecture, agnostic to silicon and operating system, the enabling microservices can be written in any programming language to run on any hardware; this level of flexibility is very important given the heterogeneous nature of IoT.

Openness is a critical success factor for scale by enabling an ecosystem of plug-and-play components that work together compared to proprietary platforms that further fragment the landscape

The EdgeX partner ecosystem is also a key factor in EdgeX momentum; the community has driven through open collaboration a well-defined roadmap, helping deliver well thought-out and relevant solutions for foundational functionality; the security working group is a notable example of this, with at least ten of the top IoT security companies on the planet working together to define EdgeX platform API requirements.

Vertical Solutions based on EdgeX are also starting to gain traction indeed Samsung is chairing a new Vertical Solutions Working Group in which end users will sponsor industry and use-case focused projects to define requirements for the core EdgeX platform and develop and deploy test beds in their respective industries.

As part of this initiative Samsung is spinning up a project for smart factories and National Oilwell Varco recently proposed one for Oil and Gas. We will see additional projects for use cases spanning Smart Cities to Buildings to Farms to make sure the foundational platform meets the needs of a wide variety of applications.

EdgeX Commercialization

There’s also another important player in the open source ecosystem: The commercialization partner.

EdgeX is targeted at the industrial segment of the Internet of Things, many applications here are business critical requiring long lifespan, therefore a key consideration organizations face is how to leverage Open Source in a sustainable and risk-free way.

Some companies will choose to take a cut of the open source code and maybe support themselves, but many companies simply want to exploit their value-added applications and leverage EdgeX to sell infrastructure or monetize services around IIoT deployment rather than focus on supporting the foundational code base.

For this reason, many companies are prepared to pay for professional highly proactive long-term support, guaranteed roadmap evolution, influence, and specialized services on top of the open source core.

As a founding member of the EdgeX project, IOTech realized this at an early stage of project development and strived to be the key commercialization partner, helping companies to enjoy the benefits and flexibility of open source, while mitigating the risks of its use.

In addition to taking a proactive role supporting the evolution of the EdgeX open source code, IOTech is creating professionally packaged, commercially supported versions of the core EdgeX software called Edge Xpert and developing complementary licensed IP which will offer through the partner ecosystem.

In summary, the EdgeX ecosystem is growing fast and there’s clear momentum for global adoption. I don’t think that’s an accident. EdgeX has all the attributes: it’s vendor-neutral open source, it meets a real market need, and it has a modern polyglot microservices architecture. At the same time, it is backed by some of the largest IoT players and vendors in the global IoT market.  Meanwhile, it has vendors like IOTech that can take the risk out of commercial adoption.

For a more information on IOTech’s EdgeX-related product and service offerings visit or contact Keith at

EdgeX enables Phenomenal Applications

By Blog, EdgeX Foundry

Guest blog by Marc Hammons and Tyler Cox (Dell Client CTO Software Architecture Team)

For those not yet in the know, EdgeX Foundry is a platform that provides IoT edge computing; making it easier to connect your “things” (sensors and devices) to the rest of your enterprise and allowing your enterprise to interact and help control those things.

Today, EdgeX is headless – there is no user interface.  The beauty of the platform is that it enables any type of interface – new or existing.   The idea is for organizations to use any preferred cloud or enterprise dashboard and management console with EdgeX to monitor and control their things that communicate via any standard.  The EdgeX community believes this presents an incredible opportunity for differentiation via entirely new and innovative user interfaces to help manage IoT deployments.  A few organizations like Dell have built some UIs for demonstration purposes. Now, we encourage EdgeX community members to add unique value by creating open source or commercial interfaces for EdgeX.

During a recent local hackathon, the Dell client CTO team completed a unique interface for interacting with sensors and devices that interoperate through the EdgeX framework.  The result was an amazing augmented reality (AR) interface to observe the readings coming from sensors and actuate the devices with hand signals.  Take a look at the video below demonstrating several things being controlled by the Dell AR app integrated with EdgeX.

EdgeX helps to normalize control of the edge to a common set of easy to use APIs regardless of the underlying communication protocols. This demo shows how those APIs allow some wonderfully new and imaginative ways to visualize and control resulting data feeds.  EdgeX helps users stop reinventing and instead focus on innovation – this is where the payoff of IoT and edge computing starts to show signs of revolutionizing our lives!

This demo shows connectivity and control of a Modbus motor, SNMP managed Patlite, and Bosch BLE sensor pack through the AR headset and EdgeX, but imagine how the same principles could be used by support technicians inside of a complex factory control room, workers performing field maintenance on machines, sensor-enabled distribution centers, or even working within your company’s own server room.  That’s what could happen as we, the IoT community, collaborate on common interoperability frameworks like EdgeX, which makes it easier for application providers to focus their efforts on creating amazing interfaces among other valuable innovations.

For those interested in more of the tech details, the team used the Meta 2 AR headset and the Darknet open source neural network framework with its “you only look once” (YOLO) algorithm to help enable the system to recognize the various connected devices.  Unity was used to create the AR application interface that interacts with EdgeX version 0.2 running on the Dell Edge Gateway 5000.  The entire application was created in the two day hackathon – which speaks to the ease of use and utility of the EdgeX framework.

For more information, you can check out these resources:

EdgeX ARM64 Support

By Blog, EdgeX Foundry

Written by Gorka Garcia and Federico Claramonte from Cavium 

Cavium, a provider of highly integrated semiconductor processors that enable intelligent networking, communications, storage, video and security applications, recently joined EdgeX Foundry and is already an active contributor.

We are using our OCTEON TX family of Multi-Core 64-bit ARM Embedded Processors to target the intelligent IoT Edge Gateway market.  We believe in open source technologies for this market and value EdgeX Foundry for its scalability and flexibility.

Over the past few months, Cavium has helped create a strong ARM64-based version of the EdgeX platform that is on par with the versions for other CPU platforms.  Our particular focus was on ensuring efficient execution of the platform on OCTEON TX processors using a intelligent edge gateway reference design.

As we started the port, the first issue we met was the lack of ARM64 support in EdgeX docker containers. As a first pass, we ran EdgeX without using containers and just calling the micro-services directly. This worked at first try, as the EdgeX software is written in java and it did not use any native libraries. Then, we created a new set of ARM64 containers that can be deployed to ARM64 in the same way as x86. While doing this, we simplified the docker container process creation by implementing some scripts that will handle that task. When running all the containers in our lower memory ARM64 boards, we noticed a peak of memory usage at startup. After some investigation, we managed to reduce these memory peaks by simplifying the startup process, managing to also improve the startup time of EdgeX. These are changes that benefit all supported platforms, not just ARM64. Right now we are involved in the porting of some micro-services from java to Go Lang, which will help reduce memory footprint even further as well as improve the overall performance.

All our work has been contributed to the EdgeX Foundry community as we believe interoperability is key for IoT solutions success and are committed to help grow the EdgeX ecosystem. Throughout this whole process, we had support from the EdgeX community, answering our questions and giving feedback on our work. Cavium will continue supporting the EdgeX Foundry project to make sure it runs well in our ARM64 processors as well as doing generic optimizations of the services that could benefit the whole community.

For more developer resources, please visit the EdgeX Foundry wiki page.

The Future of EdgeX is Go Go Go with Go Lang

By Blog, EdgeX Foundry

Written by Jim White, EdgeX Foundry TSC Member and  Chair of Core Services Working Group

To begin this post, I need to give you a little history.  When my team and I started on Project Fuse (which became EdgeX Foundry) at Dell some two years ago, we knew the micro service architecture was going to be the mechanism to deliver the edge/IoT platform to satisfy our ideal platform.  What we weren’t sure about was the programming language to use to get started in writing our microservices.  As we looked around at options we knew we needed a very powerful and flexible programming platform that would provide all sorts of tools and connectors to the various protocols of the IoT world.  Many of the newly emerging languages, like Go Lang, just didn’t ring the bell on the availability of tools and connectors at the time.  So, we went with Java as our primarily programming language as it was well known to us, provided all the libraries and connectors we could want, and it seemed to be in line with the other products we wanted to integrate with at the time.  We also knew that the microservice architecture would allow us to add or replace a microservice in the future using a different language if we needed.  To be honest, our project was a proof of concept system so the choice in language was less relevant then than today.

As we fast forward to EdgeX’s introduction this spring, it was clear from the community that while the concept architecture we built with Fuse was on the mark, we needed to eventually improve EdgeX’s performance, footprint, and scalability – especially to meet the mission critical edge use cases we would encounter.  Languages like Go Lang have come a long way, and many of our community members were already seeing incredible improvements using Go Lang in their IoT solutions.  Indeed, even at Dell, as we were getting ready to introduce EdgeX into the open source community, we had started to experiment with Go Lang (and other languages) and had even developed some replacement micro services to demonstrate the potential performance/footprint improvements while also trying to understand the challenges.

Today, I am pleased to announce that the EdgeX community has formalized plans to develop preview EdgeX microservices in Go Lang and make them available by Jan 31, 2018.  This will be a preview of the California release of EdgeX scheduled for the spring of 2018.  We will release these Go Lang services but will not be making any other changes to the system’s functionality or API set – in other words, these Go-based microservices should be drop in replacements to their Java counterparts.  And for the foreseeable future, we plan to support both the Java and Go Lang versions as we know the Java and Go Lang communities are vibrant and may want/need these alternatives in their particular IoT solutions.

Specifically, we plan on releasing the following microservices in early 2018 as part of this preview release:

  • Core Data, Core Metadata, Core Command microservices
  • Export Client microservice
  • Initial elements/libraries to a Go Lang Device Service SDK

Additional microservices and facilities may be added to this list depending on work accomplished between now and then.  Much of this work is actually already underway – in parallel to our efforts as a community to get the Barcelona release out this fall.  We hope to have some preliminary performance and footprint numbers (in comparison to the existing Java microservices) so people will have an understanding of the impact of this work by the time we showcase the Barcelona release in the fall.

We are hopeful this work will also help demonstrate the community’s commitment to drive down the size and speed of EdgeX to meet today’s edge platforms.  Much work remains, but this will help provide proof positive that the platform is heading in the right direction and will help galvanize the community around our desire to solve real world IoT/edge use cases.

By the way, don’t let this work suggest that EdgeX is going to use Go as the only development language going forward.  One of the core tenets of EdgeX is to be polyglot and use the tools of choice for each microservice to best meet the use case need.  As an example, others in our community are already on record (IoTech, Inc. for example) in their desire and focus to eventually develop a C based device service and device service SDK.  C/C++ will probably make a lot of sense when trying to operate a device service on very constrained device hardware and offers extreme performance improvements.  Go simply offers a popular alternative to Java that is seeing wide use in the IoT community and helps us get the collective footprint and performance of EdgeX down fairly quickly.

So, do you like to work in Go?  Lend us a hand!  Come join us in the EdgeX community as we try to build the best open source IoT/edge platform on the planet!

Getting Data from EdgeX to Google Cloud IoT Core

By Blog, EdgeX Foundry

Written by Jim White, EdgeX Foundry TSC Member and  Chair of Core Services Working Group

The EdgeX Foundry community continues to grow as does the EdgeX functionality thanks to contributions from around the world.  In this post, I’d like to highlight an exciting addition to the EdgeX “northbound” interface.  That is, a new capability built into the EdgeX export services that allows EdgeX data to be sent to Google Cloud IoT Core.

What is Google IoT Core?  It’s a Google public beta cloud service (what Google calls a fully managed service) that allows you to easily and securely connect, manage, and ingest data from millions of globally dispersed devices.  See for more details.

For those unfamiliar with the EdgeX architecture, the services responsible for organizing, formatting, transforming, etc. the sensor data collected by EdgeX and sending it to enterprise or cloud based systems are the export services.  In the EdgeX and IoT communities, we often call theses the “northbound” services or interfaces as they are typically depicted on the top end of any diagram that depicts an edge platform.  “Southside” services or interfaces are those that communicate with sensors, devices or other systems even closer to the “things” edge and are usually depicted at the bottom of any diagram.

Bernard Van Haecke from Schlumberger, Menlo Park, CA office dug into EdgeX when it was released and recently had his connector contribution approved and posted as part of the Export services.  What his addition does is allow the export services to pipe data to Google IoT Core.

EdgeX export services already allowed for sending data to any MQTT topic or HTTP REST endpoint generically and to Azure IoT Hub specifically.  We believe going forward, there will be lots of these connectors – some public and some private (perhaps you will need one to your own closed enterprise system).  But Bernard will always have the distinction of being our first new connector on the northside.  Thanks Bernard!

You can learn more about the Google IoT Core export on the EdgeX Wiki here:

EdgeX Foundry is on display at IoT Solutions World Congress

By Blog, EdgeX Foundry

This week, EdgeX Foundry will be on display at IoT Solutions World Congress taking place in Barcelona, Spain, from Oct. 3-5, 2017.

The EdgeX Foundry booth (Booth E541) will be filled with innovative member solutions from Canonical, CloudPlugs, Cumulocity, Dell/RSA, ForgeRock, IOTech, Linaro, NetFoundry, Neustar, RFMicron, Vantiq and VMware. Other EdgeX Foundry members will also have EdgeX on display in their own booths, including Analog Devices, Bayshore Networks, Device Authority, EnOcean Alliance, FogHorn and Opto 22.

If you’re in Barcelona, stop by Booth E541 to see the live demonstrations, chat with members and learn more about the EdgeX ecosystem. There will also be a happy hour from 3-5 p.m. on Tuesday, Wednesday and Thursday, so stop by for drinks and light snacks!

Demos in the EdgeX Foundry Booth (Booth E541):

Canonical: Canonical will show how Ubuntu and Ubuntu Core, the Operating System of Choice for smart IoT, can be used as the IoT gateway Operating System to run EdgeX on.

CloudPlugs: CloudPlugs will be displaying the Edge One™ IIoT Gateway on Dell Edge Gateway 3000 controlling Modbus devices and integrated with EdgeX. CloudPlugs is an advanced IIoT platform that uses fog computing to easily develop, deploy and manage industrial devices and applications.

Cumulocity: Cumulocity IoT scales up to geo-distributed multi-tiered cloud and on-premises high availability hybrids and down to a single node fully featured Edge platform – all with the same secure carrier grade software architecture. Cumulocity will be showcasing the Edge platform and a range of connected devices for consumer, industrial and environmental use cases. Cumulocity IoT rapidly accelerates IoT adoption.

Dell: The Dell demo will use the EdgeX platform to manage 3 devices – a people counting camera, thermostat with heat/cool fans, and Patlite signal tower running on a Dell Edge Gateway 5000 and 3000. Through EdgeX, the people counter will actuate (through EdgeX rules engine) the thermostat and fans based on the number of people it detects.

RSA: Highlighting monitoring and threat intelligence for the edge (i.e. the gateway and attached devices), this demo consists of an RSA agent that runs on gateway and monitors, collects, and sends information to hosted cloud service for security evaluation/action. Dell Technologies offers the industry’s broadest IoT infrastructure portfolio including Dell gateways and RSA security, enhanced by curated partnerships and the EdgeX Foundry ecosystem.

ForgeRock: ForgeRock will be using EdgeX and the Identity Edge Controller (IEC) to demonstrate the integration on a Dell Gateway 5000. The IEC demo will deliver the following inbound services – attestation, auto onboarding at boot, authorization and token validation. ForgeRock® Edge Security offers complete end-to-end security for IoT deployments. It ensures the integrity of IoT devices and their communication using secure, standards-based tokens instead of insecure hard coded usernames and passwords, or managing thousands of individual PKI certificates. It adds a rock-solid security layer to IoT hardware used at the edge, including leveraging highly secure on-chip Trusted Execution Environments (TEE) if available, and comprehensive, policy based controls for publishing and subscribing to data streams from edge devices, making it as easy to protect data coming from IoT devices as it is to protect a web page.

IOTech: IOTech will be showcasing the new GUI they have developed to support EdgeX.  The demo will showcase how the GUI can be used to browse device and device service related information, as well as being able to visualize device generated data. IOTech is a vendor neutral middleware specialist aiming to be at the heart of the edge infrastructure opportunity by leveraging EdgeX technology to accelerate solution time-to-market and leveraging the partner ecosystem of key IoT players to facilitate a global market opportunity for the company.

Linaro: The demo will feature sensor data communication from the Zephyr microPlatform into an Edge X gateway. It also demonstrates a newly available feature in the Zephyr microPlatform, LWM2M. The Zephyr microPlatform is a minimal, secure, and OTA-enabled platform for product development that is continuously updated for the life of the product by Open Source Foundries.

NetFoundry: NetFoundry will be showing two demos. Demo 1 uses the NetFoundry we console to spin up a network to show superior application performance and security across any network, including the public internet. Demo 2 highlights NetFoundry enforcing the Neustar Trusted Device Identity (TDI) security and performance requirements from edge-to-cloud. NetFoundry enables customers to quickly and easily spin up highly-secure, performant app-specific networks at scale.

Neustar: Neustar will be showcasing two use cases of Trusted Device Identity. The first use will be demonstrating a secure firmware update to an endpoint using an edge gateway to validate payload and confirm source. The second demo will be demonstrating secure end point to app path protection over a core network and terminating in two end points (an app and a sensor). This use case will a show immediate revocation and resilience to man in the middle attacks. IoT solutions need to scale securely beyond the traditional PKI implementations. Neustar is launching Trusted Device Identity (TDI), a unique, scalable, and real-time approach, providing the means to securely communicate to and from end points with immediate revocation capability.

RFMicron: RFMicron is helping to extend EdgeX into the realm of real-world data with Smart Passive Sensing™ devices. These battery-free and maintenance-free wireless sensors can be applied in a wide variety of industrial, automotive and medical applications. The demo showcases the RfmApi software that employs edge processing to convert raw sensor data into trusted information. RFMicron helps protect people and equipment in real-time with new industrial IoT software connecting smart passive sensors into the powerful EdgeX backbone. The latest RFMicron sensors support full AES-128 encryption for secure commands and data transfers in wireless mode for blockchain applications. RFMicron helps protect people and equipment with new industrial IoT software connecting smart passive sensors into the powerful EdgeX backbone.

VANTIQ: VANTIQ’s open platform integrates with a wide range of systems and we are excited about furthering our association and integration with the EdgeX Foundry community. VANTIQ provides the only application platform-as-a-service that enables the rapid development of real-time, event-driven applications.

VMware: In partnership with SAP, VMware will be demoing the Smart Popcorn Machine which pops popcorn and monitors the temperature, pressure, etc. of the machine. The data is pushed up to the SAP Cloud and to VMware’s new IoT Pulse Center which manages, monitors, secures, and onboards the sensors within the Popcorn Machine. The demo does not currently integrate with EdgeX live but will be in the future and the value proposition will be talked about. VMware Pulse IoT Center is a secure, enterprise grade, end to end IoT infrastructure management solution that allows IT and OT to have complete control of their IoT use case, from the edge to the cloud by helping them manage broader, operate smarter, innovate faster and protect better.

If you want to see more EdgeX Foundry in action, you can visit other member booths including:

Analog Devices: Booth D485

Bayshore Networks: Booth B211

Device Authority (Booth B240): Device Authority is the leading provider of IoT IAM. Our KeyScaler™ platform provides trust for IoT devices and the IoT ecosystem, to address the challenges of securing the Internet of Things.

EnOcean Alliance (Booth B254): EdgeX is a crucial part for EnOcean based gateways which bring sensor data, provided by self-powered and wireless sensor solutions, to the cloud and thus enabling cognitive buildings. At the stand, we will demonstrate EnOcean based self-powered wireless solutions, enabling highly flexible, maintenance-free applications for the Internet of Things and supporting the transition from intelligent to cognitive buildings.

FogHorn: Booth E571/B211

Opto 22 (Booth B286): Dell Edge Gateway 5000 with EdgeX collecting and controlling operational data on a working model wind turbine. Real-time data can be accessed through EdgeX Console at public URL admin/123. Opto 22 manufacturers industrial controllers, I/O, and edge computing devices bridging the physical and digital worlds for IIoT.

Striim (Booth B221): The demo is real time predictive maintenance and predictive quality for manufacturing.

In the Industrial Internet Consortium booth (Booth E571), you can also catch Sensify Security’s demo that showcases completing porting their blockchain-based IAM system to the EdgeX platform.

If you’re not in Barcelona, stay tuned on @EdgeXFoundry for pictures and the new EdgeX Foundry Youtube channel for videos!

EdgeX Foundry Member Spotlight: Switch Automation

By Blog, EdgeX Foundry

The EdgeX Foundry community is comprised of a diverse set of member companies that represent the IoT ecosystem. The Member Spotlight blog series highlights these members and how they are contributing to and leveraging open source solutions. Today, we chatted with Deb Noller, CEO and co-founder of Switch Automation.

What does your company do and what is your role? I’m the CEO and co-founder of Switch Automation. Switch is committed to creating a more sustainable world, one broken building at a time. We recognize that buildings contribute 39% to CO emissions in the U.S. alone and have a massive impact on everything from climate change to employee health and productivity. Our end-to-end solution helps enterprises uncover hidden inefficiencies in their real estate portfolios and provides real-time insight to optimize building performance.

How would you describe your company in three sentences?  Switch Automation is a smart building platform that collects disjointed building data, aggregates it in a cloud-based global framework and synthesizes the data into actionable insights. From on-site IoT monitoring devices to energy metering and sub-systems, our configurable dashboards provide a single interface where a range of facilities management professionals can understand building performance, employ fault detection and diagnostics, and execute real-time control and command. The Switch Engineering Services team, in-house data scientists and integration experts work closely with customers to ensure smooth implementation and a best-in-class user experience.

Why is your company investing in the IoT ecosystem? When Apple introduced the iPhone, they didn’t set out to build every single app. The IoT industry is enormous and there is plenty of room for many companies to be successful. However, it’s a complex space and can be difficult to build an end-to-end, quick to deploy solution. My belief is that best in-class solution providers will partner together to solve this problem and deliver more flexible, scalable options for customers.

How has IoT impacted your company? What benefits have you seen or what do you expect to achieve? IoT is our business. In the last 5 years, we’ve implemented the Switch Platform in more than 70 million sf of real estate and helped a wide range of customers realize hundreds of thousands in operational and energy savings.

Given the forecast for 70 billion connected devices by 2025 and the building-related IoT market growth to $76 billion in 2020, we will continue updating the Platform to accommodate innovative technologies, artificial intelligence and machine learning as they become operational mainstays.

Businesses currently have to invest a lot of time and energy into developing their own edge computing solutions. What are some of the business or technical challenges you have faced when adopting edge computing technologies? How have you overcome them? We had to build our own gateways and software stack to provide the interoperability, security and connectivity between systems and devices that our customers expect. Security can present a big challenge, but fortunately we’ve partnered with Dell for our hardware solution, the Switch Gateway. The Gateway utilizes TPM, Secure Boot, and Trusted App to help tamper-proof the Switch Platform. We then built a state of the art software solution on top of the Switch Gateway to reinforce protection from external threats.

Why did your company join EdgeX? For the last five years we’ve seen what a truly cohesive IoT ecosystem can do to foster connectivity, sustainability, scalability and generate huge savings for our customers.

One of our clients, a leading financial institution with 7,000+ branches, uses the Switch Platform to monitor signage, lighting, space temperatures, occupancy, energy usage and more. Prior to implementing the Platform, their operations team endured the tedious and time-consuming practice of gathering vast amounts of data from multiple disparate sources then wrestling it into actionable insights. Each branch was an isolated silo of information and by the time the information was filtered down to meaningful findings, the window for significant savings had closed.

By leveraging the Switch Platform to connect vital systems, our customer now spots problems in real time and engages the appropriate resources to repair it before incurring costly operational and capital expenses.

We want to help more businesses achieve these kinds of results and believe that supporting collaborative industry endeavors like EdgeX is a great step.

How are you going to use the framework? We already use the framework and recommend it to our customers as the best way forward for their business.

Where do you see enterprise and industrial IoT in 20 years? In 20 years, enterprise and industrial IoT will be the norm. Cars in the 1950s didn’t have electric locks–now they do. People will have devices all over their buildings and the data will be freely shared across the organization. Automated analytics, machine learning and AI will all have a seat at the table and align with evolving customer needs.

In the IoT age, what shouldn’t be connected and why? Just because you can connect to a plethora of widgets, doesn’t mean you should. I like to ask, “Does connecting to this device deliver a worthwhile and tangible benefit to the end user?”

EdgeX Foundry Member Spotlight: Samsung Electronics

By Blog, EdgeX Foundry

Today, EdgeX Foundry announced Samsung Electronics has joined as a Platinum member to help accelerate open source development of their industrial IoT edge platform. You can view the complete news release here.

We had the chance to sit down with Kyeongwoon Lee, Senior Vice President for Samsung Electronics, to discuss why they joined the EdgeX community and how they will be using the framework.

What is your your role within Samsung?

I am one of the core contributors and enablers for Samsung’s IoT business in terms of connectivity with our variety of products. By working with the IoT ecosystem, I am very active in the open source community and leverage different standards such as Open Connectivity Foundation (OCF) and IoTivity.

What is Samsung’s vision for Industrial IoT? 

Our traditional portfolio includes Consumer Electronics (CE), Information technology & Mobile Communications (IM) and Device Solutions (DS). But there is a lot of potential in Industrial IoT (IIoT), such as Smart Manufacturing, Smart Building and Smart Lighting and Smart Energy Management, and we believe we need to build a synergy and true seamless interoperable IoT services across the business domains. As one of the biggest manufacturing companies around the world, we have many infrastructures and a lot of experiences but, if we collaborate with EdgeX Foundry, we believe that our IIoT efforts will be much more clear and stronger. We will be able to continue building and growing an IIoT business.

What are some of the business or technical challenges you have faced when developing IoT edge solutions? How have you overcome them?

The biggest technical challenge is interoperability. There are a variety of devices in factories that are part of proprietary solutions and aren’t talking to each other.  Even in global standardization, there are still Brownfield areas that are used by proprietary solutions which makes interoperability a challenge. The other challenges are scalability and flexibility. For example, real-time operations is very important and in order to meet performance criteria, we need scalability.

We’ve overcome some of these challenges by working with open source such as IoTivity, and leveraging some of the IoT standards like OCF. In addition to this, when it comes to the IIoT ecosystem, we need more flexibility per vertical specific use case, so that we could expect the faster and more optimized deployment. We believe that the best answer is to collaborate on a pure open source platform that is vendor neutral and can work with existing technologies and services. This will help us deploy the very best to the industry and developers. 

Why is Samsung joining EdgeX Foundry?

We are attracted to EdgeX Foundry’s value proposition and recognize that it is the best solution for several of our challenges – interoperability, scalability, flexibility and transparency to existing cloud services. EdgeX Foundry will help us create lightweight edge solutions with the support a growing community with Industrial IoT edge platform expertise.

How are you planning to use the EdgeX framework? How do you think it will help you achieve your business goals?

EdgeX Foundry will help Samsung create interoperable and lightweight edge solutions that will help us grow and strengthen our presence in Industrial IoT.