·

PLM vs LIMS for Discrete Manufacturing: A Guide for Test Labs

Estelle Lee (Mahbuba Rahman Sraboni)

what-is-a-lims-for-discrete-manufacturing-how-it-differs-from-life-sciences-lims-and-plm

Key Takeaways

  • A LIMS for discrete manufacturing is a laboratory information management system built for hardware test labs, organized by project and test unit where most LIMS are organized by sample and batch;

  • A project-centric LIMS keeps every work request, test unit, and result under its validation project, so each result stays tied to the test unit and revision it ran on;

  • A hardware test lab LIMS has to schedule test units, calibrated workstations, certified operators, shifts, and test sequence together, which a life-sciences LIMS built around sample queues does not model;

  • In the PLM vs LIMS split, PLM owns the product definition and can date a test on a program plan, and the LIMS decides who runs the test, on which workstation, on which shift;

  • A manufacturing LIMS for a test lab keeps the schedule and the test record in one system, and it supports ISO/IEC 17025 by holding evidence of authorized personnel, calibrated equipment, and identified test units.

What Is a LIMS for Discrete Manufacturing? How It Differs from Life-Sciences LIMS and PLM

A LIMS for discrete manufacturing is a laboratory information management system (LIMS) built for test labs that validate hardware products such as vehicles, appliances, and electronics. This project-centric LIMS organizes work by project and test unit and schedules test units, workstations, certified operators, and test sequences together. Life-sciences LIMS and PLM are built around samples and product definitions.

A discrete manufacturer can own a LIMS in its quality control lab and PLM across engineering, and its test lab can still plan every endurance run on a spreadsheet. Neither system holds a record that says this test unit runs on this workstation, with this certified operator, on this shift.

The gap starts with the labels. "LIMS" covers systems built for opposite kinds of lab work, and "PLM" suggests lab coverage that the category was never built to provide. The cost lands on the test floor as idle workstations and completion dates that move without warning.

Choosing a manufacturing LIMS for a test lab starts with knowing which kind of system each label describes. This LIMS for discrete manufacturing guide covers:

  • What a LIMS for discrete manufacturing is and which lab it serves;

  • How a project-centric LIMS differs from a sample-centric one;

  • Why a hardware test lab LIMS cannot run on life-sciences assumptions;

  • Where the PLM vs LIMS boundary sits and whether PLM schedules labs;

  • Why a test lab needs a manufacturing LIMS and a scheduler in one place;

  • How a LIMS for discrete manufacturing supports ISO/IEC 17025;

  • What discrete manufacturers run today in place of a manufacturing LIMS.

A test lab can sit between a company's LIMS and its PLM and still plan on a spreadsheet. QATrax schedules against operator certifications, shifts, and calibrations, so the test it can't staff never gets booked.

Explore QATrax LIMS

LIMS for Discrete Manufacturing at a Glance: What Each System Tracks

A LIMS for discrete manufacturing tracks projects, test units, workstations, certified operators, and test sequence as scheduled records. A life-sciences LIMS tracks samples, and PLM tracks the product definition. The table below compares the three systems by the records a test lab has to schedule against.

What the test lab has to track

Life-sciences LIMS

PLM

LIMS for discrete manufacturing

Organizing record

Sample or batch

Product and its revisions

Project, with work requests and work orders under it

Item under test

Consumed sample with one ID

Part number and revision

Test unit, reused across tests and tied to a revision

Workstation and calibrated equipment

Instrument list and maintenance dates

Not a scheduled resource

Scheduled resource with calibration status

Floating equipment

Rarely modeled

Not a scheduled resource

Scheduled alongside the workstation

Certified operator and shift

User roles and access

Not modeled

Certification per test and workstation, plus shift

Test sequence

Test panel on a sample

Test plan as a document

Sequential and prioritized sequence the schedule enforces

Test type

Run time of an assay

Not modeled

Continuous, attended, or unattended

Rescheduling

Re-queue a sample

Not applicable

One request or the whole lab against every constraint

Compliance frame

FDA 21 CFR Part 11 and GxP

Change control

ISO/IEC 17025

Each column describes what the category is built to hold. For tracking samples and their audit trail, a life-sciences LIMS is the reference system. For controlling the product definition and its revisions, PLM is the reference system.

For scheduling a test lab, the LIMS for discrete manufacturing column is the only one where the workstation, the certified operator, and the test sequence are scheduled records. That difference decides whether your scheduler works inside the system or in a spreadsheet beside it.

When the organizing record is a sample, a 30-test validation program has nowhere to live as one piece of work. QATrax tracks work requests and test units under the project, so results keep their context.

Explore QATrax LIMS

What Is a LIMS for Discrete Manufacturing?

A LIMS for discrete manufacturing is a laboratory information management system (LIMS) that manages the test labs where discrete manufacturers validate hardware designs. It organizes work by project and test unit and schedules the resources each test needs. The same category is also called a project-centric LIMS or a hardware test lab LIMS.

A LIMS for Discrete Manufacturing Is a Project-Centric LIMS

A LIMS for discrete manufacturing is a project-centric LIMS, which means the project is the parent record for every test request, test unit, and result. It serves the test labs where discrete manufacturers validate a design before launch.

Discrete manufacturing produces separate, countable products such as vehicles, aircraft, smartphones, and computers, assembled from parts in a set sequence. Process manufacturing follows a formula and produces goods such as chemicals, food, and beverages that can't be told apart as individual units.

Three names describe this one category. "LIMS for discrete manufacturing" names the industry, "project-centric LIMS" names the data model, and "hardware test lab LIMS" names the lab. Some searchers also use the longer form "manufacturing laboratory information system."

The trait that matters most in a LIMS for discrete manufacturing is that the schedule and the test record live in one system. A test can't be planned without knowing the test unit, the workstation, and the certified operator, and the test's result means little without the same three facts.

What Does Manufacturing LIMS Usually Mean?

A manufacturing LIMS is, on most product pages, quality control software that logs samples from batch production, tests each sample against a specification, and supports the decision to release the batch. The term is broader than this guide's subject, because it covers both sample-based systems and test lab systems.

A sample-based manufacturing LIMS draws its samples from three points in production:

  • Raw materials: The lab samples incoming material on receipt, before the material enters production;

  • In-process batches: The lab samples the product at defined points while the batch is being made;

  • Finished goods: The lab samples the finished batch before it ships.

