Skip to content

URS-PAR-001: Parameter Management

Property Value
ID URS-PAR-001
Version 1.0
Status Draft
Bounded Context Cross-cutting (Parameters)
Author
Approved By
Date

BR Traceability

URS Requirement Business Requirement arc42 Reference
URS-PAR-001.1 BR-05 arc42/01 s1.1
URS-PAR-001.2 BR-05 arc42/06 s6.5
URS-PAR-001.3 BR-05 arc42/12 - Glossary
URS-PAR-001.4 BR-05, BR-01 arc42/06 s6.2
URS-PAR-001.5 BR-05 arc42/06 s6.5

Scope

Parameter management handles equipment-specific configurations that are linked to product versions. Each parameter type represents a different equipment category (gripper, conveyor, vision system, etc.). Setups contain the configuration, and mappings link setups to specific product versions.

Requirements

URS-PAR-001.1: Setup CRUD Operations

Description: The system shall support CRUD operations for setup configurations per parameter type and product version.

Acceptance Criteria: - Create setup with parameter-type-specific fields (e.g., process name, row mirroring for TH) - Retrieve setups by UID or by version - Update setup fields with CRC recalculation - Delete setup by UID - Each parameter type has its own setup structure

GxP Relevance: Direct Risk Class: Medium

URS-PAR-001.2: Mapping CRUD Operations

Description: The system shall support CRUD operations for parameter mappings linking setups to product versions.

Acceptance Criteria: - Create mapping linking a setup to a product version with parameter-type-specific values - Retrieve mappings by setup UID or version UID - Update mapping values with CRC recalculation - Delete mapping by UID

GxP Relevance: Direct Risk Class: Medium

URS-PAR-001.3: Support 15+ Parameter Types

Description: The system shall support all equipment parameter types used in the microfactory.

Acceptance Criteria: - Supported types: TH, SC, EGP, RFL, XGX, IV3, Kann, HP, ES, CMMT, CL, EL, GJ, MF, Process, MfProcess, Unspecified - Each type has its own setup and mapping structure - All types follow the same CRUD interface pattern (generic repository — see ADR-007) - New parameter types can be added without changing existing code

GxP Relevance: Direct Risk Class: Medium

URS-PAR-001.4: Cascading Delete on Version/Product Deletion

Description: When a product version or product is deleted, all associated parameter mappings across all types shall be deleted.

Acceptance Criteria: - Deleting a version removes all mappings for that version across all 15+ parameter types - Deleting a product cascades through versions to mappings - Deletion is transactional (all-or-nothing) - No orphaned mapping records remain

GxP Relevance: Direct Risk Class: High

URS-PAR-001.5: Retrieve All Mappings for a Version

Description: The system shall retrieve all parameter mappings for a given product version across all parameter types in a single operation.

Acceptance Criteria: - Single request returns mappings for all parameter types - Parallel queries to all 15+ repositories for performance - Response grouped by parameter type - Response time < 1000ms (see QS-P4)

GxP Relevance: Indirect Risk Class: Low

References