What you define in the control plan reaches the machine.

Occama is a quality management system for manufacturers that connects the rules with what actually happens in production. Curator centralises control plans and recipes. Collector guides the operator through measurement by those plans and collects the results.

Collector: recording a measured value against tolerance

Occama is used by

  • Volkswagen
  • Škoda Auto
  • Kiekert
  • Brembo
  • Vitesco
  • Festo

Sound familiar?

Most manufacturers run quality in two separate worlds: in one, plans are written; in the other, someone is supposed to measure according to them. Between the two sit Excel, paper and a lot of manual work.

  • “Our control plans live in Excel.”

    A different file for every product, a different structure for every plant.

  • “Every plant uses a different form.”

    The data cannot be compared or merged, because nothing is named the same way twice.

  • “We have thousands of control plans and changes are a nightmare.”

    A change means pulling the old version from every measuring station, printing the new one and distributing it. Then hoping nobody was missed.

  • “Operators have to hunt for what to measure.”

    A production control plan often does not carry the values, it only refers to them. Tolerances are on the drawing, the record goes in a report. Whoever measures has to piece it together.

  • “We have an old CAQ system and IT no longer wants to maintain it.”

    An application that has to be installed on every station, kept at the same version and taken offline for upgrades. Harder to run year after year.

  • “We want to connect quality with MES, production and ERP.”

    Measurement lives outside the production order, so results are matched up by hand.

  • “We need better traceability.”

    During an audit it is hard to prove that what should have been measured really was, and as often as it should have been.

  • Occama connects those two worlds.

    Excel is a good tool for writing a control plan. It's not a good tool for someone three floors below to measure by.

From rule to data in five steps

  1. 01

    Define

    In Curator you model the control plan or recipe: parameters, tolerances, measurement frequency, instruction images.

  2. 02

    Publish

    You release the change to the shop floor in a controlled way. Not by sending out a new file, but by publishing a version.

  3. 03

    Measure

    Collector shows the operator what to measure for the given operation, order or product. And how.

  4. 04

    Record

    The operator enters the measured value. The system immediately relates it to the defined parameters and tolerances.

  5. 05

    Evaluate

    Results move on: to your databases, reporting, SPC or higher-level systems.

CuratorOne place for what should hold in production

Curator isn't a control plan editor. It manages everything that governs how your plants produce and measure: control plans, recipes, parameters, catalogues, inspection structure and above all the changes you keep making to them.

  • CentralisationEvery control plan and recipe in one place, across products and plants.
  • Change managementYou do not edit individual files. You change a parameter where it is defined.
  • Controlled publishingA change reaches exactly where it applies, and it is clear which version is valid at the station.
  • StandardisationYou unify how control plans are created, named and structured across the company.
  • ScalabilityIt handles environments with ten thousand control plans and tens of thousands of rows. At a Tier 2 supplier that is nothing unusual.
Curator: recipe list, 963 records in one place
One change, one placeA published control plan edit takes effect at the station without sending files around.

Send us one of your control plans

Take any Excel file you use today and send it to us. We will send back a short video showing what that same plan looks like in Curator and how an operator would measure by it in Collector.

Send a control plan

We ask nothing in return and you don't have to talk to us.

Collector: visual inspection of a part at the machine
Always the valid versionThe operator measures by the control plan that is valid right now. Not by a printout from three revisions ago.

CollectorA digital measurement guide for the operator

Collector turns the control plan into concrete action. Based on the operation, order or product it shows the operator what to measure and walks them through it step by step.

  1. Receives the relevant measurements for a specific operation, order or product.
  2. Sees what to measure, with which gauge and to what tolerance.
  3. Can open instructions or a work instruction image.
  4. Enters the measured value.
  5. Colour coding shows immediately whether the value is in tolerance.
  6. Data moves on to other systems.

Collector can be called from the context of a production order or a higher-level application. It doesn't have to be a separate island. It can be a step in your existing workflow.

What changes

We don't compare ourselves with specific systems feature by feature. The difference is in the architecture and in how the data is handled day to day.

Today

  • Control plans in Excel and on paper
  • The measuring station has to be a Windows PC on a wired network
  • A new version means downtime and walking from station to station
  • A change is distributed as a new file
  • Every plant has its own data structure
  • Measurement lives outside the production order
  • Results are retyped by hand
  • Measurement is a separate application the operator has to open