The batch model fits process manufacturers well, because the batch is the unit of work and the same test panel repeats on every batch. Statistical checks on repeated measurements are a central feature of a manufacturing LIMS of this kind.

The batch model also fits production quality control inside a discrete manufacturer, where incoming parts and finished lots get inspected against a drawing or specification. A sample-based manufacturing LIMS has no natural place for a prototype, a test program, or a schedule of workstations and certified operators.

Which Manufacturing LIMS Fits the Quality Control Lab or Test Lab?

The quality control lab needs a sample-centric manufacturing LIMS, and the test lab needs a project-centric one. Most discrete manufacturers run both kinds of lab. The quality control lab checks that parts and lots meet specification, and the test lab validates and qualifies a design before it goes to market.

The quality control lab and the test lab differ in three ways that shape the manufacturing LIMS each one needs:

  • Repetition versus programs: The quality control lab runs the same panel on many lots, while the test lab runs a unique set of tests on a few test units for each program;

  • Duration: A quality control measurement often takes minutes, while a test lab runs endurance runs that hold a workstation for days;

  • Output: The quality control lab produces a pass or fail on a lot, while the test lab produces evidence for a qualification package.

The quality control lab and the test lab also answer to different parts of the company. In the manufacturers we work with, the quality control lab answers to production and release, and the test lab answers to engineering programs with launch dates.

In labs we've seen, the manufacturing LIMS bought for the quality control lab often gets offered to the test lab as well. The test lab tries to enter its programs as samples, finds no place for the schedule, and goes back to spreadsheets within months.

A sample-based manufacturing LIMS can serve the quality control lab well and still leave the test lab without a system. The test lab is the lab a LIMS for discrete manufacturing is built for, and it is where the prototypes, the endurance runs, and the certified operators are.

A quality control lab repeats one panel on many lots, while a test lab runs a different program each time. QATrax supports sequential and prioritized test sequences, so each program runs in its required order.

Explore QATrax LIMS

Project-Centric LIMS vs. Sample-Centric LIMS by Parent Record

A project-centric LIMS makes the project the parent record, and a sample-centric LIMS makes the sample the parent record. Every other record hangs from that parent. The choice decides which questions the system can answer months later, such as which results belong to one program and one revision.

What Does a Sample-Centric LIMS Organize?

A sample-centric LIMS is a LIMS that organizes every record under the sample. The lab logs a sample on receipt, assigns tests to the sample, attaches results, and disposes of the sample when testing ends.

The sample-centric structure answers three questions quickly: where a sample is, what was tested on it, and whether it passed. For a lab that receives hundreds of similar samples a week, those are the questions that matter.

A sample-centric LIMS also assumes the sample is consumed or discarded. Once the sample's tests finish, the record closes, and nothing later depends on that sample's condition.

Many sample-centric LIMS products carry a project field, so a lab can tag samples with a program name. The sample remains the parent record, though, and the project is a label on the sample.

A validation program doesn't fit under a sample. A program of 30 tests on three test units that depend on each other becomes 30 unrelated entries in a sample-centric LIMS, and the dependencies between the tests live in someone's memory.

What Does a Project-Centric LIMS Organize?

A project-centric LIMS is a LIMS that organizes every record under the project. The record has five levels, and each level inherits context from the level above it:

  1. Project: The validation or qualification program, with its design review dates;

  2. Work request: What a requestor asks the lab to test, with the information needed to start;

  3. Work order: The work the lab schedules and a certified operator carries out;

  4. Test unit: The specific build under test, at a specific revision;

  5. Test and result: What ran, on which workstation, by which certified operator, and what it showed.

A requestor enters the program context once, at the work request. The certified operator who opens the work order sees the test unit, the test method, and the test sequence without asking anyone.

Published research on test lab scheduling models the work the same way. In A Local Search Framework for Industrial Test Laboratory Scheduling (2021), Annals of Operations Research describes three schedules from one industrial test lab that each held 59 to 74 projects divided into 223 to 297 jobs.

The "jobs" in the Annals of Operations Research study are groups of tests the lab schedules together, and each group belongs to a project. The study covers a single lab, and it shows an industrial test lab's workload grouping under projects without any software vendor involved.

A project-centric LIMS lets a test lab answer program-level questions directly. Your scheduler can see every open test on a program, every test a test unit has been through, and every result due before a design review.

How a Test Unit Differs from a Sample in a Hardware Test Lab LIMS

A test unit is the specific build of a product that a test lab tests, and it differs from a lab sample in four ways. A hardware test lab LIMS has to model all four differences for the test unit, which some labs call a sample or DUT:

  • Reuse: One test unit passes through several tests, so its history and physical condition carry forward from test to test;

  • Identity: A test unit is a specific build at a specific revision, and a result means nothing without that revision. This is the foundation of test data traceability;

  • Scarcity: A program may have only three prototypes, so the test unit is a scheduled resource alongside the workstation and the certified operator;

  • Destruction: A destructive test ends the test unit, so the destructive test has to run last in that unit's test sequence.

A consumed sample has none of these four traits. A sample gets one ID, one set of tests, and a disposal date.

The reports differ too. A sample lab issues a result or certificate for each sample, and a hardware test lab issues an engineering test report that covers the test unit, the method, the equipment, and what the certified operator observed.

A hardware test lab LIMS that treats a prototype as a sample loses the test unit's history at the first retest. The lab then can't say which tests a rebuilt test unit has already survived.

Worked Example: One Validation Project in a Project-Centric LIMS

A project-centric LIMS keeps a validation project together by holding its test units, its test sequence, and its design review date in one record. The hypothetical scenario that follows shows the difference from a sample-centric view.

Hypothetical scenario. A controller validation project has three test units, eight tests, and a design review date. One of the eight tests is destructive.

In a sample-centric view, the lab holds eight unrelated entries. Nothing in the sample-centric record says that the destructive test has to run last on its test unit, or that two of the tests have to run on the same test unit in order.

In a project-centric LIMS, the lab holds one project. The project record shows the test sequence, each test unit's path through its tests, and the design review date the program is working toward.

Halfway through the scenario, unit 2 is rebuilt at a new revision. The project-centric LIMS shows which of the completed results ran on the old revision of unit 2, so the lab knows which results still count.

The project-centric LIMS also shows the date at risk. If the rebuilt unit 2 has to repeat two tests before the destructive test can run, the scheduler can see whether the design review date still holds.

