Rigo One

Summary

Rigo One is a quality management and traceability software for batch-based industrial operations. It brings controls, documents, specifications, results and owners together in a single batch record, so that releasing sooner and controlling more stop competing: evidence review and the release decision happen in one place, with the grounds on record.

The product organizes the operation around a concrete unit: the batch. Each batch gathers its origin, its stages, its controls with specification, its balance, its documents, its incidents and the final decision. Five owners work on that batch record with distinct actions, and every transition is recorded with author, time, grounds and the workflow configuration version in force.

What problem it solves

When an audit asks about a batch, or a shipment is held, the answer is usually scattered across systems and people.

Evidence lives in emails, spreadsheets and shared folders.

Every control, document and result stays attached to the batch that gives it meaning.

Nobody knows for certain whose turn the next step is.

Every open item has an owner, and every person sees their next action.

A batch is released with no record of why it was decided that way.

The decision keeps who acted, what they verified and on what grounds.

Who it is for

Rigo One is built for industrial operations that manufacture in batches or discrete orders and need to coordinate several people around the same quality decision.

Quality Management

See what is on hold, why, and how much volume depends on resolving it.

Production Management

Confirm that the requirements are covered before authorizing preparation.

Laboratory Analyst

Add results and records, and correct a measurement without erasing the previous one.

Document Reviewer

Approve or return a batch record, stating in writing what was missing.

Authorized approver

Decide the release with the complete set in view, and leave a record of it.

What it includes

How the workflow works

Preparation and review advance as parallel branches. Adding a record, approving it and authorizing the release are distinct transitions, performed by distinct people.

Management

Prioritizes by risk and pending volume.

Production

Verifies the requirements and authorizes preparation.

Analyst

Submits records or corrects a measurement.

Reviewer

Approves the evidence or returns it with an observation.

Authorized approver

Records the release decision.

A documentary approval does not remove an out-of-specification result or an open deviation. The workflow configuration defines when the mass balance is required and who authorizes the release; publishing a new version of that configuration does not modify batch records closed under the previous one.

Industries and profiles

The demo includes 10 profiles. Each one defines its products, stages, raw materials, controls with range, documents and its release criterion. The rule that runs is common; what changes is the profile configuration.

A generic core profile is also included (receiving, transformation, control and release) for operations that do not fit the previous ones.

What you can try in the demo

Five guided tours, with fictitious data. You can pause them, resume them, restart them or explore on your own without following any.

Unblock a batch · 4–6 min

Spot the missing record, submit it, approve it and authorize the release, moving through each perspective.

Resolve a deviation · 6–8 min

Investigate an out-of-range result, record the correction, reconcile the process loss and verify the closure.

Prepare an audit · 3–4 min

Reconstruct the batch history, review the evidence and download the complete batch record.

Find a pattern · 3–4 min

Ask the copilot for the batches that share a raw material, a piece of equipment or a line, or that have a parameter above a threshold, and open the batches it returns.

Release for a customer · 4–5 min

Compare the same batch against two customer specifications, review the version in force and its history, and apply a concession from the catalogue of accepted exceptions.

The demo lets you attach test files (up to three per action, 5 MB each) to see how evidence stays bound to the action, its owner and the batch.

Current scope and limits

The demonstration is a working prototype with fictitious data. We would rather state precisely where the limit is.

The profiles, ranges and criteria shown are illustrative: they are not recipes, specifications or regulatory criteria, and must not be carried over to a real operation. Scope, integrations and the implementation plan are defined during the evaluation.

Regulatory framing

Rigo One organizes batch evidence the way quality and food safety management standards ask for it; it does not replace your management system and does not certify anything by itself.

ISO 9001:2015 · 8.5.2

Identification and traceability: every batch keeps its material genealogy, its stages and its linked records.

ISO 9001:2015 · 8.7

Control of nonconforming outputs: an out-of-specification result or an open deviation (nonconformity) blocks the release even when the batch record is complete.

ISO 9001:2015 · 10.2

Nonconformity and corrective action: investigation, containment, correction and verification are recorded as distinct steps, each with an owner and a rationale.

FSSC 22000 · HACCP

Backward and forward traceability by raw material batch, and the complete history that a mock recall requires.

21 CFR Part 11 (FDA) and Annex 11 of the EU GMP ask for the same thing underneath: knowing who did what, when and on what grounds, over data that cannot be altered without leaving a trace. Rigo One is built for that path, and the regulatory scope is settled during the pilot.

