The difference between a forecasting project and a forecasting competency is what happens after the model finishes running. A competency runs again automatically next month, writes its primary output back into the ERP as a demand plan, and gets more accurate with every period that passes. Here is the architecture that makes that possible.
Most PE-owned manufacturers who have attempted a demand forecasting initiative have built a project. A consultant or data team is engaged, they spend the first several weeks extracting and cleaning ERP data, they build a model, they present a 12-month forecast, and the deliverable is a spreadsheet. Six months later, when someone needs to rerun the forecast, the process starts over from scratch - because the data pipeline that fed the first model was never designed to persist.
A forecasting competency looks different. The data pipeline is permanent. The models run on a schedule, refresh automatically at period close, and produce outputs that are distributed to the right stakeholders at the right grain - finance at L1, procurement at L2, the board at portfolio level. The primary output is not a report. It is an MRP forecast file that uploads directly back into the ERP as a forward demand plan, closing the loop from data source to operational decision.
The pipeline is the moat. The model is replaceable. A team that builds a connected, automated forecasting pipeline owns a capability that compounds with every period it runs - not a one-time analysis that decays the moment the project ends.
This article describes the architecture of that pipeline: five stages, a stack built on Marquis IQ plus open source Python plus AI, and a circular flow that starts and ends at the ERP.
Data originates in the ERP, is normalized by Marquis IQ, shaped into model-ready features, run through competing models, and then written back into the ERP as a forward demand plan. The cycle repeats at every period close automatically.
Not every model is right for every entity. A facility with stable, seasonal revenue and 48 months of history needs a different approach than a product line that ships intermittently or an entity added through acquisition with 14 months of clean data. Running a single model against all entities and calling it a forecast is how you get confident wrong numbers.
The Marquis IQ pipeline runs multiple models in competition for each grain and lets walk-forward accuracy determine the winner. Forecast Value Added (FVA = MAE of the naive baseline minus MAE of the model) is calculated per entity per model. A model with positive FVA earns its place. A model with negative FVA - meaning it underperforms simply repeating last year's number - is a signal that the data at that grain needs attention, not that a better algorithm is required. The eight models below cover the full range of demand patterns found in PE-owned manufacturing portfolios.
The MRP Input File is what closes the loop. Excel reports and Marquis IQ serve the finance and planning teams. The MRP file serves the ERP - a structured, ERP-formatted upload that converts model predictions into the demand plan format each system expects for material requirements planning. Without it, the forecast informs decisions people make manually. With it, the model's output directly influences purchase order generation, production scheduling, and safety stock calculations. The data came from the ERP. The forecast goes back in.
The statistical models - ETS, Prophet, XGBoost - handle the forecasting mathematics. AI (Claude, OpenAI, and similar language models) plays a different role in the pipeline: it translates what the models produce into language that non-technical stakeholders can act on.
When the model's residual spikes unusually in a period - a segment that was expected to generate $2.1M came in at $3.4M - AI generates a plain-language explanation of what changed based on the data context available: which customers contributed to the over-performance, whether the pattern is consistent with prior seasonal behavior, and whether it signals a structural shift or a one-period event. The model surfaces the anomaly. AI explains it.
The same pattern applies to model health monitoring. When FVA drops below zero in a specific segment, AI flags the issue and communicates it to the planning team: "The model for Foodservice at Indianapolis is currently underperforming the naive baseline. The most likely cause is the step-change in order patterns following the March distribution agreement. Consider retraining with a shortened history window that excludes the pre-agreement period." That communication requires no statistical background from the reader.
For board and executive reporting, AI converts the forecast table into a narrative: what the model expects, where performance is ahead or behind structural baseline, and which segments carry the highest uncertainty in the forward period. The finance team stops writing the same descriptive paragraph every month and starts reviewing AI-generated drafts that are grounded in the actual model outputs.
Related reading: Why Manufacturing Demand Planning Fails covers the data foundation this pipeline requires. Beyond the 12-Month Forecast covers how PE operators use the model outputs as business intelligence.
Questions about building and maintaining a connected forecasting pipeline for manufacturing.
Marquis IQ certified connectors, conformed master data, and Azure SQL give the Python runbook everything it needs. The data foundation is already there - the forecasting competency is the next layer on top of it.