EmberNet
EmberEdge

The screen at the machine.

EmberCORE runs the whole estate. EmberEdge is what an operator sees at the node: sign in with a PIN, log an issue, call maintenance, end a shift. It keeps working when the link is down, and it sends everything up when the link is back.

What it is

A small app that does one job at the node.

Loopback only

EmberEdge answers on the node itself and nowhere else. Nobody signs in to it from another computer on the plant network.

Sign in on the box

Operators use an employee ID and a PIN. People assigned to the box use their email and the passphrase they set in EmberCORE. Both work with no link.

Locked down

It ships hardened and runs with the least privilege it needs, and it locks an ID after repeated wrong PINs.

Syncs when it can

Flux carries the sync first, with HTTPS to EmberCORE as the backup. With neither, it keeps its own journal and sends it in order when a link is back.

On the node

Sign in once, work, and sign out for the next person.

These are real screens from the shipped EmberEdge 0.1.3 image, running in a lab with sample people. The keypad is the sign-in. Home carries the floor actions, any active alert, and the link state.

The EmberEdge sign-in screen, a keypad with Employee ID active and links to Staff sign in and Emergency sign in
Sign in: an employee ID and a PIN, checked against the sign-in list EmberCORE sent to the box.
EmberEdge Home for an operator, with Log an issue, Call maintenance and End shift, an alert, and the Switch operator and Link tiles
Home: Log an issue, Call maintenance, End shift, an alert to acknowledge, and the Link tile.

Put EmberEdge at your machines.

Let's talk about your plant and the people who run it.

Request a demo