Versioning & Conformance

Robot Versioning

Each robot has a version number that increments with non-conformant changes.

Version Numbering

1.0: Robot activated (original configuration)
2.0: First non-conformant change
3.0: Second non-conformant change
And so on…

What Triggers Version Increment

Action	Version Change	Variant Created
Robot activated	Starts at 1.0	No
Swap same component type	No change	No
Add new component	+1.0	Yes
Remove component	+1.0	Yes
Swap different component type	+1.0	Yes

Example Timeline

Robot: "Alpha" (ROB-2025-00142)

Jan 1:  Activated with AMR-v3.0
        Version: 1.0
        Config: AMR-v3.0 (100% conformant)

Feb 15: Battery swapped (same model, different SN)
        Version: 1.0 (no change - conformant maintenance)
        Config: AMR-v3.0 (100% conformant)

Mar 10: LiDAR upgraded to VLP-32 (different model)
        Version: 2.0 (non-conformant change)
        Config: AMR-v3.0-Var-1 (87% conformant)

Apr 5:  Added ultrasonic sensors
        Version: 3.0 (non-conformant change)
        Config: AMR-v3.0-Var-2 (78% conformant)

Conformance

Conformance measures how closely a robot matches its original Build Configuration, expressed as a percentage.

How It’s Calculated

Botbit compares the robot’s current components to the components defined in its original BC (not current variant):

Conformance % = (Matching Components / Total Current Components) × 100

Example:

Original BC: 10 components defined
Current Robot: 11 components installed (1 added, 1 swapped to different type)
Matching: 8 components match original BC
Conformance: 8 / 11 = 73%

Conformance States

Conformance	Meaning
100%	Perfect match to original design
90-99%	Minor deviation (1-2 changes)
75-89%	Moderate deviation (several changes)
< 75%	Significant deviation (many changes)

What Affects Conformance

Conformant Changes (don’t reduce conformance):

✅ Swap Battery 1.0 (SN: ABC-123) → Battery 1.0 (SN: DEF-456)
✅ Replace any component with identical type

Non-Conformant Changes (reduce conformance):

❌ Swap Battery 1.0 → Battery 2.0 (different model)
❌ Add component not in original BC
❌ Remove component from original BC
❌ Change subassembly to different type

Conformance Detail View

Robot detail page shows breakdown:

Current Configuration: AMR-v3.0-Var-1
Original Build Config: AMR-v3.0
Conformance: 87%

Conformant Components (8):
├── ✅ Jetson Xavier NX (SN: JX-2024-00142)
├── ✅ RoboClaw 2x30A (SN: RC-2024-00891)
...

Non-Conformant Components (3):
├── ❌ VLP-32 LiDAR (Expected: VLP-16)
├── ❌ Ultrasonic Sensor Array (Added - not in original)
├── ❌ 300Ah Battery (Expected: 200Ah)

Why Conformance Matters

Fleet Standardization: Dashboard shows “Fleet Conformance Rate: 73%” - tells you how many robots match their original designs. Low conformance may indicate designs need updating.

Warranty & Support: Robots with 100% conformance are easier to support - you know exactly what’s installed.

Design Validation: If all robots drift to the same variant, the original BC may need updating to reflect field reality.