Audit trail: who, what, when and on what grounds

In the demo: Every transition keeps author, time, rationale and the version of the workflow configuration. · In the pilot: Server-side timestamp and an immutable record.

Role-based access control

In the demo: Five perspectives with actions exclusive to each role: a documentary approval does not release. · In the pilot: Corporate authentication with the roles of your organization.

Electronic signature

In the demo: Not included. · In the pilot: To be defined according to the agreed regulatory scope.

Data integrity (ALCOA+)

In the demo: A correction keeps the original measurement and is recorded as a correction. · In the pilot: Input validation and environment backup.

Change control

In the demo: The workflow configuration is versioned, and every batch keeps the version it was decided under. · In the pilot: Versioned specifications with formal approval.

Computerized systems validation

In the demo: Not included. · In the pilot: Validation plan agreed with the client.

Rigo One does not certify anything by itself: certification depends on your management system. What it brings is the path towards compliant electronic records, with the regulatory scope, root cause analysis and effectiveness verification of the CAPA cycle defined when the pilot is planned.

Data, privacy and security

Demo access requires a short sign-up. The session is kept with an opaque cookie for seven days and tour progress is stored in your own browser.

If you attach files, they are kept in private storage bound to your session: every lookup or download verifies the session and ownership, and other visitors cannot reach them. Use test files only; no real or confidential information is needed.

The detail is in the Privacy, Cookies, Terms and conditions.

How to evaluate it

Discovery · 2 weeks

We interview Quality, Production and the Laboratory, review real batch records and define how the data will come in: recorded in Rigo One, imported from your spreadsheets or your ERP, or through connectors. This is where we take the baseline figures for the four indicators — release time, volume on hold, review hours and cost of poor quality — and deliver a scope report with the success criteria.

Pilot in parallel · 2 weeks · shared risk

One plant, one or two lines, your real batches. The operation carries on unchanged; Rigo One runs alongside it with your roles and your controls. The pilot is paid in two halves: the second only if the capability criteria agreed during discovery are met. We close with a results report against those criteria.

Annual license per plant · From USD 990 per month

A dedicated environment for your company in the LILAB cloud, with support and updates included and unlimited users per plant. The pilot fee is credited in full towards the first-year license; the tiers and the add-ons are in the pricing table.

The data of each client lives in an isolated environment and can be exported in full at any time. The amounts, the add-ons and what every license includes are in the pricing table.

Pricing

No per-seat licenses and no surprises: one monthly amount per plant, billed annually, and a pilot split in two halves: the second is only paid if we deliver what we agreed on. A single screen of the demo shows 11,440 dollars on hold waiting for a decision; the license pays for itself as soon as one batch stops waiting a few days a month.

Discovery + pilot · one month · USD 2,900 (up front) + USD 2,900 (at closing, only if the criteria are met)

One plant, up to two lines, your real batches running alongside your operation. Everything paid is credited in full to the first-year license. If the criteria are not met, the second half is not charged and each side goes its own way.

Initial plant · USD 990 per month · One production line

To start with the line where the waiting hurts most.

Standard plant · USD 1,490 per month · Up to three production lines

The usual step for a mid-sized plant with several lines and a single Quality team.

Additional plants · 30 % discount

Same company, same environment, on the tier that matches each plant.

ERP, LIMS and instrument connectors · Quoted per system

They are defined during the discovery and implemented during the pilot or afterwards.

Capability criteria set during discovery and measured with records the system itself produces

• Every pilot batch ends with a complete record and a logged decision with an owner.
• Rebuilding the history of any pilot batch takes under five minutes, against the time measured during discovery.
• Every pending item has an owner and a next action, with no coordination meetings, verifiable in the log.

The pilot runs in parallel: your operation keeps releasing with its current process, which is why we measure demonstrated capability rather than the impact on your release time yet. That impact is measured during the license.

Included in every license

• Unlimited users per plant
• A dedicated environment in the LILAB cloud
• Support and updates included
• Full export of your data at any time
• Plants with more than three lines: quoted to measure

Prices in US dollars, before taxes. Billed annually.

Rigo One is not an ISO document manager. It runs the release of every batch: controls against specification, evidence, mass balance, deviations and the decision with an owner. That is why it is charged per plant and not per user: the whole plant works on the same batch record.

Results review at six months

Halfway through the first year we review the business-case indicators together — release time, volume on hold and review hours — against the baseline taken during discovery, and agree on what to adjust for the following six months.

Official source of this sheet: https://www.rigo-one.app.