CE_Peptide_Map_Validator

CE Peptide Map Validator

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

Utility description: CE Peptide Map Validator

CE Peptide Map Validator — Peptide Mapping Validation (CE/HPLC)

ℹ️ Utility compares sample peptide map with reference:
• Sequence coverage ≥95.0%
• Peptide count (±2 from expected)
• Missing peak area ≤1.0%
• Max time shift ≤0.5 min
• Identity score ≥90

⚠️ CRITICAL: Peptide mapping is the primary method for primary structure confirmation.
Allows detection of deamidation, oxidation, and splicing/cleavage errors.

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

Input format:
BatchNumber,ProteinName,CoveragePercent,DetectedCount,ExpectedCount,MissingAreaPercent,MaxRtShift,IdentityScore

Example:
MAB-PM-2026-001,Trastuzumab,98.5,42,43,0.2,0.15,98.0

— WHY IS THIS NEEDED?
Peptide Mapping is a "fingerprint" method for protein drugs.
The protein is enzymatically digested (usually with trypsin) into peptides, which are then separated by CE or HPLC.
• Identity Confirmation: Peptide map must exactly match the theoretical sequence map.
• Detection of Post-Translational Modifications (PTMs): Peak shift may indicate deamidation, oxidation, glycation.
• Processing Control: Missing or new peaks may indicate incorrect folding or signal peptide cleavage.
• For Biosimilars: Comparison with reference product to prove structural similarity.

⚠️ CRITICAL:
• Sequence coverage must be maximal (>95%) to ensure verification of the entire molecule.
• Any missing or new peaks must be investigated.
• Migration/Retention time shift beyond tolerance indicates change in charge or hydrophobicity (modification).
• Method requires high system reproducibility (system suitability).

Key features:
• Automated comparison with reference profile.
• Assessment of amino acid sequence coverage.
• Detection of anomalies in peptide profile.
• LabWare LIMS integration.

Critical parameters:
• Sequence coverage: ≥95.0%
• Peptide count: Expected ± 2
• Missing peak area: ≤1.0%
• Max time shift (RT): ≤0.5 min
• Identity score (Match Score): ≥90

💡 Usage tips:
1. Use standard digestion protocol (trypsin) for reproducibility.
2. For CE, coated capillaries are often used for separating complex peptide mixtures.
3. Regularly calibrate the system with a standard peptide set.
4. If a new peak is detected, perform mass spectrometry identification (LC-MS/MS).

⚠️ Note: Peptide mapping is the most specific identity test for complex proteins, superior to conventional methods (SEC, UV).

input.csv

BatchNumber,ProteinName,CoveragePercent,DetectedCount,ExpectedCount,MissingAreaPercent,MaxRtShift,IdentityScore
MAB-PM-2026-001,Trastuzumab,98.5,42,43,0.2,0.15,98.0
MAB-FAIL-2026-002,Insulin Analog,85.0,28,30,2.5,0.8,82.0

URS & FS — User Requirements and Functional Specification

This document defines the controlled interface, validation behaviour and expected output of CE_Peptide_Map_Validator. The document is intended to reside inside the utility folder together with input.csv and the description file. Expected executable: CE_Peptide_Map_Validator.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 class	Capillary electrophoresis
Main object/method	Peptide Mapping Validation (CE/HPLC)
Input	`input.csv` with a fixed header and controlled data types.
Output	`output.json` with `PASS`, `WARNING`, `FAIL` statuses, detailed checks and critical findings.
Exclusions	The 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.

• Sequence coverage ≥95.0%
• Peptide count (±2 from expected)
• Missing peak area ≤1.0%
• Max time shift ≤0.5 min
• Identity score ≥90
⚠️ CRITICAL: Peptide mapping is the primary method for primary structure confirmation.
CE_Peptide_Map_Validator.exe input.csv output.json → evaluate your data
BatchNumber,ProteinName,CoveragePercent,DetectedCount,ExpectedCount,MissingAreaPercent,MaxRtShift,IdentityScore
• Identity Confirmation: Peptide map must exactly match the theoretical sequence map.
• Detection of Post-Translational Modifications (PTMs): Peak shift may indicate deamidation, oxidation, glycation.
• Processing Control: Missing or new peaks may indicate incorrect folding or signal peptide cleavage.
• For Biosimilars: Comparison with reference product to prove structural similarity.
⚠️ CRITICAL:
• Sequence coverage must be maximal (>95%) to ensure verification of the entire molecule.
• Any missing or new peaks must be investigated.
• Migration/Retention time shift beyond tolerance indicates change in charge or hydrophobicity (modification).

