Skip to content

Installed base

Every machine learns from the ones like it.

Norlan groups the equipment by model, wherever it is installed. A fix found on one unit reaches the next one that fails, and you can see whether a problem belongs to one machine or to the model.

Checkweigher CW-500

Installed base · Berlin and Munich

BerlinMunichS1-PK-L1-0051S1-PK-L1-0052S1-PK-L2-0018S1-PK-L3-0033S2-PK-L4-0092S2-PK-L4-0093S2-PK-L7-0104S2-PK-L7-0105
MK

M. Keller · Munich · 06:05

Weights drifting since start-up. Static check is fine, it only goes off with the belt running.

One unit or the model

Know whether a failure belongs to one machine or to all of them.

The same fault on one unit and on every unit of a model call for different people. Norlan puts the units side by side, so you see which one it is before anyone starts taking a machine apart.

Checkweigher CW-500

Incidents per unit · last 12 months

ASONDJFMAMJJS1-PK-L1-0051BerlinS1-PK-L1-0052BerlinS1-PK-L2-0018BerlinS1-PK-L3-0033BerlinS2-PK-L4-0092MunichS2-PK-L4-0093MunichS2-PK-L7-0104MunichS2-PK-L7-0105Munich

It is this unit, not the model.

The drift keeps coming back on one checkweigher in Munich. Look at how it is installed on that line.

  • Which unit fails most

    Every unit of a model side by side, month by month.

  • One machine

    When it keeps coming back on one unit, look at how it is installed and run.

  • The whole model

    When it repeats across units, the root cause is in the model, and the conversation is with the manufacturer.

Knowledge per model

What Norlan knows about each model, and what it still needs.

Across every unit, Norlan finds the problem that keeps coming back, says which threads it learned it from and marks it validated once a technician agrees. Each model also shows what is missing: no documents yet, or nobody has described what the machine does. Norlan drafts that description for you to approve.

  • Recurring problems, with the threads they come from
  • Models without documents or context, as a list to work through
  • A drafted description of each equipment type, ready to approve

Checkweigher CW-500

Installed base · Berlin and Munich

Validated

Recurring problems

The dominant problem across the units is load-cell drift: five cases on three units in six months, almost always after pressure washing or a format change. Cleaning the load-cell housing before recalibrating is what holds.

  • Load-cell driftS2-PK-L4-0092 · MunichOpen
  • Load-cell driftS1-PK-L1-0052 · Berlin22 Jul

Built from 2 documents and 5 threads · what 3 technicians know

What Norlan knows about this model

InventoryDocumentedHistoryPatternSuggests the fix
Imported

The units arrive from the CMMS, grouped by model.

Inheritance

Written once for the model. Refined for each unit.

The manual, the parts list, the guides and what the machine does are attached to the model, so every unit has them from the day it is imported. What makes one unit different, a retrofit or the way it runs on its line, stays on that unit.

  • Documents and guides reach every unit
  • Each unit keeps what makes it different
  • A new unit starts with what the others know

How guides reach every unit

S2-PK-L4-0092 · Munich

Checkweigher CW-500 · one of eight units

From the model · every unit has it

Weighs every portion in motion and rejects anything out of range. Drift after pressure washing usually means brine under the load cell: clean before recalibrating.

ManualParts listGuide · Load-cell cleaning

This unit only

Mounted on a vibration-damping base after the 2024 retrofit, with the digital filter at 7. Above 60 packs a minute it needs the belt tension checked first.

Retrofit report · 2024

Questions about the installed base

Do we have to clean up our asset hierarchy first?

No. Sites, areas and lines come in the way your CMMS already has them, keyed by asset code, so a later import updates what is there instead of duplicating it. The model is added alongside the hierarchy, not instead of it.

Our equipment is the same model but not identical. Does that break it?

It is the normal case. What is true for the model sits on the model; what a retrofit or a line changed sits on that unit. Each unit shows both, so nobody mistakes one for the other.

What about equipment we only have one of?

They still get their threads, their documents and the assistant. What they miss is the experience of other units, which is exactly what the model view makes visible.

Who approves the description Norlan drafts for a model?

Someone on your team. The draft describes what the equipment type does, and it only becomes the model's context once a person approves or corrects it. What a unit does on your line is always written by your people.

Can the manufacturer see our units?

Only the threads you invite them into. Manufacturers who want the same view across their customers' units have their own page, and the argument for letting their engineer into the record is in Resources: The service engineer in the thread, not around it.

Book a demo

Bring a model you run more than once. We will show what its units could already share.

We start with the operation — which failures repeat, who gets called when something breaks, what the CMMS does not hold — and then show how Norlan would work on it.

What we usually cover

  • How an incident flows today, from detection to fix
  • Where the conversation actually happens: the systems, or calls and WhatsApp
  • What takes longer — the diagnosis, or getting the right people and information together
  • How much of what a technician knows is written down, and what happens when they are away
  • Which tools are really in play: CMMS, ERP, mobile, paper
  • What a pilot would measure, and how

Pick a time that suits the plant. Bring one failure that keeps coming back.

The call is with the people who build the product, with no qualification call first. Norlan is pre-general-availability and shaped with maintenance teams in pharma and food processing.