Integration with your systems
PlanifAI does not replace your ERP, your maintenance system or your HR software. It reads what it needs to plan or forecast and returns the result. Your systems remain the official record of orders, stock, work orders and people.
What goes in and what comes out
Section titled “What goes in and what comes out”| Case | In | Out |
|---|---|---|
| Production | Orders with date and priority, routings with times, resources and calendars, orders in progress | Sequence and dates per plant, resource and stage; orders affected by each change |
| Maintenance | Assets, hours or cycles, maintenance programme, open work orders, workshops | Date and workshop of each service; expected availability |
| Shifts | Staff, skills, base roster, absences, needs per shift | Roster with confirmed covers |
| Forecasting | Sales or consumption per item and month, item master, stock and lead times | Forecast per item; reorder point and safety stock |
Routes
Section titled “Routes”| Route | When |
|---|---|
| Excel or CSV with review | To start (a pilot) and sometimes to operate. Before importing you see what is created, updated and rejected |
| Ingestion from your system | Scheduled and incremental. What fails the quality checks is quarantined with its reason |
| API | To launch computations and collect results from your tools. Computations are asynchronous jobs |
| Export | The result as CSV or in a staging table your system picks up |
There are no packaged connectors: each integration is designed in the project on what your system already exports.
Data quality
Section titled “Data quality”- Each source shows the date of its latest data.
- Each load leaves a record: accepted rows, quarantined rows and the reason.
- A proposal computed on data that has since changed is marked as outdated.
Back to the system
Section titled “Back to the system”Whether the result goes back automatically or after a person confirms it is decided in the project. Usually the planner accepts the proposal and then it goes back.