Pilot · Pre-launch Operational memory system for maintenance teams

Do you know what worked last time? We remember.

SHAMAN builds a living knowledge base of your plant - it forms automatically as technicians work, and supports them in real time.

CMMS → when / IoT → what / SHAMAN → how
Apply for a pilot See how it works
  • Offline-first
  • On-prem pilot
  • Every answer cites its source
01 / Audience Who it's for

Who are we building SHAMAN for?

01 · Front line

Maintenance technician

A breakdown, and the clock is running. You need a short list of what to check right now - and you want to know what worked here last time on a similar symptom.

Ask in plain language - get steps and context.
02 · Shift

Shift supervisor / team lead

A shift handover only counts if it leaves a trace. Without one, the next crew starts the same work from scratch.

Every repair leaves a note. The next shift knows what to watch.
03 · Engineering

Maintenance / QA - manager, engineer

You want order, not one more spreadsheet. You need evidence: what was done and on what basis (source, revision).

Every answer has a basis - document, page, revision.
03 / Product What we build

SHAMAN is an OMS - Operational Memory System

It doesn't replace your CMMS or IoT. It adds the missing layer: "how we actually do it here".

01 / Context

Documents + history + notes

Everything the plant already has - manuals, procedures, work instructions, team notes - becomes a single source.

02 / The "how" steps

What to check and why

A short list of actions for the specific symptom - plus what worked last time on something similar.

03 / Repair memory

Symptom → steps → outcome

Each repair leaves a takeaway for the next shift. The knowledge stays in the plant.

Ask in plain language

"Pressure drop - what should I check?" - you get steps and context. No training course required.

"What worked last time?"

It surfaces similar cases from your plant and the notes left after repairs - not the general internet.

Sources and revisions

Every answer points to the document, page and revision. If the data isn't there, it says "I don't know".

On the floor, not in the office

Designed offline-first and for on-prem deployment in pilots. Connectivity never blocks the work.

04 / Trust Security

Security and compliance

Offline-first

Connectivity never blocks the work. It syncs when the network returns.

On-prem in pilots

Your data stays inside your own infrastructure.

Every answer sourced

Document, page, revision. No source - no answer.

SHAMAN supports technicians at work - it is not a tool for monitoring or rating people.

05 / Pilot Pilot programme

We're looking for plants to run pilots with

We want to build operational memory together with the maintenance team that will actually use it. We'll agree the scope and terms after a short call.

Our side

What we do in the pilot

  • 01 We deploy SHAMAN in your infrastructure (on-prem) or - if you prefer - on an environment we provide for the duration of the pilot.
  • 02 We ingest selected documentation - PDFs, procedures, work instructions.
  • 03 We set up the context for a chosen area (e.g. one line or machine group).
  • 04 A short onboarding on shift - and from that point on, "what helped" starts staying in the plant.
  • 05 We collect feedback and improve the product.
Your side

What we need from the plant

  • 01 A contact person in maintenance. Someone to run the pilot on your side.
  • 02 Access to documentation and approval to test within an agreed scope.
  • 03 Sign-off from IT - environment, access, security rules.
Apply for a pilot or a free consultation
06 / Contact

Not sure whether SHAMAN fits your plant?

Start with a short, free call. We'll work out together whether a pilot makes sense at your site - no obligations and no 60-slide deck.

  • We reply by email within 2 business days.
  • In that reply we propose a time for a call - the phone number is optional.

Leave your details

Pick what brings you here - we'll get back to you within 2 business days.

Use your company domain - we do not reply to enquiries sent from private mailboxes.

Do not include sensitive personal data or confidential details about the plant.

The data controller is BLANKLOGIC AI sp. z o.o. Data from this form is used solely to reply to your enquiry. You have the right to access, rectify and erase it. Details: Privacy Policy · Terms of use of the form.

Submitting this form does not conclude a contract, and the stated response time is not a contractual commitment.

Thank you.

We'll be in touch within 2 business days to propose a time for a call. If it's urgent, email us directly at kontakt@blanklogic.ai.

07 / FAQ Questions

Frequently asked

No. SHAMAN does not replace a CMMS. It adds operational memory on top: "how we do it here" and "what worked last time on a similar symptom". It also runs as a standalone application, with no CMMS at all.
We design it offline-first, so that work on the shop floor never depends on the network. Syncing happens once connectivity returns.
In a pilot we assume an on-prem deployment inside the plant's own infrastructure. The data does not leave your environment.
Answers cite their source (document / passage / revision). When the data isn't there, the system says so instead of guessing.
No. SHAMAN exists to help with repairs and knowledge handover, not to rate technicians.
With a short call: we check the fit, the requirements and the pilot scope. No pitch, no slides.
We write only from addresses in the @shamanai.app and @blanklogic.ai domains. Any access to plant systems is agreed with your IT, in writing, before a pilot starts - never ad hoc by email.