Rebuilding a prototype at a new revision can leave finished results with no record of their build. QATrax ties each result to its project and work request, so there is a record to answer from.

Explore QATrax LIMS

Why a Hardware Test Lab LIMS Can't Run on Life-Sciences LIMS Logic

A hardware test lab LIMS is a LIMS that schedules and records physical tests on hardware prototypes. It can't run on life-sciences LIMS logic because that logic rests on four assumptions: sample batches, interchangeable analysts, FDA record rules, and a sample queue. None of the four holds on a hardware test floor.

Who Buys LIMS? Life-Sciences LIMS Buyers Lead the Market

Life-sciences labs are the largest group of LIMS buyers, according to market research, and LIMS grew up as a category in labs that manage regulated samples. In our experience, the best-known LIMS products were built around sample workflows in pharmaceutical, biotech, and clinical labs.

One analyst estimate puts a number on that lead. According to Grand View Research's Laboratory Information Management System Market Report, 2026-2033 (2026), life science companies accounted for an estimated 40.7% of LIMS market revenue in 2025, and manufacturing does not appear among the report's named end-use segments.

The other segments the Grand View Research report names are contract research organizations, the chemical industry, food and beverage and agriculture, environmental testing labs, and petrochemical refineries and oil and gas. All of those segments test samples of a material.

Software follows its largest buyers. The default features, the vocabulary, and the compliance tooling of a life-sciences LIMS all reflect sample labs, and a hardware test lab LIMS has to start from different defaults.

Life-Sciences LIMS Assumption 1: Work Arrives as Sample Batches

A life-sciences LIMS assumes that work arrives as samples and that the same tests repeat on batch after batch. For an assay lab, the batch assumption is correct, and it lets a life-sciences LIMS log a new sample in seconds.

On a hardware test floor, work arrives as a test request for a program. Each program brings its own mix of tests, and the item under test is a prototype that may show up late or at a different revision than planned.

The intake step also carries more risk in a test lab. In the labs we work with, test requests often arrive without all the information the lab needs to start, such as the test method, the acceptance criteria, or the test unit's configuration.

A life-sciences LIMS that assumes repeatable batches has no step for catching an incomplete test request. The gap surfaces on the day the test was supposed to start, when the workstation is reserved and the certified operator has nothing to run.

Life-Sciences LIMS Assumption 2: Analysts Are Interchangeable

A life-sciences LIMS assumes that an instrument is available when the sample queue reaches it and that any trained analyst can run the panel. User roles in a life-sciences LIMS control who can log in and approve, and the roles say little about who can run which test.

A hardware test lab LIMS can't make either assumption. A workstation, such as an environmental chamber, carries semi-permanent calibrated equipment, floating equipment has to arrive for the same hours, and both have calibration windows that close on a date.

Certified operators are specific too. The certified operator who is cleared for workstations 3 and 7 has no certification for workstation 5, so two certified operators on the same shift are not substitutes for each other.

Shifts add the last limit. If the only certified operator for a test works days, the slot that looks open on Saturday can't be used, and a life-sciences LIMS that only checks the instrument will book the slot anyway.

Life-Sciences LIMS Assumption 3: Compliance Means FDA 21 CFR Part 11

A life-sciences LIMS assumes that the FDA sets its compliance frame. FDA 21 CFR Part 11 sets the criteria under which the FDA treats electronic records and electronic signatures as trustworthy and generally equivalent to paper records.

The FDA 21 CFR Part 11 frame fits a lab whose records go to the FDA. A life-sciences LIMS is built to produce those records, and that is the right design for its buyers.

A manufacturing test lab is typically held to a different frame. ISO/IEC 17025 sets requirements for a testing lab's competence, and customers often add requirements of their own.

FDA 21 CFR Part 11 and ISO/IEC 17025 ask for different evidence. A hardware test lab LIMS has to show who was authorized to run a test, whether the equipment was in calibration, and which test unit the result belongs to.

A discrete manufacturer whose products are FDA-regulated may need both frames, and that decision belongs to its quality and regulatory teams. For a hardware test lab LIMS, the evidence the lab is asked for starts with operator competence, equipment calibration, and test unit identification.

Life-Sciences LIMS Assumption 4: The Schedule Is a Sample Queue

A life-sciences LIMS assumes that scheduling means ordering samples for an instrument or booking dates to pull samples from a study. A sample queue works when each test is short and each sample is independent.

Tests in a hardware test lab are neither short nor independent. Three test types break the sample queue model:

  • Continuous tests: A 40-hour continuous test can't pause across a shift change, so the test needs certified coverage for the whole run;

  • Unattended tests: An unattended test can run over a weekend, which frees certified operators and still holds the workstation;

  • Destructive tests: A destructive test has to run last on its test unit, whatever its priority.

A life-sciences LIMS with no model for test type or test sequence leaves the lab one fallback, and that fallback is first-come-first-served. The scheduler then carries every exception in a spreadsheet, and a hardware test lab LIMS exists to take that spreadsheet's place.

A system that treats every analyst as interchangeable will book a test onto a shift where nobody is certified. QATrax enforces operator certifications against test method profiles, so only certified operators get scheduled.

Book a Demo

What Does a Hardware Test Lab LIMS Have to Schedule at Once?

A hardware test lab LIMS has to schedule five conditions at once: the test unit, the workstation and its equipment, the certified operator, the test sequence, and the test type. All five have to be true at the same moment before a test can start, so the LIMS treats each one as a scheduled record.

Manufacturing LIMS Scheduling Starts with Units and Workstations

Manufacturing LIMS scheduling for a test lab starts with physical resources. Three physical resources have to be free for the same hours:

  • The test unit: The test unit has to have arrived and be in a usable state, at the right revision;

  • The workstation: The workstation has to be free, and its semi-permanent calibrated equipment has to be inside its calibration window;

  • Floating equipment: Any device the test borrows has to be free for the same hours and in calibration.

Calibration turns a free workstation into an unusable one. If a workstation's calibration window closes on Friday, a test that slips from Thursday to Monday loses its slot even though the calendar shows the workstation open.

Floating equipment adds a second check. A device shared between workstations may already be reserved at another workstation for the same hours, so a manufacturing LIMS has to schedule the device alongside the workstation.

