Back to the work

Work

The ENLYZE platform and what I designed

ENLYZE brings machine data, MES and ERP together in one model. Here is the platform from the machine to the decision, layer by layer, and which parts of it I designed.

From the machine to the decision

Three layers, read top to bottom, and underneath them the foundation they stand on.

parts I designed
23
parts are ENLYZE's product
5
layers from machine to decision
3
  1. 01

    Edge & connectivity

    Where a machine stops being a machine and becomes a stream of values somebody has to name.

    My design: 2 of 4

    • ENLYZE Edge

      My designenlyze.com

      The setup and diagnostics application on the edge device. Co-owned the concept, wrote part of the front end myself.

    • Data onboarding

      My designenlyze.com

      From a newly connected machine to usable data in a few days instead of weeks.

    • SPARK edge device

      ENLYZE productenlyze.com

      The hardware on the line that reads controllers, sensors and gateways, and can serve harmonized data back to the shop floor.

    • Connectors

      ENLYZE productenlyze.com

      The connector portfolio that reaches controllers, energy meters, MES and ERP systems.

  2. 02

    Cloud & data model

    This is where raw signals become objects and rules. All data ends up in one model that any feature can use.

    My design: 2 of 4

    • Object model

      My design

      Machine, order, run, downtime, reason, operator, shift. Product, design and engineering build on it.

    • Machine data and orders

      My design

      Process data and bookings in one view, so every measurement belongs to an order, a product and a shift.

    • OEE

      ENLYZE productenlyze.com

      Availability, performance and quality as one number, computed per order from the booking data.

    • Downtime logic

      ENLYZE productenlyze.com

      A threshold on a lead variable decides what counts as a stoppage, second by second and without anyone typing.

  3. 03

    App

    Every surface a plant touches, held together by one mental model.

    My design: 13 of 14

  4. Foundation

    Not a layer of its own but what all of them stand on. That includes the principles, the team, and the decision about what not to build.

    My design: 6 of 6

    • Design principles

      My design

      Five principles, written for ENLYZE and anchored in the team.

    • Design system

      My design

      Built in Figma and developed further for the whole company.

    • Research

      My design

      On site in the plants, from machine operators to management. Interviews read together with the numbers from product analytics.

    • Design leadership

      My design

      Product decisions in a trio with the CTO and the CPO. Hired and onboarded a designer, reorganised the handoff to engineering.

    • UX as a buying factor

      My design

      Customers saw the UI and UX as what set ENLYZE apart. For several, it decided the purchase.

    • Deciding what not to build

      My design

      ENLYZE Edge came instead of generic dashboards, because the plants lacked usable data.

How the parts connect

ENLYZE describes its use cases as a sequence of features. Some features carry several of them.