Operational flow
Operativo connects planning, production, and warehouse
Orders and BOMs become a realistic plan: the scheduler decides when to produce, the WMS prepares materials, tablets bring work to the shop floor, the MES captures real progress, and AI makes operational data queryable.
Operativo starts from real orders
Customer orders, items, routings, and BOMs enter from ERP, Excel, or manual entry. From there, Operativo creates phases, material needs, and priorities shared by planning, warehouse, and shop floor.
- Import orders, items, routings, and BOMs
- Create phases from item routings
- Calculate material needs from BOMs
- Due dates, priorities, and jobs in the same operational dataset
The plan is built at finite capacity
The scheduler decides when, where, and with whom to produce. It accounts for machines, workstations, shifts, operators, skills, setup, and dependencies when those constraints are configured.
- Multi-phase Gantt with real constraints
- Forecast dates and expected delays
- Resource loads and bottlenecks
- Preview, drag & drop, and rescheduling in seconds
The WMS prepares what production needs
Planned orders generate material needs, picking lists, and staging. The warehouse sees what will be needed, when it will be needed, and where to prepare it.
- Check material availability on planned orders
- Picking lists linked to jobs and phases
- Lots, serials, locations, and movements
- Issues and consumption linked to real progress
The plan reaches the shop floor as executable work
Operators see the updated queue on tablets, then start, pause, and complete phases. Each progress update changes statuses, times, actual operators, and data used for rescheduling.
- Work queue by machine, workstation, or operation
- Start, pause, resume, and complete phases
- Real times, scrap, notes, and actual operators
- The next phase enters the queue as work progresses
Operational data becomes questions, KPIs, and reports
Dashboards and AI read orders, loads, delays, warehouse, and progress. You can query data in natural language and build operational views without preparing manual reports.
- Questions about delays, loads, materials, and KPIs
- Dashboards with tables, indicators, and charts
- What-if scenarios on urgent or new orders
- Reports and custom views on real data
The ERP remains the administrative source
Operativo does not force you to replace your ERP. It imports orders, items, routings, and BOMs; then returns statuses, progress, forecast dates, and events through APIs, webhooks, polling, or SQL bridges.
- REST APIs for modern systems
- Webhooks or polling for ERP and BI updates
- SQL bridge and connectors for legacy systems
- File import/export as a fallback for pilots and simple contexts
> ERP -> orders, items, routings, BOMs
> Operativo -> plan, progress, forecast dates
> Webhook -> phase.completed, order.delayed
> SQL bridge -> legacy and on-premise ERPs