A manufacturing LIMS for a test lab therefore holds the calibration due date on the equipment record and checks the date at booking. The full set of rules is the subject of test lab scheduling, and the equipment rule alone removes a common cause of tests that can't be defended later.

Certified Operators and Shifts in a Hardware Test Lab LIMS

Certified operators and shifts limit a schedule more than most calendars show. Certification is tied to a test method and a workstation, so a hardware test lab LIMS has to match each test to the operators certified for it.

Shift coverage decides whether an attended test can run at all. A test that needs a certified operator present for 12 hours needs certified coverage across more than one shift, and a gap on nights stops the test.

Certifications also expire. A hardware test lab LIMS that holds each expiry date can stop booking a certified operator onto a test after the certification lapses, and it can show the lab manager which renewals are coming due.

The operator record in a hardware test lab LIMS needs three fields: the certifications held, the date each certification expires, and the shift pattern. With those fields in place, test lab resource management stops depending on what the scheduler remembers about each certified operator.

Test Sequence and Test Type in a Project-Centric LIMS

Test sequence and test type limit which tests a project-centric LIMS can move. Some sequences are fixed by physics, such as a destructive test that has to run last, and some are fixed by priority, such as a regulatory test that gates a launch in one region.

A project-centric LIMS handles both kinds as sequential and prioritized test sequences inside the project. The schedule can then move a test within the limits of its test sequence and refuse a move that breaks the sequence.

Test type sets how a test occupies its resources. A continuous test runs without a pause, a segmented test can be split to fit operator shifts, an attended test needs a certified operator throughout, and an unattended test can run with nobody present.

Test sequence and test type have to live in the same record as the resources. A 40-hour continuous test that starts on Thursday morning ends on Friday night, and only a project-centric LIMS that knows the test type will check for certified coverage on both nights.

How Does a Hardware Test Lab LIMS Reschedule a Late Test Unit?

A hardware test lab LIMS reschedules a late test unit by checking every constraint again and showing each new completion date the same day. Rescheduling is the larger part of scheduling work. In the labs we work with, rescheduling takes far more of the scheduler's week than building the first plan.

A late test unit shows how far one change travels. A test unit arrives two days late, the workstation it needed is booked for the next three weeks, and the only certified operator for that test works the day shift.

The completion date moves by weeks, and the tests queued behind the late test unit move with it. Nobody above the lab sees the ripple until a requestor asks why a date changed.

An urgent test request causes the same ripple from the other direction. One high-priority test request inserted on Monday displaces the tests that held those slots, and each displaced test has its own certified operator, calibration window, and test sequence to satisfy.

A scheduler working by hand has to rebuild the week one test at a time. A hardware test lab LIMS handles test lab rescheduling against every constraint at once, for one test request or for the whole lab.

If a test unit arrives two days late, the completion date can move three weeks without warning. QATrax reschedules one request or the whole lab in one move, so the new date shows immediately.

Explore QATrax LIMS

PLM vs. LIMS: Where Does PLM Stop and Lab Scheduling Begin?

In the PLM vs LIMS split, PLM stops at the product record, and test lab scheduling begins where a test needs a workstation, a certified operator, and a shift. PLM can date a test on a program plan. The LIMS decides when and how the lab can run it.

PLM vs. LIMS: What PLM Owns in the Product Definition

Product lifecycle management (PLM) is the system of record for what a product is, across every revision. In the PLM vs LIMS split, PLM owns the product definition and the history of how the definition changed.

Five kinds of record live in PLM:

  • Requirements: What the product has to do and the criteria for accepting it;

  • Bill of materials: The parts that make up the product, at each revision;

  • Specifications and drawings: The released definition that engineering controls;

  • Change orders: Each proposed change, with its approvals;

  • Test and validation information: The test plan and the evidence attached to the product.

PLM is also a large, established investment. According to CIMdata's CIMdata 2026 Executive PLM Market Report (2026), the PLM market as CIMdata defines it reached an estimated $88.3 billion in 2025, a 9.9% increase over 2024.

CIMdata's definition of the PLM market includes design tools such as MCAD, CAM, and simulation software. The scale still explains why "we already have PLM" is a credible first answer when a test lab asks for its own system.

Does PLM Schedule Labs? PLM vs. LIMS at Program and Lab Level

PLM can place a test on a program plan with a date and an owner, and PLM is not built to schedule the lab that runs the test. The PLM vs LIMS difference in scheduling is one of level.

Test scheduling happens at two levels:

  • Program level: The program plan says a test is due before the design review and names the engineer who owns it;

  • Lab level: The lab schedule says which test unit runs on which workstation, with which certified operator, on which shift.

PLM works at the program level. PLM suites offer test and verification management functions that tie requirements to tests and track whether each requirement has been verified, which is program-level work.

The lab level needs records that a product definition doesn't model. Those records include the certified operator's shift, the workstation's calibration window, floating equipment, and the test type.

In the labs we work with, the result is predictable. PLM holds the test plan as a document, and a spreadsheet beside PLM holds the calendar of who runs what and when.

PLM vs. LIMS by What Each Holds About a Single Test

One test produces facts that belong to two systems. The table below compares PLM vs LIMS by the facts each system holds about a single test.

Fact about one test

PLM

LIMS

Requirement and acceptance criteria

Holds as the reference

Receives a copy on the work request

Revision under test

Holds the released revision

Holds the revision of the test unit that ran

Which test unit

Not held

Held, with the test unit's history

Workstation and equipment

Not held

Held, with calibration status

Certified operator

Not held

Held, with certification

Planned and actual dates

Planned date on the program plan

Planned and actual dates on the schedule

Result and report

Receives as evidence

Produces

For "what was required, and did it pass," PLM is the reference. For "who ran it, on which equipment, when, and what moved as a result," the LIMS is the reference.

The rows in the middle of the PLM vs LIMS table are the lab's own facts. PLM has no reason to hold those facts, and a test lab can't schedule without them.

How Do PLM and a Manufacturing LIMS Hand Off Requirements?

PLM and a manufacturing LIMS hand off in two directions. Requirements and the test plan come down from the product record into the work request, and results and reports go back up as evidence.

The downward handoff matters most at the work request. In the labs we work with, a test request that carries the requirement, the acceptance criteria, and the released revision from the product record is far less likely to stall on missing information.

The upward handoff closes the loop for engineering. When the manufacturing LIMS returns the result and the report against the requirement, the engineer sees the outcome in PLM and doesn't need access to the lab's schedule.

