How WILBUR Works
WILBUR connects directly to any ERP environment via APIs to capture part and asset activity in real time, then converts that operational history into a secure, continuously updated digital record. The result is a trustworthy, traceable part lifecycle view, from birth to scrap.
1
Data Integration
WILBUR seamlessly connects to ERP systems through a robust API layer (WILBUR ERP Connector) to ingest comprehensive, company-provided part and asset data.
What this enables
- • Fast integration with minimal disruption
- • Continuous access to part master data, transaction data, and key reference fields
- • A foundation for consistent lifecycle tracking across systems and locations
2
Real-Time Event Tracking
WILBUR captures ERP-related events affecting parts and assets as they happen, across the full lifecycle, birth to scrap.
What we capture
- • Core operational events (manufacture, receive, install, remove, repair, sale, scrap, etc.)
- • All birth certifications and/or all historically related trace and provenance documentation
- • All historical part imagery
- • Ownership and location changes
- • Maintenance events and compliance
- • Condition/status transitions as represented in the ERP
- • Any event relevant to chain-of-custody and traceability
Why it matters
- • Eliminates delays and manual reconciliation
- • Supports audit and compliance readiness with a continuously updated timeline
- • Enables near real-time traceability and operational visibility
3
Digital Twin Creation & Continuous Updating
WILBUR transforms ERP event history into a secure digital identity for each part or asset. This identity is represented by a non-fungible WILBUR token (NFT) that links lifecycle events into a trusted timeline.
What this delivers
- • A persistent, tamper-resistant identity tied to a part's history
- • A continuously updated digital twin that evolves with every new ERP event
- • A unified traceability layer without requiring ERP replacement