Utility description: System Suitability Parameters Checker
System Suitability Parameters Checker — Chromatography System Suitability Test
ℹ️ Utility checks critical System Suitability Test (SST) parameters per USP <621> / Ph. Eur. 2.2.46:
• Column Efficiency (N): ≥2000 theoretical plates
• Tailing Factor (T): ≤2.0
• Resolution (Rs): ≥1.5
• Precision (RSD of areas): ≤2.0%
⚠️ CRITICAL: If SST fails, sample analysis results are INVALID!
This is a primary GMP and pharmacopoeial requirement before starting an analysis series.
Usage:
System_Suitability_Parameters_Checker.exe → demo mode (console output)
System_Suitability_Parameters_Checker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,TheoreticalPlates,TailingFactor,Resolution,RSD_Area,CapacityFactor
Example:
SST-HPLC-2026-001,5500,1.1,2.5,0.8,3.5
— WHY IS THIS NEEDED?
System Suitability Test (SST) confirms that the chromatographic system is functioning correctly at the time of analysis.
• SST parameters integrate characteristics of the instrument, reagents, column, and operator.
• USP <621> and Ph. Eur. 2.2.46 require passing SST before sample injection.
• Key parameters: efficiency (N), peak symmetry (T), resolution (Rs), and repeatability (RSD).
• Automatic SST check prevents wasting time on analyzing invalid batches and ensures data integrity.
⚠️ CRITICAL:
• N (Efficiency): Decrease in N indicates column degradation or poor packing.
• T (Tailing): High T (>2.0) leads to integration errors and worse resolution.
• Rs (Resolution): Rs < 1.5 means incomplete peak separation, critical for impurity quantification.
• RSD (Precision): High RSD (>2.0%) indicates problems with pump, autosampler, or detector.
Key features:
• Comprehensive check of all main SST parameters.
• Compliance with USP <621> and Ph. Eur. 2.2.46 requirements.
• Generation of clear PASS/FAIL status to block invalid data.
Critical parameters:
• Theoretical Plates (N): >= 2000
• Tailing Factor (T): <= 2.0
• Resolution (Rs): >= 1.5
• RSD (%): <= 2.0
💡 Usage tips:
1. Run SST standard at the beginning of each analysis series and periodically during long series.
2. If SST fails, check for leaks, mobile phase degassing, and column condition.
3. Use fresh standard solutions for RSD check.
4. Monitor SST parameter trends over time for predictive column maintenance.
5. Configure autosampler to stop automatically upon SST failure.
⚠️ Note: SST parameters are method-specific. This utility uses general pharmacopoeial limits, but in a real laboratory, they must be adjusted for specific monographs or validated methods.
input.csv
BatchNumber,N,Tailing,Resolution,RSD,CapacityFactor
SST-HPLC-2026-001,5500,1.1,2.5,0.8,3.5
SST-HPLC-2026-002,2100,1.8,1.6,1.9,2.1
SST-FAIL-2026-003,1500,2.5,1.2,3.5,1.5
Utility description
System Suitability Parameters Checker — Chromatography System Suitability Test
ℹ️ Utility checks critical System Suitability Test (SST) parameters per USP <621> / Ph. Eur. 2.2.46:
• Column Efficiency (N): ≥2000 theoretical plates
• Tailing Factor (T): ≤2.0
• Resolution (Rs): ≥1.5
• Precision (RSD of areas): ≤2.0%
⚠️ CRITICAL: If SST fails, sample analysis results are INVALID!
This is a primary GMP and pharmacopoeial requirement before starting an analysis series.
Usage:
System_Suitability_Parameters_Checker.exe → demo mode (console output)
System_Suitability_Parameters_Checker.exe input.csv output.json → evaluate your data
Input format:
BatchNumber,TheoreticalPlates,TailingFactor,Resolution,RSD_Area,CapacityFactor
Example:
SST-HPLC-2026-001,5500,1.1,2.5,0.8,3.5
— WHY IS THIS NEEDED?
System Suitability Test (SST) confirms that the chromatographic system is functioning correctly at the time of analysis.
• SST parameters integrate characteristics of the instrument, reagents, column, and operator.
• USP <621> and Ph. Eur. 2.2.46 require passing SST before sample injection.
• Key parameters: efficiency (N), peak symmetry (T), resolution (Rs), and repeatability (RSD).
• Automatic SST check prevents wasting time on analyzing invalid batches and ensures data integrity.
⚠️ CRITICAL:
• N (Efficiency): Decrease in N indicates column degradation or poor packing.
• T (Tailing): High T (>2.0) leads to integration errors and worse resolution.
• Rs (Resolution): Rs < 1.5 means incomplete peak separation, critical for impurity quantification.
• RSD (Precision): High RSD (>2.0%) indicates problems with pump, autosampler, or detector.
Key features:
• Comprehensive check of all main SST parameters.
• Compliance with USP <621> and Ph. Eur. 2.2.46 requirements.
• Generation of clear PASS/FAIL status to block invalid data.
Critical parameters:
• Theoretical Plates (N): >= 2000
• Tailing Factor (T): <= 2.0
• Resolution (Rs): >= 1.5
• RSD (%): <= 2.0
💡 Usage tips:
1. Run SST standard at the beginning of each analysis series and periodically during long series.
2. If SST fails, check for leaks, mobile phase degassing, and column condition.
3. Use fresh standard solutions for RSD check.
4. Monitor SST parameter trends over time for predictive column maintenance.
5. Configure autosampler to stop automatically upon SST failure.
⚠️ Note: SST parameters are method-specific. This utility uses general pharmacopoeial limits, but in a real laboratory, they must be adjusted for specific monographs or validated methods.
URS & FS — User Requirements and Functional Specification
This document describes the controlled interface, user requirements and functional behaviour of System_Suitability_Parameters_Checker. The utility is intended for automated verification of laboratory, pharmacopoeial, analytical or manufacturing QC parameters using input.csv and producing a structured output.json result.
Domain limits and critical parameters
Before production use, all limits must be verified against the approved specification, registration dossier, pharmacopoeial monograph, validated method and local SOPs.
- • SST parameters integrate characteristics of the instrument, reagents, column, and operator.
- • USP <621> and Ph. Eur. 2.2.46 require passing SST before sample injection.
- • Key parameters: efficiency (N), peak symmetry (T), resolution (Rs), and repeatability (RSD).
- • Automatic SST check prevents wasting time on analyzing invalid batches and ensures data integrity.
- • N (Efficiency): Decrease in N indicates column degradation or poor packing.
- • T (Tailing): High T (>2.0) leads to integration errors and worse resolution.
- • Rs (Resolution): Rs < 1.5 means incomplete peak separation, critical for impurity quantification.
- • RSD (Precision): High RSD (>2.0%) indicates problems with pump, autosampler, or detector.
- • Comprehensive check of all main SST parameters.
- • Compliance with USP <621> and Ph. Eur. 2.2.46 requirements.
- • Generation of clear PASS/FAIL status to block invalid data.
- • Theoretical Plates (N): >= 2000
- • Tailing Factor (T): <= 2.0
- • Resolution (Rs): >= 1.5
- • RSD (%): <= 2.0
- • Column Efficiency (N): ≥2000 theoretical plates
URS — User Requirements Specification
| ID | Requirement | Criticality | Acceptance criterion |
| URS-001 | The utility shall accept an input.csv file with exact headers defined in the data contract. | High | The file is processed without manual header editing. |
| URS-002 | The utility shall perform deterministic evaluation for System Suitability Parameters Checker using input values, approved limits and domain rules. | High | Each row receives a PASS / WARNING / FAIL status. |
| URS-003 | The utility shall validate mandatory fields, data types, numeric ranges, units and domain plausibility. | High | Schema, format and conversion errors are explicitly reported. |
| URS-004 | The utility shall identify critical deviations for parameters stated in the method description and specification. | High | A critical deviation causes FAIL or a dedicated critical finding. |
| URS-005 | The utility shall generate output.json with machine-readable results, source values, warnings and failures. | High | JSON is suitable for LIMS/ELN/MES integration, QA/QC review and archival. |
| URS-006 | The result shall not depend on machine learning or undocumented heuristics. | Medium | All decisions are based on explicit rules, thresholds and input values. |
| URS-007 | The system shall preserve traceability between batch/sample, input data, applied rules and final status. | High | The output contains the batch/sample identifier and checked parameters. |
| URS-008 | The documentation shall support IQ/OQ/PQ preparation and inspection discussion. | Medium | URS, FS, CSV/JSON contract and test scenarios are supplied with the utility. |
| URS-009 | The utility shall support batch processing of multiple input.csv rows. | Medium | Each row is evaluated independently; errors in one row do not mask errors in others. |
| URS-010 | The utility shall support a simple operating model: demo mode and execution with input/output files. | Medium | The CLI scenario is reproducible in test and production environments. |
input.csv contract
| # | Field | Type | Sample | Purpose |
|---|
| 1 | BatchNumber | string | SST-HPLC-2026-001 | Batch or lot identifier used for traceability, review and deviation investigation. |
| 2 | N | string / decimal | 5500 | Controlled input parameter used by deterministic QC rules and traceable result generation. |
| 3 | Tailing | string / decimal | 1.1 | Controlled input parameter used by deterministic QC rules and traceable result generation. |
| 4 | Resolution | string / decimal | 2.5 | Controlled input parameter used by deterministic QC rules and traceable result generation. |
| 5 | RSD | decimal | 0.8 | Relative standard deviation; precision metric for the process or analytical method. |
| 6 | CapacityFactor | string / decimal | 3.5 | Controlled input parameter used by deterministic QC rules and traceable result generation. |
BatchNumber,N,Tailing,Resolution,RSD,CapacityFactor
SST-HPLC-2026-001,5500,1.1,2.5,0.8,3.5
SST-HPLC-2026-002,2100,1.8,1.6,1.9,2.1
SST-FAIL-2026-003,1500,2.5,1.2,3.5,1.5
FS — Functional Specification
| ID | Function | Implementation |
| FS-001 | CSV import | Read input.csv in UTF-8/CSV-compatible format and validate the header and expected columns. |
| FS-002 | Schema validation | Check mandatory fields, column count, critical missing values and row structure. |
| FS-003 | Type conversion | Convert numeric, flag and text values; invalid formats are recorded as row-level errors. |
| FS-004 | Domain rule engine | Apply domain rules for System Suitability Parameters Checker, including limits from the utility description and approved specification. |
| FS-005 | Status aggregation | Produce final status: FAIL for critical failure, WARNING for non-critical deviation, PASS for conformance. |
| FS-006 | JSON export | Write output.json with detailed checks, source values, warnings, failures and critical findings. |
| FS-007 | Audit support | Keep the result structure suitable for review, deviation investigation, calculation reproduction and IQ/OQ/PQ preparation. |
| FS-008 | Integration contract | Support the production scenario: LIMS/ELN/MES creates input.csv, the utility returns output.json, and the portal displays description and documentation. |
| FS-009 | Error handling | Report errors unambiguously and do not substitute missing values with calculated values unless the rule is explicitly defined. |
| FS-010 | Version control support | Document the utility version, input contract, executable checksum and rule application date. |
Example output.json
{
"utilityId": "system-suitability-parameters-checker",
"utilityName": "System_Suitability_Parameters_Checker",
"overallStatus": "PASS|WARNING|FAIL",
"sourceFile": "input.csv",
"checks": [
{
"parameter": "BatchNumber",
"value": "SST-HPLC-2026-001",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "N",
"value": "5500",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Tailing",
"value": "1.1",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "Resolution",
"value": "2.5",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "RSD",
"value": "0.8",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
},
{
"parameter": "CapacityFactor",
"value": "3.5",
"status": "PASS|WARNING|FAIL",
"message": "Rule-based check result"
}
],
"criticalFindings": [],
"warnings": [],
"generatedFor": "QA/QC review and LIMS integration"
}
Traceability matrix
| URS | FS | OQ/PQ coverage |
|---|
| URS-001, URS-003 | FS-001, FS-002, FS-003 | OQ-001/OQ-002/OQ-003 |
| URS-002, URS-004 | FS-004, FS-005 | OQ-004/PQ-001 |
| URS-005, URS-007 | FS-006, FS-007 | OQ-005/PQ-002 |
| URS-008, URS-010 | FS-008, FS-010 | IQ-001/OQ-006 |
OQ/PQ test scenarios
| ID | Scenario | Expected result |
|---|
| OQ-001 | Valid sample row | PASS or acceptable WARNING according to the rules. |
| OQ-002 | Mandatory column missing | Schema error or FAIL. |
| OQ-003 | Non-numeric value in numeric field | Type-conversion error. |
| OQ-004 | Critical parameter outside limit | FAIL and critical finding. |
| OQ-005 | Multiple rows with different statuses | Independent row-level evaluation. |
| PQ-001 | User real batch/sample | Reviewed result with retained input/output files. |
QA/QC and change control
- Do not rename columns without updating the validator, documentation and test set.
- Retain
input.csv, output.json, executable version, documentation and checksum. - Before production use, perform IQ/OQ/PQ or equivalent CSV/CSA verification.
- Critical limits must be verified against the approved specification, local SOPs and registration dossier.