Two records should stay where they are. The schedule stays in the manufacturing LIMS, because the schedule changes daily and depends on lab resources, and the product definition stays in PLM, because engineering controls it.

PLM vs. LIMS After an Engineering Change: Which Answers What?

After an engineering change, PLM answers what changed and which requirements the change touches. The LIMS answers which completed tests ran on the old revision of the affected test unit, and which scheduled tests now need a different test unit.

Neither system can answer the other's half. PLM doesn't know which physical test unit sat on which workstation last month, and the LIMS doesn't decide which requirements a design change affects.

The scheduled half is easy to overlook. Tests still on the calendar for the old revision keep a workstation and a certified operator reserved until someone cancels them, and that capacity sits idle if the engineering change doesn't reach the lab's schedule.

A lab with both PLM and LIMS records can separate the results that still stand from the tests that need a re-run. A lab with only PLM reconstructs that list from memory and email, and re-runs the tests it can't confidently defend.

PLM can say a test is due before the design review, while the lab still needs a workstation and a certified operator. QATrax schedules those resources together, so the due date has a slot.

Explore QATrax LIMS

Manufacturing LIMS or Lab Scheduler? A Test Lab Needs Both

A test lab needs both a manufacturing LIMS and a lab scheduler, in one system, because each half is incomplete alone. A lab scheduler without the test record can't explain its bookings. A manufacturing LIMS without the schedule can't say when any test will run.

What Does a Lab Scheduler Without a Manufacturing LIMS Leave Out?

A lab scheduler without a manufacturing LIMS leaves out the work behind each booking. A lab scheduler or equipment booking tool knows that a slot is taken and knows little about why.

Four records are missing when a lab scheduler runs without a manufacturing LIMS:

  • The work request: The information the lab needs to start the test, including the test method and acceptance criteria;

  • The test unit's history: What the test unit has already been through, and at which revision;

  • The result: What the test showed;

  • The report: The document that goes back to the requestor.

The four missing records then live somewhere else, usually in spreadsheets and shared folders. The calendar says a workstation was booked on Tuesday, and a separate file says what ran there and what it showed.

An incomplete work request is the first casualty. A booking tool will reserve a workstation for a test whose method or acceptance criteria nobody has supplied, and the gap surfaces when the certified operator arrives to run the test.

What Does a Manufacturing LIMS Without a Scheduler Leave Out?

A manufacturing LIMS without a scheduler leaves out when any test can run. It knows what was requested and what the result was, and it holds no model of workstations, certified operators, or shifts as scheduled resources.

The schedule then gets built by a person, usually in a spreadsheet. That scheduler carries the certifications, the calibration dates, and the test sequences in memory, and checks each one by hand.

Research on one industrial test lab measured what a hand-built schedule misses. In Investigating Constraint Programming and Hybrid Methods for Real World Industrial Test Laboratory Scheduling (2024), the Journal of Scheduling reports that a manually built schedule from one industrial test lab omitted 90 required resource assignments, 88 for employees and 2 for equipment.

The Journal of Scheduling figure comes from a single lab, so it shows the kind of gap a manual schedule leaves and says nothing about the average lab. Each missing assignment is a test on the plan with nobody named to run it.

What Breaks When the Schedule and Manufacturing LIMS Live Apart?

Three failures follow when the schedule and the manufacturing LIMS record live in different systems:

  • A failed test needs a re-run: The record changes first, and the schedule finds out later, after the next open slot has gone to another test;

  • A reschedule crosses a calibration due date: The schedule changes first, and the record finds out at the audit, when the result turns out to rest on out-of-calibration equipment;

  • Planned versus actual can't be measured: The plan sits in one system and the actual dates sit in another, so nobody can compare them without a manual export.

The planned versus actual failure matters most to engineering leadership. Without planned and actual dates and actual test durations in one place, test lab capacity planning runs on estimates.

All three failures share one root. A change in one system is invisible to the other system until a scheduler carries it across, and the lab pays for the delay with a re-run or a slipped completion date.

A test lab that runs the schedule and the manufacturing LIMS in one system sees each change once. The failed test, its re-run, and the tests it displaced all appear on the same schedule as soon as the result is recorded.

A Manufacturing LIMS with Scheduling Handles a Monday Reschedule

A manufacturing LIMS with built-in scheduling handles an urgent Monday test request in one place, because the constraints and the test records sit in the same system. The hypothetical scenario that follows walks through one such Monday.

Hypothetical scenario. An urgent test request lands on Monday morning in a lab that runs a manufacturing LIMS with built-in scheduling. The week already holds three constraints:

  • A continuous test: A 40-hour continuous test started Monday at 6:00 a.m. and ends Tuesday at 10:00 p.m.;

  • A certified operator: The operator who can run the urgent test is certified on two of the lab's five workstations;

  • A calibration window: The calibration window on one of those two workstations closes on Friday.

The scheduler sees all three constraints in one place. The continuous test can't move, the certified operator limits the urgent test to two workstations, and any test pushed past Friday on the workstation with the closing calibration window needs a different slot.

The scheduler places the urgent test, and the manufacturing LIMS recalculates the completion dates of the tests it displaced. Nobody in the scenario calls a status meeting, because the scheduler works from recorded facts and the displaced requestors find out the same morning.

Keeping the schedule in one tool and the test record in another makes a scheduler reconcile both by hand. QATrax holds work requests, the schedule, and results together, so the scheduler updates one record.

Book a Demo

How Does a LIMS for Discrete Manufacturing Support ISO/IEC 17025?

A LIMS for discrete manufacturing supports ISO/IEC 17025 by holding the records the standard's clauses ask for. ISO/IEC 17025:2017 sets general requirements for the competence of testing and calibration labs. Five clauses map directly to records a manufacturing test lab keeps.

The table below pairs each of those five ISO/IEC 17025 clauses with the record a manufacturing test lab keeps for it. Each row was checked against the text of ISO/IEC 17025:2017.

Clause

What the standard asks for (paraphrased)

Record a manufacturing test lab keeps

6.2 Personnel

Documented competence requirements; personnel authorized for specific lab activities; records kept

Operator certification per test method and workstation, with dates

6.4 Equipment

Calibration where accuracy affects results; a calibration program; visible status; out-of-service handling; equipment records

Calibration status and due date on every workstation and device

7.4 Handling of test items

