CE_Recombinant_Protein_Purity

CE Recombinant Protein Purity

Lumex QC URS & FS input.csv output.json rule-based LIMS-ready capillary electrophoresis
Open selection

Utility description: CE Recombinant Protein Purity

CE Recombinant Protein Purity — Recombinant Protein Purity Control (SDS-CE)

ℹ️  Utility checks electrophoretic purity of protein under denaturing conditions:
    • Main Band ≥95.0%
    • High Molecular Weight Impurities (Aggregates) ≤2.0%
    • Low Molecular Weight Impurities (Fragments) ≤3.0%
    • Total Impurities ≤5.0%
    • Peak Resolution ≥1.5

⚠️  CRITICAL: Protein aggregates can trigger immune responses.
    Fragments indicate proteolytic degradation.

Usage:
  CE_Recombinant_Protein_Purity.exe                            → demo mode (console output)
  CE_Recombinant_Protein_Purity.exe input.csv output.json      → evaluate your data

Input format:
BatchNumber,ProteinName,MainBandPercent,HMW_Impurities_Percent,LMW_Impurities_Percent,Total_Impurities_Percent,Resolution

Example:
  PROT-REC-2026-001,Recombinant Human Insulin,97.5,0.5,1.2,2.5,2.5

— WHY IS THIS NEEDED?
Sodium Dodecyl Sulfate Capillary Electrophoresis (SDS-CE) is a quantitative alternative to gel electrophoresis (SDS-PAGE).
It separates proteins by molecular weight under denaturing conditions.
• Main Band: Target protein with correct molecular weight.
• High Molecular Weight Impurities (HMW): Dimers, oligomers, and aggregates. Critical for safety due to immunogenicity risk.
• Low Molecular Weight Impurities (LMW): Protein fragments resulting from hydrolysis or incomplete synthesis.
• The method provides high reproducibility and accurate quantification of impurities compared to gel staining.

⚠️  CRITICAL:
• Main substance purity ≥95.0% (for highly purified products often ≥98-99%).
• Aggregate content is strictly limited (≤2.0%) due to allergy risk.
• Resolution between main peak and impurities must be sufficient for integration (≥1.5).
• Sample preparation includes disulfide bond reduction and SDS denaturation.

Key features:
• Quantitative purity assessment by molecular weight.
• Control of aggregation and degradation.
• Compliance with pharmacopoeial requirements (USP <1056>, Ph.Eur. 2.2.54).
• LabWare LIMS integration.

Critical parameters:
• Main Band: ≥95.0%
• HMW (Aggregates): ≤2.0%
• LMW (Fragments): ≤3.0%
• Total Impurities: ≤5.0%
• Resolution: ≥1.5

💡 Usage tips:
1. Use standard molecular weight marker sets for size calibration.
2. SDS concentration in buffer must be above critical micelle concentration.
3. Optimization of reduction time may be required for complex proteins.
4. SDS-CE does not separate isoforms with same mass but different charge (use CIEF for that).

⚠️ Note: Unlike native CE, SDS-CE destroys the tertiary structure of the protein, so the method is suitable only for assessing chain integrity and aggregation, not native activity.

input.csv

BatchNumber,ProteinName,MainBandPercent,HMW_Impurities_Percent,LMW_Impurities_Percent,Total_Impurities_Percent,Resolution
PROT-REC-2026-001,Recombinant Human Insulin,97.5,0.5,1.2,2.5,2.5
PROT-FAIL-2026-002,rHu_Growth_Hormone,92.0,3.5,2.0,6.5,1.2

URS & FS — User Requirements and Functional Specification

This document defines the controlled interface, validation behaviour and expected output of CE_Recombinant_Protein_Purity. The document is intended to reside inside the utility folder together with input.csv and the description file. Expected executable: CE_Recombinant_Protein_Purity.exe.

Purpose: the utility performs deterministic verification of QC input data against approved limits, generates machine-readable output.json, and supports QC/QA review, LIMS/ELN/MES integration and CSV/CSA preparation.

Scope