Production data flow

Step	Responsible object	Description	Control
1	LIMS/ELN/MES or QC analyst	Creates `input.csv` with measured values and batch identifier.	Header, mandatory-field and unit checks.
2	CE_Peptide_Map_Validator	Loads CSV, converts data types, applies domain rules and produces the result.	Deterministic rules; no ML/probabilistic conformance decision.
3	QC reviewer / QA	Reviews `output.json`, warnings, critical deviations and source values.	Review, deviation investigation and data-trail retention.
4	Archive / eQMS	Retains input, output, utility version, documentation and checksum.	Data integrity: ALCOA+, reproducibility and change control.

URS — User Requirements Specification

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

input.csv contract

#	Field	Type	Sample	Purpose
1	`BatchNumber`	string	`MAB-PM-2026-001`	Batch or lot identifier used for traceability.
2	`ProteinName`	string	`Trastuzumab`	Controlled input parameter used by the deterministic QC rules.
3	`CoveragePercent`	decimal	`98.5`	Controlled input parameter used by the deterministic QC rules.
4	`DetectedCount`	decimal	`42`	Controlled input parameter used by the deterministic QC rules.
5	`ExpectedCount`	decimal	`43`	Controlled input parameter used by the deterministic QC rules.
6	`MissingAreaPercent`	decimal	`0.2`	Peak area or ratio used for quantification and comparison.
7	`MaxRtShift`	decimal	`0.15`	Controlled input parameter used by the deterministic QC rules.
8	`IdentityScore`	string	`98.0`	Controlled input parameter used by the deterministic QC rules.

BatchNumber,ProteinName,CoveragePercent,DetectedCount,ExpectedCount,MissingAreaPercent,MaxRtShift,IdentityScore
MAB-PM-2026-001,Trastuzumab,98.5,42,43,0.2,0.15,98.0
MAB-FAIL-2026-002,Insulin Analog,85.0,28,30,2.5,0.8,82.0

Input validation rules

ID	Field	Type	Check	Criticality
VR-001	`BatchNumber`	string	not empty; unique within file where applicable	Medium
VR-002	`ProteinName`	string	not empty where mandatory	Medium
VR-003	`CoveragePercent`	decimal	parse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved % limit	Medium
VR-004	`DetectedCount`	decimal	parse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved numerical limit	Medium
VR-005	`ExpectedCount`	decimal	parse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved numerical limit	Medium
VR-006	`MissingAreaPercent`	decimal	parse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved % limit	Medium
VR-007	`MaxRtShift`	decimal	parse as invariant decimal; finite value; no NaN/Infinity; evaluate against approved numerical limit	Medium
VR-008	`IdentityScore`	string	not empty where mandatory	Medium

FS — Functional Specification