Unambiguous identification kept for the life of the item in the lab; deviations recorded on receipt

Test unit ID, revision, and condition on arrival

7.5 Technical records

Enough detail to repeat the work; who did it and when; traceable amendments

Work order history: operator, equipment, dates, and changes

7.11 Control of data and information management

The lab's information management system validated before use, protected, and changes controlled

Validation and change records for the LIMS itself

Which Manufacturing Test Labs Work to ISO/IEC 17025 in 2026?

Accredited testing and calibration labs work to ISO/IEC 17025, and many internal manufacturing test labs follow it without holding accreditation. ISO/IEC 17025 is the international standard that labs use to show they are competent and produce valid results. As of November 2026, the current edition is ISO/IEC 17025:2017, which ISO reviewed and confirmed in 2023.

Accredited labs are numerous. According to ILAC's Facts & Figures (2024), accreditation bodies that signed the ILAC Mutual Recognition Arrangement had accredited more than 114,600 labs in 2024.

The ILAC count covers every kind of accredited lab, including medical labs assessed against a different standard. Manufacturing test labs are one part of that total.

Internal manufacturing test labs often follow ISO/IEC 17025 because their customers or programs expect evidence of the same quality. Automotive customers often set lab requirements of their own on top of the standard.

Clauses 6.2 and 6.4 in a Manufacturing LIMS: Personnel and Equipment

Clauses 6.2 and 6.4 of ISO/IEC 17025 cover personnel and equipment, and a manufacturing LIMS holds the records for both. Clause 6.2 asks the lab to document the competence each function requires, to authorize personnel for specific lab activities, and to keep records of both.

Clause 6.4 asks for four equipment controls that a manufacturing LIMS can hold on the equipment record:

  • Calibration: Measuring equipment is calibrated where its accuracy affects the validity of results;

  • Calibration program: The lab maintains a calibration program and reviews and adjusts it;

  • Status: A label or code makes each device's calibration status easy to see;

  • Out-of-service handling: Equipment that is faulty or gives questionable results is isolated from use.

Clauses 6.2 and 6.4 both describe conditions that have to be true at the moment a test starts. A schedule that ignores certifications and calibration status plans tests the lab can't defend afterward.

A manufacturing LIMS that checks certifications and calibration status at booking closes that gap. The test only reaches the plan if an authorized operator and in-calibration equipment are available for it.

Clauses 7.4 and 7.5 in a Project-Centric LIMS: IDs and Records

Clauses 7.4 and 7.5 of ISO/IEC 17025 cover test item identification and technical records, and a project-centric LIMS meets both through its ordinary structure. Clause 7.4 asks for an identification system that keeps test items from being confused, retained for as long as the lab holds the item, and for a record of any deviation found on receipt.

Clause 7.5 asks for technical records detailed enough to repeat the test as closely as possible. The records name the personnel responsible, and any amendment can be traced back to the original entry.

In a project-centric LIMS, the test unit's ID, its revision, and its condition on arrival sit on the unit record. The certified operator, the equipment, and the dates sit on the work order.

Nobody has to assemble the clause 7.4 and 7.5 evidence before an assessment. A project-centric LIMS produces the evidence as a side effect of scheduling and running the test.

Clause 7.11: What ISO/IEC 17025 Asks of the Manufacturing LIMS

Clause 7.11 of ISO/IEC 17025 asks that the lab's information management system be validated, change-controlled, and protected. The clause covers the control of data and information management, and it names laboratory information management systems directly.

Clause 7.11 sets three requirements for the manufacturing LIMS itself:

  • Validation: The system is validated for its functions before the lab introduces it;

  • Change control: Changes to the system are authorized, documented, and validated before they go live;

  • Protection: The system is protected from unauthorized access, tampering, and loss.

A note in clause 7.11 says commercial off-the-shelf software in general use within its designed application range can be considered sufficiently validated. A lab that configures or modifies a manufacturing LIMS still has to control and record those changes.

Can a LIMS for Discrete Manufacturing Earn Accreditation?

A LIMS for discrete manufacturing can't earn accreditation, and it can hold the evidence an accreditation assessment asks for. Accreditation comes from an accreditation body after an assessment of the lab.

A LIMS for discrete manufacturing makes the ISO/IEC 17025 evidence retrievable. An assessor's question about one test, one certified operator, or one calibration becomes a search on a record the lab already has.

Software records what the lab does and leaves the lab's procedures, training, and judgment to the lab. On assessment day, the difference a LIMS for discrete manufacturing makes is that the lab manager pulls up a work order while the assessor waits, with no search through binders.

An assessor's question about one device's calibration on one test date can cost a lab a day of digging. QATrax tracks calibration status, location, and maintenance for lab equipment, so the record is on hand.

Explore QATrax LIMS

What Do Manufacturers Run in Place of a Manufacturing LIMS in 2026?

As of November 2026, discrete manufacturers run test labs on seven kinds of setup, and six of them stand in for a manufacturing LIMS: spreadsheets, PLM with test records attached, a life-sciences LIMS, cloud tools for small labs, in-house systems, and booking point tools. The seventh is a project-centric LIMS built for discrete manufacturing.

The table below compares the seven setups by what each tracks well, where the schedule ends up, and which lab each setup fits. The fit column reflects our experience with test labs.

Setup

What it tracks well

Where the schedule lives

Best fit

Spreadsheets and email

The test plan as a list

In one person's file and memory

A small lab with one scheduler and few programs

PLM with test records attached

Requirements, revisions, results as documents

In a spreadsheet beside PLM

A lab that needs requirement evidence and schedules little

Life-sciences or general-purpose LIMS

Samples, results, audit trail

In a sample queue or outside the system

The quality control lab

Cloud tools for small labs

Test requests, basic equipment and calibration

In first-available booking

A single-shift lab with a handful of workstations

In-house system

Whatever it was scoped for

Usually out of scope

A lab with one stable process and IT capacity to maintain it

Scheduling or booking point tool

Slots on equipment

In the tool, without the test record

A lab whose only problem is double-booked equipment

Project-centric LIMS for discrete manufacturing

Projects, test units, resources, results

In the same system as the record

A multi-program test lab with certified operators and shifts

For a test lab whose completion dates slip because of certifications, shifts, or late test units, only the seventh setup keeps the schedule and the record in one system. The other six can each be the right choice for the lab named in the fit column.

Spreadsheets and Email Stand In for a Manufacturing LIMS

