Solved – Some questions about quarterly and monthly timeseries

forecastingseasonalitytime series

I need some help in my forecasting analysis.

In my company, for the most part, if we take a look at monthly sales time series we will find a lot of noise, a large standard deviation and variance, very little seasonality and some trend series.
As the product database that the company does planning is limited (between 5 and 4 years, up to 8 in some cases in older products) I can generate forecasts that are mostly very poor as if it were a forecast of white noise, with very few patterns and a very wide confidence interval. On the other hand I only need to analyze one point for the future or 2 at most.

But going deeper into the study of the time series of my company's products I can see that if I aggregate the data quarterly and look at the series in this way, the coefficient of variation in all series falls by about half, and I can see more seasonal patterns! As my company has a demand that is much greater than supply and a lot of production inefficiency, we close orders that sometimes take almost three months to be done, forcing the client to buy with a space of two or 3 months! This makes the series have more noticeable seasonal peaks if we look at them on a quarterly basis).

Example: We have a product with code M2, an article widely used as accessories for carnival party clothes. Carnival is a famous Brazilian festival that takes place between February and March. With this to carry out the whole process of making the clothes clients mostly make the purchase in the 3rd quarter of the previous year. If we look at the monthly data we cannot pick out the pattern very well, because it varies between the months of the third quarter (July, August and September).

enter image description here

enter image description here

enter image description here

On the other hand, if we look at the data grouped quarterly, we can see a decrease in the data variation and the presence of a strong quarterly seasonal pattern: (Quarterly data for the first quarter of 2014 until the last quarter of 2018).

enter image description here

enter image description here

enter image description here

With the quarterly series I get better confidence intervals and capture more patterns in my series. But my doubt is that the company's S&OP routine needs this monthly. So far we are working with this quarterly forecast divided by 3 for each month of the quarter. We generated some errors in the month but in the quarterly accumulated we are close to what was predicted.

Is there any better way to make this monthly breakdown?
Or given the limitations of data and because of the types of time series that I have is this the best tactic?

Best Answer

I work with time series rather than being an expert in it and I have never seen this raised. I don't think, however, that you can go from data aggregated at the quarterly level to the monthly level. Why is it important to your company to answer the question at the monthly level if there are no patterns at the monthly level and thus no predictability?

We predict at the monthly level as well, but due to unpredictable changes over time (my organization has no knowledge and limited interest in our spending process since we have little capacity to refuse services) our results are rarely accurate at less than the yearly level which is what I tell the people I report the data to.

In response to the IP response. We get asked for monthly data even though it is doubtful we can predict such accurately given the level of variation in our poorly documented process. When you have to do something you do, the key is to point out that what is being asked is not reasonable given the nature of the process. That way decision makers know the limits on what is being provided.

Have you considered using exponential smoothing to do predictions (Holt simple, damp trend etc)? Its not a perfect solution (its what we use) but its easy to do, has a good reputation, and can be accurate as long as the basic patterns don't change too much I think.