Utility classCapillary electrophoresis
Main object/methodRecombinant Protein Purity Control (SDS-CE)
Inputinput.csv with a fixed header and controlled data types.
Outputoutput.json with PASS, WARNING, FAIL statuses, detailed checks and critical findings.
ExclusionsThe utility does not replace the approved specification, analytical procedure, OOS/OOT investigation or Qualified Person / QA release decision.

Domain limits and critical parameters

Key fragments from the source description are listed below. Before production use, limits shall be verified against the approved specification, registration dossier, current pharmacopoeial edition and local SOPs.
  • • Main Band ≥95.0%
  • • High Molecular Weight Impurities (Aggregates) ≤2.0%
  • • Low Molecular Weight Impurities (Fragments) ≤3.0%
  • • Total Impurities ≤5.0%
  • • Peak Resolution ≥1.5
  • ⚠️ CRITICAL: Protein aggregates can trigger immune responses.
  • CE_Recombinant_Protein_Purity.exe input.csv output.json → evaluate your data
  • BatchNumber,ProteinName,MainBandPercent,HMW_Impurities_Percent,LMW_Impurities_Percent,Total_Impurities_Percent,Resolution
  • • Main Band: Target protein with correct molecular weight.
  • • High Molecular Weight Impurities (HMW): Dimers, oligomers, and aggregates. Critical for safety due to immunogenicity risk.
  • • Low Molecular Weight Impurities (LMW): Protein fragments resulting from hydrolysis or incomplete synthesis.
  • • The method provides high reproducibility and accurate quantification of impurities compared to gel staining.
  • ⚠️ CRITICAL:
  • • Main substance purity ≥95.0% (for highly purified products often ≥98-99%).
  • • Aggregate content is strictly limited (≤2.0%) due to allergy risk.
  • • Resolution between main peak and impurities must be sufficient for integration (≥1.5).

Pharmacopoeial and regulatory references found in the description

#SourceNote
1Ph.Eur. 2.2.54Used as a source/context reference from the description; the current edition must be verified before implementation.
2USP <1056>Used as a source/context reference from the description; the current edition must be verified before implementation.

Production data flow

StepResponsible objectDescriptionControl
1LIMS/ELN/MES or QC analystCreates input.csv with measured values and batch identifier.Header, mandatory-field and unit checks.
2CE_Recombinant_Protein_PurityLoads CSV, converts data types, applies domain rules and produces the result.Deterministic rules; no ML/probabilistic conformance decision.
3QC reviewer / QAReviews output.json, warnings, critical deviations and source values.Review, deviation investigation and data-trail retention.
4Archive / eQMSRetains input, output, utility version, documentation and checksum.Data integrity: ALCOA+, reproducibility and change control.

URS — User Requirements Specification

IDRequirementCriticalityAcceptance criterion
URS-001The utility shall be supplied with CE_Recombinant_Protein_Purity.documentation.html in the same folder as the description and sample input.csv.MediumThe documentation file exists in the CE_Recombinant_Protein_Purity folder and opens locally in a browser.
URS-002The utility shall accept input.csv with the exact headers defined in the data contract.HighA CSV file with the correct header is processed without manual editing.
URS-003The utility shall validate mandatory fields, column count, data types and basic plausibility of values.HighSchema and conversion errors are explicitly reported.
URS-004The utility shall evaluate each critical and non-critical QC parameter against approved limits.HighEach checked parameter receives a status and explanatory message.
URS-005The utility shall produce a final record/batch status: PASS, WARNING or FAIL.HighA critical deviation causes FAIL; a non-critical deviation causes WARNING.
URS-006The utility shall generate output.json suitable for LIMS/ELN/MES integration and QA/QC review.HighJSON contains source values, rules, statuses, warnings and critical findings.
URS-007The utility shall preserve traceability between batch identifier, input values, applied rules and final status.HighThe output contains the batch/row identifier and list of checked parameters.
URS-008The utility shall not use machine learning or probabilistic interpretation for conformance decisions.MediumThe result is reproducible and based on explicit rules, thresholds and input values.
URS-009The utility shall support the CLI scenario: CE_Recombinant_Protein_Purity.exe input.csv output.json.HighWith valid arguments, output.json is created; on error, a diagnostic message is returned.
URS-010The documentation shall support IQ/OQ/PQ or equivalent CSV/CSA verification.MediumThe document contains URS, FS, CSV contract, rules, test scenarios and traceability.
URS-011The utility shall distinguish data errors, method warnings and critical specification failures.Highoutput.json provides separate structures/fields for errors, warnings and critical findings.
URS-012The utility shall support archival retention of unchanged input and output data.Mediuminput.csv and output.json can be retained as a batch record or OQ/PQ evidence.

