erpclaw-maintenance

You can automate preventive maintenance scheduling by defining maintenance plans that auto-generate work orders. The system centralizes equipment records and enforces a strict data model to trigger these workflows automatically.

Tracking equipment downtime and work order lifecycles is handled via a local SQLite database. It unifies asset records, downtime logging, and work order management with a 39-action domain API for comprehensive reporting.

Yes, you can manage hierarchical asset records for facility operations entirely without external servers. Data is stored locally at ~/.openclaw/erpclaw/data.sqlite, enforcing strict security boundaries within your own environment.

The maintenance management system supports both checklists and predictive maintenance plans. It handles full work order lifecycles, integrates checklist verification, and generates analytics to help forecast equipment failures.

To initialize the CMMS database and start creating work orders, you run the schema initialization script. Once initialized, you use the exposed domain API actions to manage equipment, plans, and work orders directly.

A limitation of using a local SQLite database for maintenance analytics is that data remains isolated to a single local file. This restricts concurrent multi-user access and real-time cross-facility synchronization for broader operations.