History & Tracking

Every change in Botbit creates a history event with full audit trail.

Event Types

Type	When Created	Details Captured
Birth	Robot activated	Initial configuration, user, site
Component Change	Part added/removed/swapped	Old component → New component, SN, type
Configuration Change	Variant created	Version increment, variant details
Maintenance	Task completed	Action performed, date, technician

Event Details

Every event includes:

• Timestamp: Exact date/time
• User: Who made the change (with email)
• Description: Human-readable summary
• Details: Structured data (component IDs, old values, new values)

Example History

Robot: Alpha (ROB-2025-00142)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Mar 10, 2026 at 2:30 PM
Component Change
By: John Doe (john@example.com)

Replaced VLP-16 LiDAR (SN: VLP16-00234)
with VLP-32 LiDAR (SN: VLP32-00891)

Details:
- Non-conformant change
- Version: 1.0 → 2.0
- Created variant: AMR-v3.0-Var-1
- Conformance: 100% → 87%

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Feb 15, 2026 at 10:15 AM
Component Change
By: Jane Smith (jane@example.com)

Replaced Battery Pack (SN: BAT-001-A)
with Battery Pack (SN: BAT-001-B)

Details:
- Conformant change - no BC update required
- Version: 1.0 (unchanged)
- Conformance: 100% (unchanged)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Jan 1, 2026 at 9:00 AM
Birth
By: System

Robot activated with configuration AMR-v3.0
Site: Warehouse A
Build Date: Dec 28, 2025

Why History Matters

Accountability: Know who made every change

Troubleshooting: Correlate issues with recent modifications

Warranty: Prove robot maintenance and configuration

Analytics: Understand which changes are most common

Compliance: Audit trail for regulated industries

Dashboard Integration

Recent Activity Feed: Dashboard shows last 5 changes across entire fleet with links to robot detail pages.

Changes Logged KPI: Tracks total history events with breakdown:

• Variant-Creating Changes: Configuration changes that created new variants
• Regular Changes: Conformant swaps and maintenance

Organization & Teams

Multi-Tenancy

All data scoped to organization. Teams cannot see other organizations’ robots or history.

User Roles

Role	Permissions
Admin	Full access: billing, settings, invite users, all robot operations
Member	Create/edit robots, configs, components, maintenance
Viewer	Read-only access to all data

Sites

Organize robots by deployment location:

• Warehouse A
• Distribution Center
• Production Floor B

Used for filtering robots and restricting maintenance rules to specific locations.