Skip to content
Norlan

Integrations

Your systems of record stay where they are. Norlan is the layer they never had.

The CMMS keeps the work orders, the ERP keeps the assets, the document library keeps the manuals, and the assistant your company already allows keeps being the assistant. Norlan sits between your people and all of that, and holds the reasoning none of them was designed to hold.

Ask about your systemsHow a pilot works

One incident, both systems

Norlan ↔ CMMS · write-back

Product direction

  1. Incident closed in Norlan

    Cause, action, verification · from the thread

  2. Work order WO-4821 in the CMMS

    Created or updated, keyed by asset code

  3. Status back to the thread

    Closed · parts issued · hours booked

How it sits

People above, systems of record below, Norlan in between.

Assets, locations, history and manuals come in. Cited answers, approved procedures and closures with a cause go out to the people who need them — and, on the roadmap, back to the work order.

Your people

Technicians and operators at the machine · supervisors and maintenance managers at the panel · the manufacturer, only when you let them into a thread

threads · photos · voice · closures

cited answers · approved procedures · where knowledge is thin

Norlan · the operational memory layer

  • Threads
  • Assistant
  • Guides
  • Line workflows
  • Models

assets and locations · work-order history · manuals — imported, never migrated

Your systems of record — untouched

  • CMMS / GMAO

    work orders · history

  • ERP

    assets · locations

  • Document library

    manuals · SOPs

The four connections

Each one with its state, stated plainly.

What an integration project usually needs from you is an export and a decision about what may be read. Where it needs more than that, the label says so.

CMMS / EAM

  • Installed base and preventive work imported

    Locations, assets and the preventive plan come in from an export of your CMMS or ERP — SAP PM, Maximo, Fiix, Limble, MEX or whatever you run —, keyed by asset code, so a re-import never duplicates. The tree you already have is the tree Norlan uses.

  • Write-back

    An incident closed in Norlan can create or update the work order, and the order's status comes back to the thread. It is the pattern that repeats most in the market — issue, order, status back — and the one that stops a memory from looking like a silo.

Documents

  • Loaded as they are

    Manuals, SOPs, schematics, service bulletins, in the folders they ended up in. Norlan proposes the model each one belongs to, and a person confirms. No conversion project before the first answer.

  • Ingestion filters first

    What may not be read is blocked before anything is indexed — by file name or by content, set by your administrator. Payroll, commercial, legal, anything you name.

Your assistants — MCP

  • Norlan as the knowledge server your assistant reads from

    If your company already standardised on one assistant, Norlan can be the knowledge server it reads from: the asset's record, cited, with your permissions. You keep the assistant; you gain the memory.

API and exports

  • Everything you put in comes out

    Threads, guides and closures in JSON; documents in their original format. At the end of a contract, or whenever you ask. Nothing in Norlan is the only copy of something you own.

Questions about integrations

Which CMMS?

Any system that can export its installed base and preventive plan: SAP PM, Maximo, Fiix, Limble, MEX. Enterprise and mid-market systems both support that starting point. Write-back is on the roadmap and we will tell you exactly where it stands for yours.

Do we need a project to integrate?

An export and a decision about what may be read. The installed base comes in as a file keyed by asset code; the documents come in as they are. Nothing is migrated, and nothing in your CMMS changes.

Can Norlan open work orders?

Not yet, and the assistant says so if you ask it to. Write-back — an incident closed in Norlan creating or updating the order, and the status coming back to the thread — is product direction, labelled as such above.

What is available today, and what is being built?

A pilot runs on the import of your installed base and documents, the machine threads, the assistant answering from your manuals with its sources, and closures and guides drafted from the thread. Writing back to the work order and serving your own assistant are being built with the first plants. Before a pilot starts we tell you in writing which is which.

Can our existing assistant read Norlan?

That is the direction: Norlan as the knowledge server your existing assistant reads from, with the asset's record, its citations and your permissions. It is not in place today. If your IT policy allows only one assistant, this is the conversation to have early, and we will answer in writing.

Book a demo

A 30-minute walkthrough built around the plant's machines, not a canned demo.

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.

Book a demo

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.