Spreadsheets and email threads are the stand-in for a manufacturing LIMS that we meet most often in test labs. A spreadsheet holds a test plan well as a list: which tests, on which test units, in roughly what order.

Spreadsheets also dominate manufacturing data work in general. The Manufacturing Leadership Council's Survey: In Manufacturing Data We Trust—Mostly (2026) found that 76% of surveyed manufacturers use Microsoft Excel to analyze manufacturing data.

The Manufacturing Leadership Council survey covers manufacturing data broadly, and test labs are one small part of that picture. The spreadsheet habit the survey describes is the same habit a test lab starts from.

A spreadsheet stops where scheduling starts. It holds no certifications, no calibration dates, and no test sequence logic, and a test unit's place in its test sequence gets lost as the file is edited, a pattern covered in detail in LIMS vs spreadsheets.

PLM with Test Records Covers Half of PLM vs. LIMS

PLM with test records attached covers the product half of PLM vs LIMS and leaves the lab half outside. Requirements, revisions, and results as documents all sit in PLM, tied to the right part number.

This PLM setup is behind a common executive objection. Leadership often tells us the labs are doing fine with spreadsheets and PLM.

The calendar of workstations and certified operators lives in a spreadsheet next to PLM, and the scheduler maintains it by hand. A late test unit or an urgent test request forces a reschedule, and the spreadsheet has no link to the test plan in PLM, so the two drift apart.

Leadership sees the product record in PLM and assumes the lab is covered. The lab manager sees the spreadsheet and knows where the completion dates come from.

Life-Sciences and General-Purpose LIMS Fit the Quality Control Lab

A life-sciences or general-purpose LIMS fits the quality control lab, where samples and lots are the unit of work. Such a LIMS is often already licensed somewhere in the company, so extending it to the test lab looks like the low-cost path.

The test lab has to bend its projects into samples to use a life-sciences LIMS. The schedule ends up in a sample queue or outside the system altogether.

Configuration can stretch a general-purpose LIMS toward test lab work. In our experience, that effort goes into reworking workflows the lab then has to maintain, and scheduling by certified operator, shift, and test type still sits outside the system.

Cloud Manufacturing LIMS Tools Are Built for Small Labs

Cloud manufacturing LIMS tools aimed at small test labs handle several tasks well. They track test requests, keep a basic equipment list with calibration dates, and are quick to start using.

Scheduling in these cloud manufacturing LIMS tools tends to place each test in the first available slot. First-available booking works for a small lab on a single shift with a handful of workstations.

In our experience, a multi-shift or multi-site test lab outgrows first-available booking once certifications, test sequence, and test type have to be checked together. A lab that plans to add shifts, sites, or long endurance runs should try the scheduler against those cases before committing to it.

In-House Systems Rebuild What a Hardware Test Lab LIMS Schedules

An in-house system has to rebuild every constraint a hardware test lab LIMS already schedules. The in-house route looks attractive because internal IT can match the lab's current process exactly and start from the lab's own spreadsheets.

The depth of the scheduling problem appears later. Operator certifications, shifts, calibration windows, and continuous tests each become a requirement that IT has to build and then maintain.

Scheduling is usually left out of scope for the first version. The in-house system then becomes a record of test requests and results, and the calendar stays in a spreadsheet.

Maintenance is the other cost of an in-house system. Each new test type, workstation, or certification rule becomes a change request to IT, and the lab waits in the same queue as every other internal project.

Booking Point Tools Lack the Manufacturing LIMS Record

Scheduling and equipment booking point tools solve resource coordination and lack the manufacturing LIMS record. A booking point tool shows who has reserved which equipment and when, and it carries no test request, no workflow, and no reporting.

Booking point tools fit a lab whose only problem is double-booked equipment. They do less for a lab whose completion dates slip because of certifications, test sequence, or late test units, since none of those appears on a booking.

A lab on a booking point tool also loses planned versus actual reporting. A booking shows when equipment was reserved, and it can't show how long the test took or why the test moved.

A Project-Centric LIMS Keeps the Schedule and Record Together

A project-centric LIMS built for discrete manufacturing holds projects, test units, scheduled resources, and results in one system. It is the seventh setup and the purpose-built category.

The project-centric LIMS differs from the other six setups in where the schedule lives. Because projects, test units, and scheduled resources share a record, a reschedule and a result both update the same work order, and your scheduler stops maintaining a second file.

When the test plan lives in a spreadsheet beside PLM, the schedule lives in one person's head. TraxStar imports existing Excel test plans during implementation, so nothing is keyed twice.

Book a Demo

How to Evaluate a LIMS for Discrete Manufacturing in 2026

Evaluate a LIMS for discrete manufacturing with eight questions about your own lab, two each on the data model, scheduling, records, and adoption. We call the set the Eight-Question LIMS Fit Check. Feature lists look alike across every setup, and these eight questions separate a project-centric LIMS from the alternatives.

Does the Project-Centric LIMS Keep a Program Together?

A project-centric LIMS keeps a program together if it passes two data-model questions in the Eight-Question LIMS Fit Check:

  • Program view: Can the system show every open test, test unit, and result under one program without a custom report? If the answer depends on exporting to a spreadsheet, the project is a label and the parent record is something else. Try it with a program that has at least three test units and one destructive test;

  • Revision history: When a test unit is rebuilt at a new revision, does its earlier history stay attached to the old revision? A project-centric LIMS should keep both, so results from the old build aren't mistaken for results on the new one. Ask how the system shows a test unit that has been rebuilt twice.

A lab that can answer yes to both data-model questions can tell a design review which results count. A lab that can't will re-run tests to be safe.

Can the Hardware Test Lab LIMS Schedule Every Constraint?

A hardware test lab LIMS schedules every constraint if it passes two scheduling questions in the Eight-Question LIMS Fit Check:

  • Refusal: Will the schedule refuse to book a test onto a shift with no operator certified for it? A hardware test lab LIMS that accepts the booking is a calendar, and the scheduler is still the one checking certifications. Use a certified operator whose certification covers one workstation and a test booked on another;

  • Late units: When a test unit arrives two days late, can the system reschedule against every constraint and show the new completion date the same day? Ask to see the reschedule done with a continuous test and a calibration due date in the same week.

The late-unit question is the one to weight most heavily in a lab with certified operators on several shifts. A hardware test lab LIMS that can build a first schedule and can't rebuild it will leave your scheduler with the harder half of the work.

