Shift Log
Shift log add-in · Quality specificationsOptional add-in

Quality specifications: one place, versioned, for what a sample is measured against

In many plants the specification lives in a PDF, a spreadsheet and the lab’s memory — and when a limit changes, it has to be changed in three places. Quality specifications is a Shift log add-in: grades and their limits per product in one place, versioned, and Batch records, the Production plan and Analytics all read from it.

In short

  • Product → grade → limits (min, target, max) per parameter and sampling point, with an in-process target range and a release limit in separate scopes.
  • Every change is a new version with a “valid from” time: an older sample is judged with the limits in force at its own time. Four-eyes publishing can be switched on.
  • A batch opens with a target grade and measurements are judged against it; an out-of-limit result is flagged with the parameter name on the sheet, on the vessel summary and in the PDF.
  • In analysis, the target range on the trend, the samples outside it and the share within it.

What is wrong today?

Quality changes the limit in one place, production looks at another copy. When the two drift apart, a sample is measured against the wrong limit — and afterwards nobody knows which limit was in force at the time.

“In spec” is often decided in someone’s head. For in-process measurements the goal is to steer production; for release it is the limit promised to the customer. If both live in one number, either production is too strict or release is too loose.

How it works

Quality writes and publishes; production and the lab work from the same source.

  1. Product and grade

    Under the shared product list you add grades, with a customer label too. Campaign, Batch records and the Production plan see the same product.

  2. Limits, in versions

    In a draft, per parameter and sampling point: min, target, max, unit and method, with an in-process or release scope. A grade without limits can be marked too: its samples get no verdict.

  3. Publishing

    A published version cannot be changed; the next change is a new version. The first version can be valid from a past time, later ones only from now or a future time. With four eyes, someone other than the last editor publishes.

  4. Grade on the batch

    A batch gets a target grade at opening; the template can make it required. On an open batch the target grade can be changed with a reason, and the change stays in the batch’s chain. The correction helper pre-fills the in-process or the release target.

  5. Verdict and deviation

    A sample is judged against the limit in force: in spec or out of limit, with the parameter name. For event-log batches with an out-of-limit qualifying measurement, closing needs a new, passing measurement or a justified “Release with deviation” approval by an authorised person, if the template allows it.

What the plant sees

Every view reads from the same published version.

Quality specifications page
Grades per product, the version in force and its “valid from” time, an unpublished draft marked; per grade the version history: who, when, why.
Batch sheet
The band of target grade and latest measurement, with out-of-limit parameters listed; on the vessel summary marked “out of limit”.
Batch PDF
A “Target grade and release” part: the verdict of each sample and, for a release with deviation, the reason and the approver.
Production plan
The grade of a plan row comes from Quality specifications, so the plan and the sample talk about the same grade.
Analysis (with Analytics)
The target range in force at the sample’s time on the trend, with “samples outside the target range” and “within target range (share)” views; a dashboard tile’s band can be taken from Quality specifications.
Product A · StandardVersion 3 · valid from: 2 Nov 2026 06:00
ParameterScopeSampling pointMinTargetMaxUnit
Water contentin-processReactor—0.200.30%
Water contentreleaseFinished product——0.25%
DensityreleaseFinished product1.021.041.06g/cm³
  • Sample 10:40 · Reactorwater content 0.34 %out of limit — water content (max 0.30)
  • Sample 13:15 · Reactorwater content 0.22 %in spec
A sketch with made-up data, not a screenshot: a published version of a grade and the verdict of two samples.

What it needs, and how to order it

What it does not do

So you know what to expect — and what not.

Further reading

Frequently asked questions

What is the difference between the in-process target range and the release limit?

The in-process target range is for running production: what the shift should steer the process towards. The release limit is for release: whether the product is in spec. In Quality specifications they are separate scopes, so the in-process target can be stricter than the release limit.

What happens to older samples when a limit changes?

Nothing: the change is a new version with a “valid from” time, and every sample is judged with the limits in force at its own time. A published version cannot be edited.

Does it need Batch records?

On its own, Quality specifications is the versioned home of your specifications, and the Production plan’s rows take their grade from it. The target grade on a batch and the per-sample verdict come with Batch records; the target range on a trend comes with the Analytics module.

Let's start a pilot

We'll show you OPEREX on your own operational processes — no strings attached.

Request a demo
Newsletter

Follow how OPEREX evolves

New modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.

You can unsubscribe anytime — the link is at the bottom of every email.