input.csv contract

#FieldTypeSamplePurpose
1BatchNumberstringPROT-REC-2026-001Batch or lot identifier used for traceability.
2ProteinNamestringRecombinant Human InsulinControlled input parameter used by the deterministic QC rules.
3MainBandPercentdecimal97.5Controlled input parameter used by the deterministic QC rules.
4HMW_Impurities_Percentdecimal0.5Specified, unspecified or total impurity parameter controlled against an approved limit.
5LMW_Impurities_Percentdecimal1.2Specified, unspecified or total impurity parameter controlled against an approved limit.
6Total_Impurities_Percentdecimal2.5Specified, unspecified or total impurity parameter controlled against an approved limit.
7Resolutiondecimal2.5Controlled input parameter used by the deterministic QC rules.
BatchNumber,ProteinName,MainBandPercent,HMW_Impurities_Percent,LMW_Impurities_Percent,Total_Impurities_Percent,Resolution
PROT-REC-2026-001,Recombinant Human Insulin,97.5,0.5,1.2,2.5,2.5
PROT-FAIL-2026-002,rHu_Growth_Hormone,92.0,3.5,2.0,6.5,1.2

Input validation rules

IDFieldTypeCheckCriticality
VR-001BatchNumberstringnot empty; unique within file where applicableMedium
VR-002ProteinNamestringnot empty where mandatoryMedium
VR-003MainBandPercentdecimalparse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved % limitMedium
VR-004HMW_Impurities_Percentdecimalparse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved % limitMedium
VR-005LMW_Impurities_Percentdecimalparse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved % limitMedium
VR-006Total_Impurities_Percentdecimalparse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved % limitMedium
VR-007Resolutiondecimalparse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved numerical limitMedium

FS — Functional Specification

IDFunctionImplementationURS link
FS-001Local HTML documentationProvide a bilingual CE_Recombinant_Protein_Purity.documentation.html file with RU/EN switch, source description, URS, FS, contracts and tests.URS-001, URS-010
FS-002CSV importRead input.csv in UTF-8/CSV-compatible format and identify the header row and data records.URS-002, URS-009
FS-003Schema validationCompare actual columns against the expected contract; missing key fields are recorded as schema errors.URS-002, URS-003
FS-004Type conversionConvert decimal, flag/boolean and controlled string values. Invalid values are recorded at row and field level.URS-003
FS-005Domain rule engineApply rules for CE Recombinant Protein Purity, including critical limits from the description and approved specification.URS-004, URS-008
FS-006Status aggregationAggregate parameter statuses: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance.URS-005, URS-011
FS-007JSON exportWrite output.json with utility identifier, source values, check results, warnings and critical findings.URS-006, URS-007
FS-008Error handlingSeparate execution errors, schema errors, conversion errors and domain-limit failures.URS-003, URS-011
FS-009Audit supportKeep result structure suitable for review, OOS/OOT investigation, calculation reproduction and inspection discussion.URS-007, URS-012
FS-010Integration contractSupport the standard scenario: LIMS/ELN/MES creates input.csv, the utility returns output.json, and the portal displays description and documentation.URS-006, URS-009
FS-011Configuration/change controlAny change to limits, column names or rule logic requires versioning, review, regression tests and documentation update.URS-010, URS-012
FS-012Data integrityDo not modify the source input.csv; save results separately in output.json for archival retention.URS-007, URS-012

Example output.json structure