Run both scheduling checks on your own data where you can. A demonstration built on the vendor's sample lab shows the screens, and your own week with one late test unit shows the scheduling.

Will Manufacturing LIMS Records Hold Up Under ISO/IEC 17025?

Manufacturing LIMS records hold up under ISO/IEC 17025 if the system passes two records questions in the Eight-Question LIMS Fit Check:

  • Automatic evidence: Does every result carry the certified operator, the equipment, and its calibration status without anyone typing them in? Evidence that depends on manual entry has gaps on the busiest days. Check a work order from a week when the lab ran at full load;

  • Authorization on the day: Can an assessor see who was authorized to run a test on the day it ran? The record has to show the certification as it stood on the test date, including certifications that have since expired.

A manufacturing LIMS that passes both records questions makes assessment preparation a matter of opening records. A manufacturing LIMS that fails either question leaves the lab rebuilding its evidence before every assessment.

Can Your Lab Adopt a LIMS for Discrete Manufacturing Mid-Program?

Your lab can adopt a LIMS for discrete manufacturing while tests keep running if the system passes two adoption questions in the Eight-Question LIMS Fit Check:

  • Existing plans: Can your existing Excel test plans come across with their history? A lab that has to re-enter its open programs by hand will run two systems for months. Ask what happens to completed tests and their dates during the import;

  • Daily users: Will requestors and operators, the two largest groups of users, do their daily work in the system without training on the scheduler's view? Adoption depends on those two groups far more than on the few schedulers.

A lab that gets both adoption answers before signing knows what the first month will look like. Requestors submit complete test requests, operators update work orders at the workstation, and the scheduler stops being the only person who knows the plan.

Lab software that only the scheduler can use leaves requestors emailing for status and operators updating a spreadsheet. QATrax gives requestors and operators dedicated browser-based workflows, so both groups work in it daily.

Book a Demo

How QATrax Works as a Project-Centric LIMS for Discrete Manufacturing

QATrax is TraxStar's LIMS for discrete manufacturing: a project-centric LIMS for industrial and manufacturing test labs, with test and resource scheduling at its core. TraxStar has built lab software for these test labs for more than 20 years, for engineering-driven industries such as automotive testing, computer hardware validation, and appliance testing. In QATrax, work requests capture the required data upfront, and work orders, test units, and results all sit under the project they belong to, so each test unit keeps its configuration and test history as it moves through its tests.

QATrax keeps the schedule in the same system as the project record, which is the arrangement a hardware test lab LIMS needs. The QATrax scheduler aligns certified operators, equipment, test units, and test methods, and it considers workstations, test method profiles, operator certifications, equipment calibrations, and sequence requirements together. When a test unit arrives late or an urgent test request lands, your scheduler can reschedule one request or the whole lab in one move, and the new completion dates follow from the same constraints the first schedule used.

QATrax also holds the evidence a manufacturing test lab is asked for, because it tracks calibration status and enforces operator certifications against test method profiles, as described under ISO/IEC 17025 support in QATrax. TraxStar delivers workflow consulting, data migration from legacy systems and spreadsheets, configuration, and training as part of every rollout, and existing Excel test plans can be imported. Those TraxStar implementation services mean a project-centric LIMS arrives configured for how your lab already works, with requestors and operators working in dedicated browser-based workflows.

Running a hardware test lab on software built for samples leaves the scheduler rebuilding each week. TraxStar implements QATrax with consulting, data migration, and training, so your team starts with its data in place.

Book a Demo

Frequently Asked Questions About LIMS for Discrete Manufacturing

What Are the Different Types of LIMS?

LIMS fall into two types by data model, sample-centric and project-centric, and into further types by the industry each was built for. A sample-centric LIMS makes the sample or batch the parent record, which suits life-sciences, chemical, food, and environmental labs. A project-centric LIMS makes the project the parent record, which suits a LIMS for discrete manufacturing and its test labs.

What Are the Top 5 LIMS Software?

No single top-five list of LIMS software fits every lab, because most published rankings compare life-sciences and quality control products. A manufacturing test lab gets a more useful shortlist by category: sample-centric LIMS, project-centric LIMS, and scheduling tools. The deciding test for a LIMS for discrete manufacturing is whether it schedules certified operators, workstations, and test sequence together.

Is LIMS an ERP System?

No, a LIMS and an ERP system are different systems with different records. ERP plans materials, orders, inventory, and cost across the business, while a LIMS manages a lab's test requests, test work, and results. A manufacturing LIMS and ERP usually run side by side, and neither holds the other's records.

What Manufacturing Industries Use LIMS?

Process industries and discrete industries both use LIMS, in different labs. Process manufacturers such as chemical and food producers use a manufacturing LIMS for batch quality control. Discrete manufacturers in automotive, aerospace, appliances, electronics, and HVAC use a LIMS for discrete manufacturing in the test labs that validate their products.

Do You Have to Replace a LIMS to Implement PLM?

No, you can implement PLM and keep your LIMS. In the PLM vs LIMS split, PLM holds the product definition and its change history, and the LIMS holds the lab's test requests, schedule, and results. The manufacturers we work with typically run both, passing requirements down to the lab and results back up.

When Should a Test Lab Implement a Manufacturing LIMS?

A test lab should implement a manufacturing LIMS when its schedule lives in one person's spreadsheet. Two other signs point the same way: completion dates move with no traceable cause, and results can't be tied to a specific test unit and revision. By then the lab is spending its schedulers' time reconciling files.

Can a Manufacturing LIMS Replace a Test Lab's Spreadsheets?

Yes, a manufacturing LIMS can replace a test lab's spreadsheets for the test plan, the schedule, and test status. Those three need shared, current records that a spreadsheet can't keep once several schedulers and requestors edit it. Spreadsheets often stay in use for one-off analysis of results, which is work they handle well.

What Is Hardware Testing in a Manufacturing Test Lab?

Hardware testing in a manufacturing test lab is the physical testing of a product or component before it goes to market, such as endurance runs and environmental tests on a prototype. The required tests often depend on the country or region where the product will be sold. A hardware test lab LIMS schedules and records that testing.

A test lab that outgrows its spreadsheet finds out when a completion date slips without explanation. QATrax keeps work requests and the schedule in one system, so a slipped date has a record behind it.

Explore QATrax LIMS