maurice vs biophase 8800 vs labchip gxii touch · maurice vs biophase
Maurice vs BioPhase 8800 vs LabChip GXII Touch Compared
November 12, 2026
29 min read
Compare Bio-Techne Maurice, SCIEX BioPhase 8800 (software 1.6, Sept 2026) and Revvity LabChip GXII Touch on CE-SDS, charge assays, data paths, audit trails, pilot design and cost per accepted report.
- 01No independent comparison on current configurations ranks all three platforms. Select by intended assay, software edition and data path, then verify with a same-material pilot.
- 02Maurice combines size and charge assays in one family; BioPhase offers parallel capillaries and detector choice; LabChip supports microfluidic analysis from plates.
- 03Detector and labeling choices can change reported purity, so results from different methods need a bridging study before pooling.
- 04Audit trails and access controls depend on software mode or optional modules. Technical controls alone do not establish compliance.
- 05Published speed figures use different assays and units. Compare cost per accepted report using pilot results, utilization, rejection rate and buyer-supplied inputs.
Executive Summary
This report compares three protein-purity platforms as assay-and-data workflows rather than as boxes: the Bio-Techne Maurice family, the SCIEX BioPhase 8800, and the Revvity LabChip GXII Touch. No source read for this report supplies a same-material, same-lab, independent comparison of all three on current configurations, so no platform is ranked. The decision that the evidence does support is which assay type, software edition and data path match a given intended use. All product facts below are dated to retrieval on 2026-11-12 and are vendor statements unless a peer-reviewed or regulatory source is named.
The timely change is on the SCIEX side. SCIEX announced BioPhase software 1.6 on September 28, 2026, listing user management, audit trails, electronic signatures and project management tools ([1]). The 1.6 release notes state that the Audit Trail workspace is not available in workstation mode ([2]), and that the new Instrument API must be installed by a SCIEX field service employee ([3]). The software validation summary on file covers components released June 2024, so a 1.6-specific validation document was not located.
The three systems measure different things. BioPhase 8800 offers eight parallel capillaries and a choice of native fluorescence (NF), ultraviolet (UV) or laser-induced fluorescence (LIF) detection ([4]). Maurice runs CE-SDS with UV absorbance at 220 nm ([5]) and is also positioned for charge analysis ([6]). LabChip GXII Touch is a microfluidic system that reads 24-, 96- or 384-well plates ([7]). Detector choice changes reported purity: for non-reduced NISTmAb (the antibody shown in the note's Figure 2 for the PA 800 Plus), SCIEX reports 95.45% by LIF on a PA 800 Plus against 97.57% by UV on the same platform ([8]).
Regulatory text sets what a records workflow must demonstrate, not what any product guarantees. 21 CFR Part 11 asks for secure, time-stamped audit trails ([9]), and Revvity's own manual states that its GxP option alone does not ensure compliance ([10]). ICH Q14 describes transfer to a different location as needing a bridging strategy ([11]), so "unchanged transfer" should not be assumed.
The recommended path is a predefined same-material pilot. Score precision, resolution of named critical pairs, quantitation limits, repeat rate, reviewer time and traceability, then compute cost per accepted report with buyer inputs. A sensitivity illustration in this report shows that, for fixed-cost items, moving utilization from 90% to 50% raises cost per accepted report by a factor of about 1.8 at a 2% rejection rate (arithmetic, not a price claim).
SCIEX-reported non-reduced NISTmAb purity by LIF on a PA 800 Plus, illustrating detector effects
SCIEX-reported non-reduced NISTmAb purity by UV on the same PA 800 Plus
Published Maurice Turbo CE-SDS run time for reduced IgG; cartridge-specific vendor figure
Maximum samples per run listed by Revvity for LabChip GXII Touch; a vendor throughput claim
Introduction and Background
Protein purity for a monoclonal antibody (mAb) is rarely one number. Size variants (fragments, aggregates, non-glycosylated heavy chain), charge variants and glycan occupancy each need their own assay. Proteins also carry an inherent degree of structural heterogeneity ([12]). ICH Q6B notes that determining absolute and relative purity of biological products is analytically challenging and method-dependent ([13]), and that purity is assessed by a combination of procedures ([14]). It names capillary electrophoresis alongside polyacrylamide gel electrophoresis among the accepted electrophoretic approaches ([15]). Maurice, BioPhase 8800 and LabChip GXII Touch overlap on capillary or microfluidic sodium dodecyl sulfate (CE-SDS) size assays, but they diverge on charge assays, detectors, plate formats and software.
This report is written for analytical-development scientists, quality control (QC) method owners, automation leads and laboratory informatics architects. It treats three use cases separately: mAb development, where method flexibility and resolution of critical pairs dominate; high-throughput screening, where plate format and walk-away operation dominate; and QC release, where validated software, review workflow and record retention dominate. Adeno-associated virus (AAV) capsid work is covered only where assay-specific evidence exists, namely one 2024 presentation discussed below.
IntuitionLabs perspective. IntuitionLabs is not an instrument or software vendor, so it is not one of the options compared here. The framing suggested here is: choose an assay and a record architecture first, then test candidate instruments against both. That framing is consistent with ICH Q14, which says the analytical target profile (ATP), the intended purpose and performance criteria, drives the choice of technology ([16]).
Scope and evidence rules
- Primary sources only. Product facts come from manufacturer pages, release notes and manuals. Where a manufacturer authored a comparison involving a competitor, it is labelled a vendor claim and not repeated as a ranking.
- No hands-on benchmarking. This comparison is based on published vendor and literature material, not instrument testing. Cells in the pilot table that require measurement are left blank for the buyer to fill.
- Gated literature. Bio-Techne's Maurice versus LabChip NISTmAb summary page identifies a reduced and non-reduced comparison on a National Institute of Standards and Technology reference antibody ([17]). The full note sits behind a form on that page; the findings here draw on a separately hosted vendor PDF of a Maurice versus LabChip note. No independent numerical comparison of all three platforms is publicly available in the sources reviewed.
- Separate layers. Raw traces, processed peaks and reports are treated as three different records throughout. PIC/S defines raw data as the original record ([18]).
Define the critical quality attribute first
Start from the attribute and the decision it supports. ICH Q14 describes an ATP as the intended purpose, the attributes to be measured and performance criteria ([19]). ICH Q2(R2) states the validation objective as demonstrating fitness for the intended purpose ([20]). A practical ATP for a CE-SDS purity assay names the analyte, reduced or non-reduced condition, the critical pair (for example non-glycosylated heavy chain versus heavy chain), the reportable quantitation limit and the acceptance range. Without it, vendor speed figures cannot be compared because they describe different readouts.
Bio-Techne Maurice
Capabilities
Bio-Techne's current Maurice family comprises Maurice, Maurice C, Maurice S and MauriceFlex, per its consumables pages (retrieved 2026-11-12) ([21]). The base Maurice is positioned as a combined imaged capillary isoelectric focusing (icIEF) and CE-SDS instrument ([6]), while the S variant is the CE-SDS configuration with Turbo CE-SDS or CE-SDS PLUS cartridges ([22]). Cartridge compatibility is model-specific: the CE-SDS PLUS cartridge lists Maurice (090-000), MauriceFlex (090-158) and Maurice S (090-001) ([23]), and charge cartridges list Maurice, MauriceFlex and Maurice C.
Published run times differ by cartridge: Turbo CE-SDS lists 5.5 minutes for reduced IgG and 8 minutes for non-reduced IgG ([24]). CE-SDS detection is UV absorbance at 220 nm ([5]). A cartridge is listed at 100 guaranteed injections and a maximum of 500 for some cartridge types ([25]). A vendor application note describes up to 48 samples per batch ([26]).
Calibration and standards are sold as consumables. Molecular weight markers are supplied from 10 kDa upward ([27]), and a cIEF system suitability kit exists for Maurice and Maurice C ([28]). A vendor note states a CE-SDS size range of 10 to 240 kDa ([29]), whereas the marker set sold spans to 270 kDa, so the validated range for a given product should be confirmed in writing.
Adoption and evidence base
For charge analysis, a multi-company icIEF study comparing Maurice and iCE3 is summarized in a 2025 review, which reports 19 participating companies ([30]). A GMP-environment instrument change study to Maurice C reported that a quantitation-limit-level peak was more robust on Maurice C ([31]), while noting that numeric resolution could not be compared because peaks were not baseline separated ([32]). Both concern icIEF, not CE-SDS purity.
For CE-SDS, the public evidence is vendor-authored. Bio-Techne reports percent peak area relative standard deviations (RSDs) of 1% or less for all peaks across an injection batch on CE-SDS PLUS ([33]), and states comparability of CE-SDS PLUS with a United States Pharmacopeia (USP) protocol for mAbs ([34]). These are manufacturer statements, not independent validation.
Strengths and limitations
- Strength: one platform for size and charge. Maurice covers CE-SDS and icIEF in one family, which suits teams that want one vendor for orthogonal assays.
- Strength: documented access-control option. Compass for iCE offers optional Access Control; when enabled users must log in ([35]) and data files are signed and encrypted against unauthorized changes ([36]).
- Strength: CDS paths. Bio-Techne documents Empower driver support across several cartridges ([37]) and a Chromeleon path with manual pI recalibration ([38]). These are supported alternatives to native Compass, not equivalents of it.
- Limitation: edition and model dependence. The Authorization Server is listed on the download page for use with Compass for iCE ([39]), and Compass 4.1.0 is listed for Windows 11 64-bit ([40]). Which models and cartridges each control module covers should be confirmed for the exact configuration.
- Limitation: calibration sensitivity in charge assays. An independent paper reports that the infliximab main-peak pI on Maurice depended on the pI-marker calibration choice, giving 7.56 in one fit ([41]). Calibration settings belong in the method record.
- Limitation: unknown public export specification. The Compass page describes review and data reports, but no Bio-Techne page read states native file formats. An independent paper describes raw data export as text files ([42]) for an older software version.
SCIEX BioPhase 8800
Capabilities
The BioPhase 8800 uses eight capillaries in parallel, with an eight-capillary cartridge as the consumable ([43]). The product page lists NF, UV and LIF detection, with UV described as a bridge to legacy data. SCIEX states that NF permits quantitation of low-level impurities down to 0.01% ([44]), a vendor claim to be tested against your own impurity limits. Kit-based workflows include CE-SDS for size heterogeneity and native capillary zone electrophoresis (CZE) for charge heterogeneity ([45]).
Throughput claims need careful reading. A SCIEX tech note states a method that can analyze 192 reduced samples in 14 hours ([46]). The same note defines a data point as one separation from one well using one capillary ([47]) and a run as eight data points. Parallel channels therefore multiply data points per run but do not by themselves define end-to-end throughput, which also includes preparation, conditioning and review.
What the September 2026 update changes, and what remains unproven
SCIEX's September 28, 2026 announcement describes BioPhase software 1.6, adding user management, audit trails, electronic signatures and project management tools ([1]) and an Instrument API through which external software can interact via remote sequence execution ([48]). The software downloads page lists BioPhase Project Management Software 1.6 ([49]). Release notes add Windows 11 support; version 1.5 had been documented for Windows 10 and had added NF acquisition and analysis ([50]).
The software page describes two operating models. Enterprise mode adds controlled access management, audit capabilities and user permissions ([51]), while workstation mode is a streamlined environment for method development, sequence creation and data analysis. The release notes state electronic signatures use a user ID and password combination ([52]), project access is controlled user by user, and the Audit Trail workspace is unavailable in workstation mode ([2]). For a regulated lab, the edition therefore changes the record, not only the interface.
The API scope is narrower than "data integration" might suggest. The API page describes remotely starting, monitoring and stopping sequence runs ([53]) and access to project and sequence information. The product page positions it for existing laboratory automation platforms. The release notes add that the API must be installed by a SCIEX field service employee ([3]). No page read documents result export to an ELN or LIMS through the API, so that remains a vendor question.
Unproven items as of 2026-11-12:
- Validation of 1.6. The validation summary found covers components released June 2024 ([54]).
- Driver parity. The Empower driver release notes read are for the 1.5 generation and require Empower 3 (FR4) or later ([55]); a driver release matched to 1.6 was not found.
- Export formats. The documented sequence-editor reports are Summary, Detailed and one further report type; raw-data export formats are not publicly documented in the pages reviewed; ask SCIEX.
- Performance of the update. The announcement's productivity statements are vendor claims. No independent measurement of 1.6 was found.
Adoption and evidence base
All BioPhase 8800 numeric evidence found is SCIEX-authored. For CE-SDS with native fluorescence, SCIEX reports RSD below 0.1% for relative migration time and below 0.4% for corrected peak area percent of the heavy chain ([56]). For cIEF on NISTmAb, SCIEX reports a 96-well plate in about 12 hours compared with 5 days on a single-capillary instrument ([57]). These show intended performance under vendor conditions; they are not a reproduction in a buyer's matrix.
Strengths and limitations
- Strength: parallel capillaries and detector choice. Eight channels and NF, UV or LIF options suit method development across analytes.
- Strength: Enterprise-mode controls. Access management, audit capabilities and user permissions are described for Enterprise mode, as noted above.
- Strength: alternate CDS path. The Empower driver stores multi-capillary data with linked sample information ([58]) and lets users apply Empower's 21 CFR Part 11 toolset ([59]). SCIEX reports separations comparable to those from native software.
- Limitation: detector-dependent response. SCIEX states fluorescence modes do not provide the uniform response of UV absorbance ([60]), so purity values are method-specific.
- Limitation: version coverage. Validation documentation, driver versions and API scope should be requested for the exact release.
“Technical controls alone do not establish compliance; they are inputs to a validated process with procedures, training and review.
Revvity LabChip GXII Touch
Capabilities
LabChip GXII Touch is a microfluidic electrophoresis system with a single-sipper chip handling samples from 24-, 96- or 384-well plates ([7]). Revvity lists throughput up to 384 samples per run ([61]) and chip life up to 400 runs ([62]). Its software reports concentration, sizing and percent purity using ladder and marker calibration ([63]), with results as virtual gel, electropherogram or table. The product note places glycan screening and charge variant assays on the same system.
For the Protein Clear HR assay, the user guide specifies a sizing range of 14 to 250 kDa ([64]), resolution above 1.0 for the VeriMAb reference ([65]) and percent purity reproducibility below 0.5% for the main non-reduced IgG peak ([66]). These are vendor specifications under defined conditions. A vendor note describes a two-step calibration ([67]), and the product note defines resolution as the migration-time difference divided by the summed peak widths ([68]). Confirm that your acceptance criteria use the same definition.
Software, records and data export
LabChip GX Reviewer is described as the foundational software included with every instrument ([69]). The optional GxP module adds technical controls and traceable audit histories ([70]), and is described as supporting alignment with FDA 21 CFR Part 11. A Revvity flyer lists comprehensive audit logs among its security features ([71]). The product note lists a GMP, 21 CFR Part 11 compliant software option ([72]).
Export is better documented than for the other two. A user manual (Rev. B, hosted on a third-party site and dated 2018, so version-dated) states that peak and well tables export to CSV or XML ([73]) and that raw data can be exported as CSV, XML or AIA ([74]). The assay guide describes automatic export of results tables ([75]). The same manual cautions that the GxP option alone does not ensure 21 CFR Part 11 compliance ([10]). A Waters Empower driver, listed as LabChip Empower Driver 1.0, appears in the brochure ([76]).
Adoption and evidence base
A peer-reviewed 2014 study of a LabChip GXII with therapeutic antibodies reported intermediate precision of 18 determinations at 2.1% RSD or less ([77]), and noted that absolute purity values in peak area percent differed from conventional capillary SDS electrophoresis, attributed to detection methods ([78]). That is an older chip generation and software, so it informs method behavior rather than current performance. A vendor note reports a NISTmAb monomer purity of 98.52% by microfluidic CE-SDS and 98.47% on a SCIEX PA 800 Plus ([79]), and a per-sample analysis time of 65 seconds ([80]).
Strengths and limitations
- Strength: plate-native format. Direct 384-well processing suits screening and early development.
- Strength: documented export. CSV, XML and AIA export paths are described in the manual, subject to checking against the current software.
- Limitation: resolution definition and range. The assay specifies 14 to 250 kDa; fragments or aggregates outside a validated range need a different assay.
- Limitation: current software facts undocumented. Current software version, release dates and service terms are not publicly documented in the vendor pages reviewed; request them in the quote.
- Limitation: regulated edition is a separate module. The GxP option is optional.
Feature Comparison
Table 1 below is a row-level evidence matrix. It records only what a read page states; "not found" means the item was not publicly documented in the vendor pages reviewed in November 2026, not that the capability is absent; confirm with the vendor. Cells that depend on the installed configuration are marked "confirm". Editions differ, and no row should be read as meaning that all editions share the same controls.
| System and assay | Analyte or material in sources | Detector | Cartridge or chip | Software and version | Raw record and export | Calibration or standards | Access-control module |
|---|---|---|---|---|---|---|---|
| Maurice, CE-SDS PLUS or Turbo | IgG standards, NISTmAb in vendor notes ([81]) | UV 220 nm | CE-SDS PLUS cartridge, model-specific | Compass for iCE 4.1.0, Windows 11 | Signed, encrypted data files with Access Control; native format not found | MW markers | Optional Access Control with Authorization Server |
| Maurice, cIEF or icIEF | mAb charge variants | Confirm per model and cartridge | cIEF and icIEF 400 cartridges | Compass 4.1.0 or Empower ICS v1.2 | Text export in an older version | pI markers, suitability kit | As above, or CDS controls ([82]) |
| BioPhase 8800, CE-SDS | Non-reduced IgG (NISTmAb per the note's Figure 2 caption) ([8]) | NF, UV or LIF | Eight-capillary cartridge | BioPhase 1.6 (announced Sept 28, 2026) | PDF reports; raw export not found | Kit-specific (confirm) | Enterprise mode with Project Management |
| BioPhase 8800, cIEF or CZE | NISTmAb cIEF in SCIEX note | UV 280 nm in note; native CZE listed | Eight-capillary cartridge | BioPhase 1.6; Empower driver 1.5 generation | Folder acquisition or Empower database | Kit-specific (confirm) | Audit Trail unavailable in workstation mode |
| LabChip GXII Touch, Protein Clear HR | VeriMAb, NISTmAb in vendor notes | Fluorescence-based (confirm for current chip) | HT chip, up to 400 runs | GX Reviewer; optional GxP module | CSV, XML, AIA export (2018 manual) | Ladder and markers | Optional GxP module |
| LabChip GXII Touch, charge and glycan | Not stated in pages read | Confirm | Confirm | Confirm | Confirm | Confirm | Optional GxP module |
The matrix shows three asymmetries. First, Maurice and BioPhase publish more consumable and cartridge detail, while LabChip publishes more about export formats. Second, access-control and audit functions sit in optional or mode-specific components for all three, so purchase scope matters. Third, the evidence-date column in practice is "page retrieved 2026-11-12"; several pages carry no publication date, so version currency must be confirmed in a vendor quote.
Native software versus supported external data paths
Table 2 maps data paths. The Empower driver paths are shown only because all three vendors document one; this report does not compare chromatography data systems, and an existing integration is only one supported path.
| Path | What the vendor documents | Record layers to confirm | Gaps found |
|---|---|---|---|
| Maurice native (Compass) | Login, signed and encrypted files with Access Control | Raw trace, processed peaks, report | Export formats not stated on vendor pages |
| Maurice with Empower | Control of Maurice cartridges with Part 11 compliance-readiness described ([83]) | Raw data in CDS database, reintegration history | Whether native and CDS results match for your method |
| BioPhase native, workstation mode | Method development, sequences, analysis | Raw files in selected folder | No Audit Trail workspace |
| BioPhase native, Enterprise mode | Access management, audit, permissions | Project-managed records | Validation evidence for 1.6 |
| BioPhase with Empower driver | Linked sample information and Part 11 toolset | CDS database | Driver version versus 1.6 |
| BioPhase Instrument API | Remote start, monitor, stop of sequences | Run metadata, not documented as results export | Result and ELN/LIMS export scope |
| LabChip native (GX Reviewer) | Peak integration, sizing, quantification | Raw, peak table, report | Current software version |
| LabChip with GxP module | Controls and audit histories | Audit history, signatures | Not sufficient alone |
| LabChip with Empower driver | Driver listed | CDS database | Chip and assay coverage |
Read the table by record layer. A raw trace is the first capture, a processed peak table is the product of integration parameters and calibration, and a report is a rendering. The FDA data-integrity question-and-answer document defines an audit trail as a secure, computer-generated, time-stamped record ([84]) and describes audit trail review as comparable to assessing cross-outs on paper ([85]). If reintegration is a normal part of CE-SDS review, the audit trail should show who changed integration, when, and why. Part 11 signature manifestations carry the date and time of signing ([86]). EU Annex 11 asks that reasons for changes to GMP-relevant data be documented ([87]).
Performance and Benchmarks
What the public evidence does and does not show
No peer-reviewed head-to-head of all three platforms was found. Public comparisons are vendor-authored, run on different material and configurations, and read here as design information. Bio-Techne's gated summary lists the compared parameters as linearity, sensitivity, precision, reproducibility and resolution ([88]), but its numeric results are not in the public summary. A vendor PDF reports Maurice limits of detection and quantitation of 3.7 and 20.1 micrograms per milliliter for a spiked species in non-reduced samples ([89]); it should be read with the study design in view, not as a general limit.
Detector and response factor effects
Detector choice changes what "purity" means. SCIEX's own comparison reports non-reduced NISTmAb purity (per the note's Figure 2) on a PA 800 Plus of 95.45% by LIF, below the UV value, and states that fluorescence modes lack UV's uniform response. A pilot should therefore hold detector, labeling chemistry and integration rules constant per platform and report them with each result.
Size and charge assays are not interchangeable
CE-SDS reports size variants under denaturing conditions, whereas cIEF, icIEF and CZE report charge. A 2025 review summarizing a mAbs study states that cIEF and icIEF may not be considered directly interchangeable ([90]), and NIST describes CE-SDS as orthogonal to size-exclusion chromatography (SEC) ([91]). NIST also qualified cIEF for structural pI characterization and CZE for routine charge monitoring ([92]). Treat each assay as its own method, so a "Maurice vs BioPhase cIEF" comparison must name the exact charge technique on each side.
CE-SDS versus SDS-PAGE for mAb purity
CE-SDS offers on-column quantitation, higher resolution and automation compared with slab-gel SDS-PAGE according to a NIST paper ([93]). A 2012 study repeating one sample 21 times by SDS-PAGE reported large standard deviations for chain percentages ([94]), while the validated CE-SDS method showed RSD below 2.0% for corrected area percentage ([95]). NIST's paper describes a qualified CE-SDS method for which intermediate precision was assessed as coefficients of variation ([96]). Microfluidic systems add a third class: the 2014 LabChip study reported precision of 2.1% RSD or less yet different absolute purity values from capillary SDS.
The Lilly 2024 AAV presentation: scope limits
A presentation at the CE Pharm Symposium 2024 (dated September 16, 2024) compared CE-SDS platforms for AAV capsid purity and viral protein (VP) ratios ([97]). It treats CE-SDS as an alternative to SDS-PAGE for capsid purity, defines purity as the sum of VP1, VP2 and VP3 percentages, and notes low protein content as the reason LIF is favored for AAV ([98]). The same AAV9 sample measured on a PA800+ with different detections gave different VP ratios ([99]), and the presenter states that dye selection has significant impact on the VP ratio ([100]).
Applicability limits are strict. The work covers AAV capsids, not mAbs; it reflects instrument configurations of 2024; and its summary describes evaluation on AAV CE-SDS ([101]). Its detector and software observations should not be applied to current 2026 configurations without rechecking, and no performance conclusion from it is carried into this report. The useful generalization is methodological: labeling and detection choices shape reported ratios, so they belong in the method definition.
Interlaboratory evidence on transfer
Method transfer evidence exists at the technique level. An interlaboratory CE-SDS validation covered 13 laboratories in 13 companies on four commercial capillary electrophoresis platforms ([102]), and an earlier icIEF study across laboratories reported apparent pI RSD below 0.8% ([103]). A QbD-based CE-SDS validation reported meeting required criteria ([104]). The abstracts read do not give per-platform numerics, so they show that transfer is feasible under controlled protocols, not that any method transfers unchanged. ICH Q14, adopted on 1 November 2023 ([105]), frames transfer as needing a bridging strategy ([11]). Pharmacopoeial capillary electrophoresis chapters in the ICH regions are described as interchangeable ([106]), but that concerns the general chapter, not equivalence between instruments.
Data Analysis and Evidence
Same-material pilot design
Table 3 below defines the pilot. Every result cell is intentionally blank: the point is that the buyer fills it from measurements, not from brochures.
| Pilot element | Definition to fix before testing | Result per platform (buyer fills) |
|---|---|---|
| Material | One reference mAb lot plus a stressed lot, reduced and non-reduced | |
| Repeatability and intermediate precision | Use ICH Q2(R2) definitions ([107]) ([108]), and state the range ([109]); set analysts, days and cartridges or chips | |
| Resolution | Named critical pairs, with the formula stated | |
| Specificity | Interference by other substances ([110]) | |
| Quantitation limit | Lowest amount determined with suitable precision and accuracy ([111]) | |
| Repeat rate | Share of runs repeated for system suitability or integration failure | |
| Analyst review time | Minutes per report including reintegration | |
| Traceability checks | Raw trace, integration parameters, reviewer edits, signature, export identifiers |
The pilot should include a traceability exercise using a buyer-controlled sample record: acquire, review with a deliberate reintegration, export, and import into the target ELN, LIMS or CDS, then verify that identifiers, integration parameters and audit entries survive. Part 11 asks for authority checks so that only authorized individuals can alter records ([112]) and for signatures linked to their records ([113]). FDA guidance states that shared login credentials prevent identifying a unique individual ([114]), so the pilot should use named accounts. Part 11 also asks that system access be limited to authorized individuals ([115]) and that each identification code and password combination be unique ([116]). PIC/S says audit trail functionality should be enabled and locked at all times ([117]), and that review of audit trails should be part of routine data review ([118]). FDA frames review frequency as risk-based ([119]) and its guidance is non-binding ([120]). FDA describes data integrity as the completeness, consistency and accuracy of data ([121]), and PIC/S states its guide interprets existing requirements without adding regulatory burden ([122]).
Cost per accepted report
Use this formula with buyer-supplied inputs:
Cost per accepted report = (annualized instrument + service + software + standards + cartridges or reagents + analyst labor + rework + integration) divided by accepted reports
where accepted reports equal reports attempted multiplied by one minus the rejection rate. No prices are given here because none were retrieved; quotes should be obtained in writing for the exact configuration. Part 11 expects validation of systems ([123]), so validation labor belongs in the software or integration line.
Throughput figures in vendor documents define different units, so convert them carefully. SCIEX's 192 samples in 14 hours is 13.7 samples per hour end to end under its stated conditions, or 35 minutes per eight-capillary run across 24 runs (arithmetic). Revvity's 65 seconds per sample times 384 samples is about 6.9 hours of separation time, excluding preparation and chip handling (arithmetic). Maurice's Turbo CE-SDS lists 5.5 minutes for reduced IgG, cited above. These numbers come from different assays, material and unit definitions, so they must not be ranked against each other.
Sensitivity illustration (Hypothetical Example)
The following index uses only arithmetic, no prices. For fixed-cost lines (annualized instrument, service, software), cost per accepted report scales as 1 divided by (utilization times (1 minus rejection rate)), relative to a fully used instrument with zero rejection (index 1.00). For variable lines (cartridges, reagents, labor), it scales as 1 divided by (1 minus rejection rate).
- Utilization 90%: index 1.13 at 2% rejection, 1.17 at 5%, 1.23 at 10%.
- Utilization 70%: index 1.46 at 2% rejection, 1.50 at 5%, 1.59 at 10%.
- Utilization 50%: index 2.04 at 2% rejection, 2.11 at 5%, 2.22 at 10%.
- Variable lines only: index 1.02 at 2% rejection, 1.05 at 5%, 1.11 at 10%.
Utilization, not nominal channel count, dominates the fixed-cost lines in this illustration. Use your own utilization and rejection ranges, and add rework hours from the pilot's review-time and repeat-rate cells.
Decision Scenarios by Use Case (Hypothetical Examples)
These scenarios are hypothetical (Hypothetical Example) and illustrate decision logic only.
- mAb development lab with orthogonal needs. A team needing CE-SDS and a charge assay on one vendor may shortlist Maurice or BioPhase, because both document size and charge workflows. The pilot should test the specific charge technique on each.
- Screening group with plate libraries. A group processing 384-well plates may start from LabChip GXII Touch, whose published format is 24-, 96- or 384-well plates, then check whether chip-based resolution meets its critical-pair criteria.
- QC lab with an existing CDS. A QC lab may prefer a documented CDS path; all three vendors document an Empower driver: Maurice ([37]), BioPhase ([58]) and LabChip ([76]). Native and CDS results should still be compared.
Implications and Future Directions
The September 2026 SCIEX release shifts the BioPhase 8800 conversation from capillary count toward records. That is relevant because the first-order differences among the three systems in a regulated lab may be edition scope, audit-trail availability and export path. The EU consultation on a revised Annex 11 emphasizes lifecycle management of computerised systems ([124]), which points to software versioning and change control as continuing evaluation criteria, though the revised text is a draft issued for consultation, the consultation period has closed, and final adoption has not been confirmed here. Annex 11 also asks that application validation and infrastructure qualification be addressed ([125]) and that access authorization changes be recorded ([126]).
Vendor questions
- Versions. Which exact software, firmware, cartridge or chip and driver versions will ship, and which validation package covers them?
- Editions. Which controls (audit trail, signatures, access) are in the quoted edition, and which need an add-on module?
- Raw record. What are the native raw-data format, retention location and archive behavior, and can raw data be re-opened without the instrument?
- Reintegration. Are integration parameters, manual edits and reprocessing versions captured in the audit trail with reasons?
- Export. Which formats carry sample IDs, integration parameters and calibration, and has export to the target LIMS or ELN been tested?
- API scope. Does the BioPhase Instrument API provide results or only run control? For LabChip, which integration kit applies?
- Standards. Which calibration standards and suitability criteria are mandatory, and who supplies them?
- Service. What are installation (for example field-installed API), response times and software update policy?
Evidence gaps
- Independent three-way data. None is publicly available in the sources reviewed; the full Maurice versus LabChip note is gated.
- Current versions. LabChip software version history and BioPhase 1.6 validation are not publicly documented in the sources reviewed.
- Pricing and service quotes. Not publicly available; none are asserted here.
Technical controls alone do not establish compliance; they are inputs to a validated process with procedures, training and review. Laboratories should involve their quality unit and, where needed, qualified regulatory or computerized-system validation professionals. This article is not a substitute for that review.
Frequently Asked Questions (FAQs)
Maurice vs BioPhase 8800 protein purity: which is better?
No public independent evidence ranks them on current configurations. Both document CE-SDS workflows, with Maurice using UV 220 nm and BioPhase offering NF, UV or LIF. Decide with a same-material pilot.
BioPhase 8800 vs Maurice for cIEF: what differs?
BioPhase lists native CZE for charge heterogeneity and a cIEF kit, while Maurice lists cIEF and icIEF 400 cartridges. Charge techniques are not interchangeable ([90]), and NIST qualified CZE for routine charge monitoring ([92]).
LabChip GXII Touch vs capillary electrophoresis: how do they differ?
LabChip uses a microfluidic chip with 24-, 96- or 384-well plates, while capillary systems use cartridges. A 2014 study found similar profiles but different absolute purity values versus capillary SDS.
CE-SDS vs LabChip for protein purity analysis: can results be pooled?
Not without a bridging study. ICH Q14 describes comparative analysis of representative samples as part of transfer strategy ([11]). Detector and labeling differences alone can move reported purity.
What data workflow supports protein purity review?
Separate raw trace, processed peaks and report, and verify that audit entries, integration parameters and identifiers survive export. Table 2 maps documented paths, and PIC/S expects audit trail review within routine data review ([118]).
What does LabChip GXII Touch protein characterization data analysis provide?
GX Reviewer provides peak integration, sizing and quantification, with CSV, XML and AIA export described in a 2018 manual.
Does Maurice CE-SDS meet 21 CFR Part 11?
Bio-Techne documents optional Access Control and describes Empower control as compliance-ready. Compliance depends on validation and procedures, since Part 11 requires validation of systems ([123]) and EU Annex 11 expects validated applications ([125]).
Is CE-SDS better than SDS-PAGE for mAb purity?
NIST lists on-column quantitation, resolution and automation as CE-SDS advantages, and ICH Q6B accepts both approaches ([15]). The choice depends on the ATP, and a validated CE-SDS method reported corrected-area-percentage RSD below 2.0% ([95]).
Conclusion
Name the analyte, reduced or non-reduced condition, critical pair, quantitation limit and acceptance range.
Match candidate instruments to the intended assay type and data path.
Request the controls in the quoted edition and identify any add-on modules.
Score precision, critical-pair resolution, quantitation limits, repeat rate, reviewer time and traceability.
Acquire, deliberately reintegrate, export and import a sample record; verify that identifiers, integration parameters and audit entries survive.
Use buyer-supplied costs and accepted reports, accounting for utilization, rejection and rework.
The three platforms are best treated as three assay-and-record architectures. Maurice combines size and charge in one family with an optional access-control module and documented CDS paths. BioPhase 8800 offers eight parallel capillaries, three detector modes and, with software 1.6, Enterprise-mode records and an Instrument API whose scope is run control and project information. LabChip GXII Touch offers plate-native microfluidic analysis and the most explicit export documentation among the three, with a separate GxP module.
Because the independent evidence is thin and vendor documents describe different assays, the defensible selection method is procedural: define the critical quality attribute and ATP, shortlist by assay type, request edition-specific controls in writing, run a same-material pilot with predefined criteria, test export into the target record system, and compute cost per accepted report from buyer inputs. Methods should be expected to need bridging, not to transfer unchanged.
About IntuitionLabs
Build practical AI for pharma and biotech with IntuitionLabs. We help life-science teams turn complex information and workflows into useful software, governed knowledge systems and AI tools.
IntuitionLabs is an AI consulting, custom software development and data engineering firm serving pharmaceutical, biotechnology, medical-device and other life-science organizations. We work with clinical, regulatory, medical-affairs, commercial, quality and IT teams to connect technology decisions with the work people need to accomplish.
AI consulting and adoption
Our AI enablement services cover readiness assessments, use-case selection, governance and policies, team workshops, adoption measurement and ongoing advisory support. We help organizations structure the information layer behind AI: source material, context, permissions and maintained knowledge that make generated answers useful and reviewable. Private LLM inference and hosted AI options support teams evaluating how to operate AI with appropriate control over their data and infrastructure.
Software, data and life-science workflows
IntuitionLabs develops custom software for pharma and biotech, integrates enterprise systems, and builds data engineering and business intelligence solutions. Areas of focus include AI agents, regulatory research, medical writing, medical affairs, CMC information, competitive intelligence and clinical-document workflows. Our eTMF intelligence work includes cross-system reconciliation and inspection-readiness support.
Enterprise platforms and regulated delivery
We provide Veeva services, application support, managed services, integrations and custom applications, alongside enterprise content work involving platforms such as Egnyte. For regulated workflows, our services include GxP enablement, computer-system validation and software development addressing 21 CFR Part 11 requirements. The applicable controls, validation responsibilities and acceptance criteria are defined for each engagement.
Work with IntuitionLabs
Explore AI enablement, pharma and biotech software development, data engineering and BI, and Veeva services. Contact IntuitionLabs to discuss your workflow, information sources and implementation needs.
IntuitionLabs publishes educational research to help life-science teams make informed technology decisions. Coverage of a product or organization does not imply a client relationship, endorsement or partnership.
Sources / 126
Need Expert Guidance on This Topic?
Let's discuss how IntuitionLabs can help you navigate the challenges covered in this article.
I'm Adrien Laurent, Founder & CEO of IntuitionLabs. With 25+ years of experience in enterprise software development, I specialize in creating custom AI solutions for the pharmaceutical and life science industries.
The information contained in this document is provided for educational and informational purposes only. We make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the information contained herein. Any reliance you place on such information is strictly at your own risk. In no event will IntuitionLabs.ai or its representatives be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from the use of information presented in this document. This document may contain content generated with the assistance of artificial intelligence technologies. AI-generated content may contain errors, omissions, or inaccuracies. Readers are advised to independently verify any critical information before acting upon it. All product names, logos, brands, trademarks, and registered trademarks mentioned in this document are the property of their respective owners. All company, product, and service names used in this document are for identification purposes only. Use of these names, logos, trademarks, and brands does not imply endorsement by the respective trademark holders. IntuitionLabs.ai is an AI software development company specializing in helping life-science companies implement and leverage artificial intelligence solutions. Founded in 2023 by Adrien Laurent and based in San Jose, California. This document does not constitute professional or legal advice. For specific guidance related to your business needs, please consult with appropriate qualified professionals.