MenterisPL

For manufacturing plants

See where your shop floor loses minutes.

Pallets wait for pickup. Stations wait for material. We check it on footage from the cameras in your plant and show how many minutes per shift are lost, and where.

  • We measure zones and objects, not people
  • Billed per project
  • We say so when it is not worth it

How it works, as a diagram

Example values

Event record
Place: Set-down area B
Type: Pallet waiting for pickup
Start: 10:42
End: 11:06
Duration: 24 min

One shift, 6:00 to 14:00

  • empty
  • occupied
  • occupied too long
In this example: 3 events, 92 min in total. There is one principle: we check how long a marked zone stays occupied or empty. The threshold is set in the project.

The problem

Short waits rarely reach the report.

A long breakdown gets written down. A pallet waiting at the set-down area and a station without material disappear into the shift total.

The plant knows its total downtime. It does not know where the time goes, or why.

Where
Which spot on the floor has material or a station waiting most often.
How long
How long a single wait lasts and how much adds up over a whole shift.
When
At which hours and on which shift it keeps happening.

Use cases

3 situations we start from.

They all come down to one measurement: how long a marked zone stays occupied or empty.

  • Pallets and containers waiting for pickup

    Situation

    The set-down area is full, a pallet stands still, containers wait between departments. Nobody records it, because nothing broke.

    What we measure

    How long the pickup zone stays occupied and how many times per shift it exceeds the agreed time.

    What the team gets

    An event log: place, type, start, end and duration. A short clip for each event.

  • A station waiting for material

    Situation

    The buffer in front of the station is empty and the station stands idle. The shift report shows a lower output at best.

    What we measure

    How long the buffer zone in front of the station stays empty and at which hours it repeats.

    What the team gets

    A shift report: number of events, total time and the hours they repeat. Optionally an alert to the person who can react.

  • Congestion in zones and blocked aisles

    Situation

    Too many pallets build up in a zone, or an aisle is blocked. Movement on the floor slows down before anyone reports it.

    What we measure

    Build-up in a marked zone and the time an aisle stays blocked.

    What the team gets

    An event with its place and a clip. The manager can add the cause, because the picture alone does not explain it.

These describe typical situations, not deployments. With you we start by checking whether the problem exists at all, and how often.

Counting pallets or products passing a point is an add-on at most. When a photocell or a machine counter is enough, we say so.

Review on footage

First we check it on your footage.

Before anything is installed, we count the lost minutes on footage from the cameras already running in your plant.

  1. We pick one place

    Together we point at the spot on the floor where the most time is lost.

  2. We take about a week of footage

    From existing cameras, as an export from the recorder. No hardware installed.

  3. We count the minutes

    We check how long the zone was occupied or empty and at which hours it repeated.

  4. We hand over the result and a verdict

    You get a result in minutes per shift and an honest view on whether a project makes sense.

A review can end with “a sensor is enough here” or “this is not worth it”. If so, you will hear it.

Book a call about a review

Working together

How we work.

  1. A conversation

    We ask what you produce, where time is lost and whether that spot is the bottleneck.

  2. Review on footage

    About a week of footage from existing cameras at the chosen spot. A result in minutes per shift.

  3. Implementation

    Scope, hardware, price and acceptance criteria are agreed before work starts. We use existing cameras where the camera view allows. Where it does not, we add 1-3 cameras.

  4. After implementation

    Support and change terms are agreed separately.

We bill per project. We do not require a multi-year subscription.

Principles

What we hold to.

  • We measure zones and objects, not people.

    We care how long a pallet or a station waits. We do not rate employees, build rankings or supply data for bonuses or penalties.

  • We do not recognise faces.

    We do not identify people. It is not needed to measure how long a zone stays occupied.

  • We say so when a sensor is enough.

    If a photocell or a machine counter solves the problem, you will hear it from us.

  • We say so when it is not worth it.

    A review can show the losses are too small for a project to make sense. That is a result too.

  • A person confirms the cause.

    No movement in the picture does not mean a breakdown. That is why the manager adds the cause of an event.

Questions

What people ask most.

Are our cameras enough?

Often yes, if the camera view allows. Sometimes 1-3 cameras have to be added where the current ones cannot see. We check this during the review.

What does it integrate with?

Integrations are agreed in the project. They depend on what the plant uses and who needs the information.

How is it priced?

We prepare a quote after the review, for a specific project. Scope, hardware and acceptance criteria are agreed before work starts.

Do we have to sign up for a subscription?

We do not require a multi-year subscription. We bill per project, and support after implementation is agreed separately.

How long are recordings kept?

The retention period is agreed in each project, in line with the law.

What about employee privacy?

We measure the state of zones and objects, not people's work. We do not recognise faces or identify people. As a rule the plant remains the data controller and we process data under a data processing agreement. We confirm this in every project.

What do you not do?

We do not do in-line quality inspection or machine OEE measurement. We do not build safety systems, although we do measure a blocked aisle as a zone event. We do not stop machines automatically and we do not rate people's work.

Team

Who you talk to.

The company is run by 3 partners. All of them sit on the management board.

  • Jakub Kowalski

    Board member

  • Jakub Kossakowski

    Board member

  • Szymon Łysek

    Board member

Menteris sp. z o.o., Jonkowo, Poland. KRS 0001228343, NIP 7394030592, REGON 544219881.

Contact

Book a call about a review.

Tell us what you produce and where time is lost on the floor. We will reply and suggest a time to talk.

Prefer to pick a time right away?

Book a call in our calendar.

Open the calendar(opens in a new tab)

Write to us

The form needs JavaScript. Write to contact@menteris.com or book a time in the calendar.

A few sentences are enough. For example: what the plant makes and where material waits most often.

We will use the form data to contact you about your enquiry. Privacy policy(opens in a new tab)