With Occama

  • Central management of plans and recipes
  • A browser on a panel or tablet at the machine is enough
  • Updates happen without touching the stations
  • A change is published in a controlled way
  • One structure and catalogues
  • Measurement tied to the production context
  • Structured data ready for further processing
  • Measurement is a step in your workflow: Collector is called from the production order

Occama fits into your IT landscape

You do not run quality in isolation. Occama assumes that ERP, MES and other production applications run alongside it and that measurement data has to move on.

  • API

    Communication with adjacent systems.

  • Production order link

    Collector can be called from a higher-level application.

  • Data export

    Structured for reporting, SPC and further analysis.

  • K-fields

    Mapping your catalogues to the key numbers you already use in other systems.

  • Single sign-on (SSO)

    Occama connects to your corporate SSO.

  • Cloud or on-premise

    Hosted by us or on your own server.

Occama produces clean, structured data that you then work with in SPC and other tools. Cpk and process capability stay where you are used to calculating them.

Who Occama is for

Occama makes sense in mid-sized and large manufacturers where quality is defined by documented specifications and measured against them. Automotive Tier 2 to Tier 4 is where the benefit is easiest to see. It's not the only place it belongs.

Quality manager

Control plans under control, changes published in a controlled way, a traceable measurement process.

Process engineer

Recipes, process parameters and manufacturing specifications in one structure.

Operator

Sees what to measure, with which gauge and to what tolerance. No piecing it together from a drawing, a plan and a report.

How we start

The hard part is not deploying the application, it is putting the data in order. What data you have, what it is called, what it means, what the catalogues look like and what exactly counts as a control plan at your company. Thinking the structure through usually takes longer than configuring the system. That is why we deploy Occama together with you.

We don't just deploy software. We help you unify control plans, data and the measurement process so the system actually works.

  1. 1

    Half an hour online

    Free

    We show Curator and Collector and ask how you manage control plans today. By the end you know whether it fits your environment, and we give you a ballpark price.

  2. 2

    Deployment

    We convert your control plans, configure the system around the way you run quality, and start measuring at the stations. Scope and schedule are already clear from the first meeting.

How pricing works

Occama is licensed by the number of stations where measurements are taken and by the number of plants. The licence includes the first stage of implementation: converting your control plans and configuring the system around the way you run quality.

The price per measuring station is fixed and is not multiplied by how many features you use there. The more stations, the lower the price per station, and beyond a certain scope covering a whole plant becomes a flat fee.

We give you a ballpark figure for your size of operation right in the first meeting, before you have to request anything internally.

What people ask us most

What happens to the control plans we already have?

We convert them. Whether they sit in Excel or in an older CAQ system, the goal is to get them into one structure that can be managed centrally, including unified naming and catalogues. The conversion is part of the implementation, not work you have to do upfront.

How long does deployment take and what do we have to provide?

The scope is driven by the state of your data, not by the size of the installation. From you we need access to what you use today (control plans, catalogues, the list of parameters) and one person from quality who decides what the resulting structure should look like. You get the schedule after the first meeting, once we know what we are working with.

Will Occama run on our server or in your cloud?

Whichever suits you. The features are the same either way. Occama is a web application, so nothing is installed at the stations; Collector runs in a browser on a panel, tablet or PC at the machine. If your internet connection drops, an installation on your own server makes sense, with Collector communicating over your internal network.

What can Occama show during a customer audit?

For every measurement it records what was measured, against which version of the control plan and with what result, and the data can be exported. That gives the audit a traceable trail from the specification to the measured value. Exactly what form of record your auditor requires is something we go through during deployment.

How much training do operators need?

Collector is designed for the shop floor, not the office: the operator picks a control plan and enters measured values, with no other choices in front of them. Training is therefore short and someone from your own quality team can run it. Measurement masks and control plans are configured by the process engineer in Curator, not by the operator at the machine.

Which languages does Occama run in?

The interface is fully localised into Czech, English and German. The language is set per user, so people can work side by side in different languages within one plant.

We will show you on your own control plans

Half an hour online. We show Curator and Collector, ask how you manage control plans today, and give you a ballpark price. If it makes sense, we arrange a longer demo for your team.

Pick a time (30 minutes)

A calendar opens where you choose a free slot. It takes a minute and there is nothing to fill in.

Or write directly:
[email protected]Zdeněk Šiška, Sales Director