Predictive parts forecasting for every fleet size

At minimum, Aerotrax needs 12 months of component removal history in CSV format. This typically comes from your maintenance records system exported as task card or unscheduled removal data. Flight cycle and flight hour data per tail improves forecast accuracy but is not required to start a pilot. We walk you through the CSV format during onboarding.

For a CSV-based pilot, the baseline model is built within 5 business days of receiving clean data. Your first demand report arrives at the end of that period. For Pro API integrations, setup typically takes 2 to 3 weeks depending on your system configuration.

Yes. Aerotrax offers a 30-day pilot on your own removal history data. The pilot produces a real demand forecast for your fleet, not a generic demo. At the end of the 30 days, you decide whether to continue. Pilot pricing is discussed during the demo call.

Data is encrypted in transit and at rest. Customer removal data is stored in isolated tenant partitions and is never used to train models for other operators. Enterprise customers can discuss on-premise deployment options where data never leaves their infrastructure.

Pro includes pre-built connectors for AMOS and CESIUM. SAP PM and Mxi Maintenix connectors are available as part of Enterprise custom integrations. All plans support CSV upload, so any system that can export task card data works with Aerotrax from day one.

You can upgrade from Starter to Pro at any time. Billing adjusts on the next monthly cycle. If you add fleet types that exceed your current plan limits, our team will contact you to discuss options. There are no penalties for upgrading mid-cycle.