# Rigo One — Batch quality and traceability software

Official source: https://www.rigo-one.app/en
Manufacturer: [LILAB S.A.C.](https://lilab.io), Lima, Perú.
Contact: hola@lilab.io

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.

## What it includes

- **Batch record**: Origin, stages, controls, documents, incidents and decision brought together in one place, with their status always visible.
- **Material genealogy**: Which raw materials went into the batch, and which other batches used them. The scope of an incident stops being guesswork.
- **Controls against specification**: Every result is compared with its range. An out-of-specification value blocks the release, even when the batch record is complete.
- **Customer specifications**: The same batch can conform for one customer and not for another. Every specification keeps its dated versions with the reason for the change, and accepted concessions sit in a catalogue with reference and validity.
- **Deviations with verified closure**: Investigation, containment, correction and verification as distinct steps. Closing a deviation (nonconformity) does not authorize the release.
- **Mass balance**: Opening inventory plus inputs, minus outputs and closing inventory. It tells recorded figures from estimated ones and keeps the difference instead of assigning it to process loss by default.
- **Analytics with sources**: Filters by product, line and control, comparison between lines and export. Every figure lets you open the batch behind it.
- **Ask the batch record**: Ask in plain language for the batches with a given raw material, piece of equipment or line, or with a parameter above a threshold. Every answer arrives with the batches that support it, one click away; the decision stays with the person.
- **Process conditions recorded**: The conditions of the run —temperature, pressure, time, cold chain— are captured by stage during production, with time and owner. They explain how the batch was run; the release is still decided by the laboratory controls.
- **Workflow with owners**: Prepare, submit, review, correct and authorize are separate transitions, each one with author, time, rationale and the version of the workflow configuration.
- **Downloadable batch record**: Production, history, balance and decision in a single file that reproduces the structure of an audit batch record for an internal or external review.

## Who it is for

- **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.

## Decision workflow

1. **Management**: Prioritizes by risk and pending volume.
2. **Production**: Verifies the requirements and authorizes preparation.
3. **Analyst**: Submits records or corrects a measurement.
4. **Reviewer**: Approves the evidence or returns it with an observation.
5. **Authorized approver**: Records the release decision.

Adding a record, approving it and authorizing the release are distinct transitions, each with author, time, grounds and configuration version. A documentary approval does not remove an out-of-specification result or an open deviation.

## Industry profiles

- **Industrial core**: Reception → Transformation → Control → Release. Controls: Process variable, Product characteristic.
- **Oils and fats**: Reception → Refining → Blending → Packing → Release. Controls: Humidity, Acidity, Temperature.
- **Paints and coatings**: Weighing → Dispersion → Adjustment → Filling → Release. Controls: Viscosity, pH, Density.
- **Plastic packaging**: Resin reception → Preparation → Molding → Inspection → Release. Controls: Weight, Thickness, Leaks detected.
- **Cookies and baked goods**: Dosing → Mixing → Baking → Packing → Release. Controls: Final moisture, Pack weight.
- **Meat · Deboning and derivatives**: Carcass reception → Deboning → Conditioning → Derivatives processing → Packing → Dispatch. Controls: Carcass temperature at reception, Deboning room temperature, Meat pH, Derivatives cooking temperature.
- **Aquaculture feed**: Dosing → Extrusion → Drying → Bagging → Release. Controls: Pellet moisture, Pellet durability.
- **Ingredients for animal nutrition**: Reception → Transformation → Separation → Packing → Release. Controls: Final moisture, Declared protein.
- **Fresh fruit and packing**: Reception → Grading → Packaging → Cold storage → Release. Controls: Grading defects, Net box weight.
- **Pharmaceutical · Semi-solid bulk**: Weighing → Mixing → Homogenization → Transfer → Quality review. Controls: Viscosity, pH.

## Guided tours in the demo

- **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.

## Current scope

Available today:
- Release rules that run on the batch data
- Ten industry profiles with their controls and documents
- Workflow by perspectives, with rationale and version
- Mass balance, analytics and a downloadable batch record
- Copilot queries over the loaded batches, with the sources one click away
- Customer specifications with dated versions and a catalogue of concessions

Not yet:
- Integration with ERP, LIMS or MES
- Corporate role-based authentication and electronic signature: defined within the pilot scope
- Shared server-side persistence: your progress is saved in your browser
- Computerized systems validation: the plan is agreed with the client during the pilot
- Formal approval of a specification by your own customer

Scope, integrations and the implementation plan are defined during the evaluation. The demo uses fictitious data and must not be used to decide about real product.

## 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.

### Electronic records: what is here today, and what the pilot closes.

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.

| Requirement | In the demo | In the pilot |
| --- | --- | --- |
| Audit trail: who, what, when and on what grounds | Every transition keeps author, time, rationale and the version of the workflow configuration. | Server-side timestamp and an immutable record. |
| Role-based access control | Five perspectives with actions exclusive to each role: a documentary approval does not release. | Corporate authentication with the roles of your organization. |
| Electronic signature | Not included. | To be defined according to the agreed regulatory scope. |
| Data integrity (ALCOA+) | A correction keeps the original measurement and is recorded as a correction. | Input validation and environment backup. |
| Change control | The workflow configuration is versioned, and every batch keeps the version it was decided under. | Versioned specifications with formal approval. |
| Computerized systems validation | Not included. | 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.

## How to evaluate it

Three steps with defined scope and duration. Your operation does not stop, and from day one you know what you are going to measure.

1. **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.
2. **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.
3. **Annual license per plant** (From USD 990 per month): A dedicated environment for your company in the [LILAB](https://lilab.io) 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.

| Item | Price | Scope |
| --- | --- | --- |
| 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](https://lilab.io) 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.

## FAQ

### Who is Rigo One for?

For quality, production and review teams, and for the people who authorize release in industrial operations that work in batches and need to coordinate controls, evidence and decisions.

### What kind of operations does it cover?

Operations that manufacture in batches or discrete orders and need traceability between raw materials, process, controls and finished product. The demonstration includes ten profiles: oils and fats, paints and coatings, biscuits and baked goods, meat deboning and derivatives, aquaculture feed, animal nutrition ingredients, fresh fruit and packing, semi-solid bulk pharmaceuticals, plastic packaging and a configurable generic core.

### What can I try in the demo?

Five guided tours with fictitious data: unblocking a batch by completing its evidence, resolving a deviation, preparing an audit by reviewing the history and the batch record, finding a pattern by asking the copilot, and releasing for a customer by comparing the batch against two specifications. You can pause, resume and restart each guided tour.

### How long does it take, and do I need to install anything?

Nothing to install: it runs in the browser and registration takes less than a minute. Each guided tour lasts between three and eight minutes, and you can explore on your own without following any of them.

### How does it help resolve a deviation?

The guided tour lets you investigate an out-of-range result, record the correction, review the balance and verify the closure. Closing the deviation does not automatically authorize the release: that decision belongs to the authorized approver.

### Does it connect to our ERP or LIMS?

Not yet. The demonstration works with fictitious data and is not connected to production systems. Integrations are part of the scope defined when a pilot is planned, and they are best reviewed in the discovery conversation.

### Does it comply with ISO 9001, FSSC 22000 or 21 CFR Part 11?

Rigo One organizes quality and food safety evidence the way ISO 9001 and FSSC 22000 ask for it: identification and traceability by batch, control of nonconforming outputs, and recording of nonconformities with their corrective action. Against 21 CFR Part 11 and Annex 11 of the EU GMP, the demo already covers the audit trail with author, time and grounds, the separation of actions by role, keeping the original measurement when a value is corrected, and a versioned workflow configuration; corporate authentication, electronic signature and computerized systems validation are defined within the pilot scope. No software certifies anything by itself: certification depends on your management system.

### What can the quality copilot answer?

Questions about the batches loaded in the demo: which ones share a raw material, which ones went through a given piece of equipment or line, or which ones have a parameter above a threshold. Every answer shows the batches behind it, and you can open them to check it. It is not connected to an external model by default, nor to real data, and it does not decide for anyone: it points to where to look.

### Can I handle different specifications per customer?

In the demo, yes: the same batch is compared against two customer specifications, and you can see which one it conforms to and which one it does not. Every specification keeps its versions with the date, the reason for the change and who published it, and accepted concessions sit in a catalogue with their reference and validity. Formal approval by your own customer and the electronic signature are defined within the pilot scope; the internal release rule does not change.

### Can I attach evidence?

Yes. The demo lets you attach up to three files per action, of up to 5 MB each: PDF, PNG, JPG, Word, Excel, CSV or TXT. The files are linked to your registration session and are not accessible to other visitors. Use test files only.

### What happens to the data I leave when registering?

It is used to enable your access to the demo and to respond to your interest in the product. It is not sold or transferred for commercial purposes. You can request its review or deletion by writing to hola@lilab.io. The details are in the Privacy policy.

### Does the demo change a real operation?

No. The batches and the guided tours use fictitious data. The actions of the exercise are saved in this browser; restarting a guided tour does not delete the attachments already saved. Decisions stay in the hands of the authorized people.

### Who is behind Rigo One?

Rigo One is a product of [LILAB S.A.C.](https://lilab.io), a technology company based in Lima, Perú that designs custom software, digital products and automation for industrial and service operations.

### How does the pilot work?

It starts with a two-week discovery to map your release workflow, your controls and where the data will come from, and that is where we set the capability criteria. A two-week pilot follows, running in parallel with your operation, with one plant and one or two lines. One month in total, from signature to decision. The pilot is paid in two halves of USD 2,900: the first up front and the second at closing, only if the criteria are met. Everything paid is credited in full towards the annual license, which is charged per plant with unlimited users.

### What happens if the pilot does not meet the criteria?

The second half is not charged. What was paid up front covers the two weeks of discovery and the two weeks of pilot support; if you decide to continue later, it is credited in full towards the license all the same.

### How much does Rigo One cost?

The discovery together with the pilot, one month in total, costs USD 2,900 up front and USD 2,900 at closing, conditioned on meeting the agreed capability criteria; everything paid is credited in full towards the first-year license. After that, the license is charged per plant and billed annually: from USD 990 per month for one production line, and USD 1,490 per month for up to three lines, always with unlimited users, with a joint results review at six months against the discovery baseline. Additional plants of the same company get a 30 % discount, and connectors with ERP, LIMS or instruments are quoted per system. Prices are in US dollars and do not include taxes.

### Why is it charged per plant and not per user?

Rigo One is not an ISO document manager: it runs the release of every batch with its controls against specification, its evidence, its mass balance, its deviations and the decision with an owner. For that to work, Quality, Production, the Laboratory and whoever authorizes all work on the same batch record, so charging per seat would penalize exactly what makes the product useful. That is why the price is per plant and users are unlimited.

### How do I evaluate Rigo One for my company?

You can explore the demo through a simple registration, or schedule a discovery conversation with someone from the team. In that meeting we review the workflows, the control points and the needs of your operation. After that conversation, the standard path is a two-week discovery and a two-week pilot running in parallel with your operation.

## Links

- [Product sheet](https://www.rigo-one.app/en/product)
- [Explore the demo](https://www.rigo-one.app/en/register)
- [Book a discovery call with the team](https://calendar.app.google/oqvHZBB7JdhZVr5d8)
- [Terms and conditions](https://www.rigo-one.app/en/terms)
- [Privacy](https://www.rigo-one.app/en/privacy)
- [Cookies](https://www.rigo-one.app/en/cookies)
- [Versión en español](https://www.rigo-one.app/)