Con3187 Creating Industrial Middleware with Java ME and Single-Board Computers

Creating Industrial Middleware with Java ME and Single-Board ComputersSeptember 2016

2Copyright © 2016 Accenture All rights reserved.

About Us

Senior Technology Architect

Accenture

Global Java Community Lead

Twitter: @_deors

GitHub: deors

Technology Architect

Accenture

Global Java Community Champion

Twitter: @restalion

GitHub: restalion

Copyright © 2016 Accenture All rights reserved. 3

Related Sessions in Java One 2016

Monday, Sep 19 Tuesday, Sep 20 Wednesday, Sep 21

Introduction to Java ME 8 [CON3189]

Java ME and Single-Board Computers for Creating Industrial Middleware [CON3187]

All Your Faces Belong to Us: Building an Open Face Recognition Platform [CON6217]

12:30 p.m. - 1:30 p.m 2:30 p.m. - 3:30 p.m 3:00 p.m. - 4:00 p.m

Hilton - Golden Gate 6/7/8



Kevin HookeJulio Palma

Jorge HidalgoJulio Palma

Jorge HidalgoMariano Rodriguez


The Environment• We can find a lot of different machines, sensors, alerts, … into an industrial environment.

• Every single machine has usually a mechanism that allow us to know its state (visual or sound signals, communication ports, …)

• Operator has to decide the action to be executed (call maintenance team, restart the machine, do a little maintenance, …).

• Most of times reason why machine is not productive enough is simply lost, plants has not the information, it is lost or dispersed into some operator’s minds.

Problem description


This is a global challenge

Problem description


The plants• Each plant has different characteristics:

– Equipment

– Processes

– Legal requirements

• Easy to find old factories working together with new ones.

• Information from plants is not structured.

– And we need to show all this information structured to be useful.

Problem description


Problem descriptionDecision centers are also global






Management systems• Enterprises have management systems as complex as production line.

– Standard ERPs (such as SAP)

– Custom applications

• Our goal is retrieve all this information and create a model that let us make better decisions.

– Which plants are more productive?

– Which ones work better together?

– Anticipate needs for raw materials

• We need a way to retrieve information:

– Without errors

– Automatically (no human intervention)

– Real-time

Problem description


High-level diagram

Solution description


High-level diagram


Machines. We can’t touch!


High-level diagram



Board of directors.We can’t touch!


High-level diagram



Board of directors.We can’t touch!Covered by ERP


High-level diagram



Board of directors.We can’t touch!Covered by ERP

This is our domain


Our approach

• The idea is create customizable translation middleware:

– Reads output signals from machines.

– Send translated information to ERP.


Machine 1

Machine 2

Machine 3

Translation Middleware



ERP


Topology


Robot Simulator


Robot Simulator


Receiver Microservice

ERP Simulation



MongoDBMongoDBMongoDB


Schema• Java ME application.

• Running in a Raspberry Pi.

• Simulate different types of machines without the actual machine.

• Created for testing purposes.

• Communication with Translation Middleware via GPIO.

Robot Simulator

Robot Simulator Midlet

Robot Controller



Timeline• For this sample demo we’ll only manage five signals:

– Input signals:

• Start/Stop button

• Error button

– Output signals:

• Machine downtime

• Machine running

• Machine error

Robot Simulator

Machine running

Machine error

Machine down

Robot Simulator

Tim

elin

e

Wor

king

Hou

rs


UML Diagram

• Only four classes are needed to simulate our simplified robot.

• Two helper classes are created to simplify LEDs and buttons management.

Robot Simulator


Schematic• Two input signals:

– One connected to GPIO 17 for ON/OFF events

– One connected to GPIO 22 for ERROR events

• Three output signals:

– ON signal on GPIO 24

– OFF signal on GPIO 23

– ERROR signal on GPIO 25

Robot Simulator


Schema• Java ME application.

• Running in a Raspberry Pi.

• Translates the signals from Machine-specific to Receiver input messages

• Communication with Robot Simulator via GPIO.

• Communication with Receiver Microservice via REST interface.


MachineMiddleware Midlet

MachineMiddleware Controller

Robot Simulator



Timeline• For each signal from machine we create a new event.

• We add metadata information to the event:

– Machine ID

– Event timestamp.

• Status is not maintained in middleware. We receive signals, enrich and translate them to message that ERP can receive and understand.


Machine running

Machine error

Machine down

Robot Simulator


ON event

ERROR event

OFF event

Tim

elin

e

Wor

king

Hou

rs


UML Diagram





Configuration

• You can customize your input pins, device name and REST service URL.



Schematic• Three input signals:

– ON Signal in port 22

– OFF Signal in port 18

– ERROR Signal in port 24



Schema• It’s role is translate from Events to data that ERP can understand.

• Spring Boot application running into a Docker cotainer.

• In our sample project it stores data into a MongoDB database

• Exposes a REST interface to retrieve events and send intervals information to ERP application.


Spring Boot REST Services

Spring Data MongoDB

MongoDB


Timeline• Events sent by middleware are stored into database.

• Microservice returns information translated into intervals.

• Can receive events from different sources (Machines, Apps, …) through its REST interface.


Machine running

Machine error

Machine down

Robot Simulator


ON event

ERROR event

OFF event

ReceiverMicroservice

Tim

elin

e

ON interval

ERROR interval

Wor

king

Hou

rs


UML Diagram





Events• Events stores information of each signal from machines.

• They are a direct representation of information itself.



Intervals• Intervals are the same information but in the format expected by ERP.

• Intervals are information processed to be visualized.



Testing

• We can run a little test using JaSON Chrome extension.

– Launch a new event.



Testing

• We can run a little test using JaSon Chrome extension.

– Launch a new event.



Schema• There are a lot of difirent ERPs

– Custom

– SAP, …

• We need some program that let us create friendly reports.

• For our sample we’ve created a very simple application that shows an activity timeline.

ERP Simulator

Receiver

Vaadin App

RESTEasy


Timeline• Receiver Microservice returns information as intervals.

• ERP Simulator shows an activity table.

• Filter options are available.

• Application autorefresh information.

ERP Simulator

Machine running

Machine error

Machine down

Robot Simulator


ON event

ERROR event

OFF event

ReceiverMicroservice

Tim

elin

e

ON interval

ERROR interval

ERP Simulator

Wor

king

Hou

rs


UML Diagram

• We can easily view the activity of machines:

– Filtered by source (machine) and date

– In different dates.

ERP Simulator


View

• We can easily view the activity of machines:

– Filtered by source (machine) and date

– In different dates.

ERP Simulator


Demo


• Modern single board computers are powerful enough to run different roles into a full solution.

• Combination of availability, affordability, power compsumtion… make them a best choice for real solutions.

• Java ME provides us a powerful set of tools that allow us to:

– Capture data from phisical devices.

– Send data to other systems.

• Fine-grained architectures let us create powerful and flexible solutions.

• Combination of Java ME and Microservices take our solutions to the next level:

– One single language: Java!

– Comunications via GPIO and REST Services

– Containerized microservices

Conclusions


Questions

Copyright © 2016 Accenture All rights reserved.

• https://github.com/restalion/middleware-solution

References

41

https://github.com/restalion/middleware-solution

Con3187 Creating Industrial Middleware with Java ME and Single-Board Computers

Software