No this is not automated yet. It's a new development of driver-based Revenue planning application. Currently the 3 steps above are run manually one after the other after successful completion of each step.
Stored Procedures would take 6 hours minimum to complete and there is no scope for improvement at this point, Because those procedures run off of some machine learning models to produce 36 months forecast factors.
I am currently thinking through design options and I know both DM sequences and SPs can be called from Extender BR and that can be attached to a DM step and Sequence. However, the DM sequence timeout after 2 hours. Since my SPs itself take 6 hours to complete this may not be an option for me.
Run parameters for the Stored Procedures are entered in a Cubeview by Users. So I need to extract it from OS and push it to DB tables before the SPs kickoff (which is my Step 1).