{
  "utilityId": "ce-recombinant-protein-purity",
  "utilityName": "CE_Recombinant_Protein_Purity",
  "object": "CE Recombinant Protein Purity",
  "overallStatus": "PASS|WARNING|FAIL",
  "sourceFile": "input.csv",
  "recordCount": 2,
  "checks": [
    {
      "parameter": "BatchNumber",
      "value": "PROT-REC-2026-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-001"
    },
    {
      "parameter": "ProteinName",
      "value": "Recombinant Human Insulin",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-002"
    },
    {
      "parameter": "MainBandPercent",
      "value": "97.5",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-003"
    },
    {
      "parameter": "HMW_Impurities_Percent",
      "value": "0.5",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-004"
    },
    {
      "parameter": "LMW_Impurities_Percent",
      "value": "1.2",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-005"
    },
    {
      "parameter": "Total_Impurities_Percent",
      "value": "2.5",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-006"
    },
    {
      "parameter": "Resolution",
      "value": "2.5",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-007"
    }
  ],
  "criticalFindings": [],
  "warnings": [],
  "metadata": {
    "executionMode": "CLI",
    "interface": "CSV to JSON",
    "documentationFile": "CE_Recombinant_Protein_Purity.documentation.html"
  }
}

Traceability matrix URS → FS → OQ/PQ

URSFSVerificationExpected result
URS-001FS-001Check that CE_Recombinant_Protein_Purity.documentation.html exists in the utility folder.The file exists, opens, and the RU/EN switch works.
URS-002/003FS-002/003/004Run the utility with a correct CSV, a CSV missing a mandatory column and a CSV with an invalid data type.Correct CSV is processed; schema and type errors are explicit.
URS-004/005FS-005/006Submit values within limits, at warning level and beyond a critical limit.PASS, WARNING and FAIL are produced according to rules.
URS-006/007FS-007/009/012Verify output.json structure and batch traceability.JSON contains batch identifier, values, rules, statuses and critical findings.
URS-008FS-005Repeat execution with the same input.csv.The result is identical; no probabilistic behaviour is present.
URS-009/010/012FS-010/011/012Execute the CLI scenario and archive input/output/version.Artefacts are suitable for OQ/PQ and change-control records.

OQ/PQ test scenarios

IDScenarioInput dataExpected result
OQ-001Positive pathSample CSV with valid values.output.json is created; final status is PASS or acceptable WARNING according to rules.
OQ-002Mandatory column missingRemove one key column from the header.Schema error; the row shall not be treated as passed.
OQ-003Invalid typePut text into a numeric field.Type-conversion error with field and row identification.
OQ-004Critical limitCritical parameter value outside the approved limit.FAIL and an entry in criticalFindings.
OQ-005WarningNon-critical deviation or unknown controlled category.WARNING without hiding the source value.
PQ-001User real batchReal input.csv from the QC process.Reviewed result with input.csv, output.json, version and checksum retained.

QA/QC, CSV/CSA and change control

  • Do not rename columns without updating the validator, test set and documentation.
  • Retain input.csv, output.json, executable version, checksum and a copy of the documentation.
  • Before production use, perform IQ/OQ/PQ or equivalent risk-based CSV/CSA verification.
  • Critical limits shall be approved by the process owner and verified against the registration dossier, pharmacopoeia and local SOPs.
  • Any change to rules, thresholds or status interpretation shall go through change control and regression testing.

Included in packages

Biopharmaceuticals Extended QC Suite

Extended QC utility coverage for mAbs, biosimilars, proteins, insulins, vaccines, mRNA/LNP, HCP, sterile release, microbiology, water, cleanroom and stability workflows.

Open

Diabetes QC Suite

QC package for diabetes medicines: insulins, metformin, SGLT2/DPP-4/GLP-1 products, glucagon and supporting dosage-form quality checks.

Open

Endocrinology QC Suite

QC package for endocrinology: thyroid, pituitary/peptide hormones, corticosteroids, sex hormones and selected metabolic medicines.

Open

Immunology QC Suite

QC utility package for immunology: monoclonal antibodies, biosimilars, immunomodulators, immunosuppressants, ELISA/SPR, HCP, protein characterization, sterility and pyrogen/release checks.

Open

Lumex QC Suite

A single Lumex package combining the former Lumex and Lumex2 sets: instrumental and general pharmaceutical QC, AAS/ICP, CE, HPLC, NIR/PAT, stability, dissolution, content uniformity, system suitability and statistical control.

Open