ID	Function	Implementation	URS link
FS-001	Local HTML documentation	Provide a bilingual `CE_Peptide_Map_Validator.documentation.html` file with RU/EN switch, source description, URS, FS, contracts and tests.	URS-001, URS-010
FS-002	CSV import	Read `input.csv` in UTF-8/CSV-compatible format and identify the header row and data records.	URS-002, URS-009
FS-003	Schema validation	Compare actual columns against the expected contract; missing key fields are recorded as schema errors.	URS-002, URS-003
FS-004	Type conversion	Convert decimal, flag/boolean and controlled string values. Invalid values are recorded at row and field level.	URS-003
FS-005	Domain rule engine	Apply rules for CE Peptide Map Validator, including critical limits from the description and approved specification.	URS-004, URS-008
FS-006	Status aggregation	Aggregate parameter statuses: `FAIL` for critical failure, `WARNING` for non-critical deviation, `PASS` for conformance.	URS-005, URS-011
FS-007	JSON export	Write `output.json` with utility identifier, source values, check results, warnings and critical findings.	URS-006, URS-007
FS-008	Error handling	Separate execution errors, schema errors, conversion errors and domain-limit failures.	URS-003, URS-011
FS-009	Audit support	Keep result structure suitable for review, OOS/OOT investigation, calculation reproduction and inspection discussion.	URS-007, URS-012
FS-010	Integration contract	Support 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-011	Configuration/change control	Any change to limits, column names or rule logic requires versioning, review, regression tests and documentation update.	URS-010, URS-012
FS-012	Data integrity	Do 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-peptide-map-validator",
  "utilityName": "CE_Peptide_Map_Validator",
  "object": "CE Peptide Map Validator",
  "overallStatus": "PASS|WARNING|FAIL",
  "sourceFile": "input.csv",
  "recordCount": 2,
  "checks": [
    {
      "parameter": "BatchNumber",
      "value": "MAB-PM-2026-001",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-001"
    },
    {
      "parameter": "ProteinName",
      "value": "Trastuzumab",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-002"
    },
    {
      "parameter": "CoveragePercent",
      "value": "98.5",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-003"
    },
    {
      "parameter": "DetectedCount",
      "value": "42",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-004"
    },
    {
      "parameter": "ExpectedCount",
      "value": "43",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-005"
    },
    {
      "parameter": "MissingAreaPercent",
      "value": "0.2",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-006"
    },
    {
      "parameter": "MaxRtShift",
      "value": "0.15",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-007"
    },
    {
      "parameter": "IdentityScore",
      "value": "98.0",
      "status": "PASS|WARNING|FAIL",
      "message": "Rule-based check result",
      "ruleReference": "VR-008"
    }
  ],
  "criticalFindings": [],
  "warnings": [],
  "metadata": {
    "executionMode": "CLI",
    "interface": "CSV to JSON",
    "documentationFile": "CE_Peptide_Map_Validator.documentation.html"
  }
}

Traceability matrix URS → FS → OQ/PQ

URS	FS	Verification	Expected result
URS-001	FS-001	Check that `CE_Peptide_Map_Validator.documentation.html` exists in the utility folder.	The file exists, opens, and the RU/EN switch works.
URS-002/003	FS-002/003/004	Run 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/005	FS-005/006	Submit values within limits, at warning level and beyond a critical limit.	`PASS`, `WARNING` and `FAIL` are produced according to rules.
URS-006/007	FS-007/009/012	Verify `output.json` structure and batch traceability.	JSON contains batch identifier, values, rules, statuses and critical findings.
URS-008	FS-005	Repeat execution with the same `input.csv`.	The result is identical; no probabilistic behaviour is present.
URS-009/010/012	FS-010/011/012	Execute the CLI scenario and archive input/output/version.	Artefacts are suitable for OQ/PQ and change-control records.

OQ/PQ test scenarios

ID	Scenario	Input data	Expected result
OQ-001	Positive path	Sample CSV with valid values.	`output.json` is created; final status is `PASS` or acceptable `WARNING` according to rules.
OQ-002	Mandatory column missing	Remove one key column from the header.	Schema error; the row shall not be treated as passed.
OQ-003	Invalid type	Put text into a numeric field.	Type-conversion error with field and row identification.
OQ-004	Critical limit	Critical parameter value outside the approved limit.	`FAIL` and an entry in `criticalFindings`.
OQ-005	Warning	Non-critical deviation or unknown controlled category.	`WARNING` without hiding the source value.
PQ-001	User real batch	Real `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

Gastroenterology QC Suite

QC package for gastroenterology: PPIs, antiemetics, prokinetics, IBD medicines, laxatives, enzymes and GI anti-infectives.

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

Radiology QC Suite

QC package for radiology and diagnostic imaging: radiopharmaceuticals, PET/SPECT, contrast media, iodinated and gadolinium products, plus particle, sterility and endotoxin checks.

Open