To add the answers already provided, splitting a solution into different processes might also simplify the design, facilitate team (ie quicker) development, enable an incremental delivery and make maintenance easier. I repeat 'might' - it's not a guarantee and each project has to be considered separately.
The main price to pay is increased license utilisation, so any 'one time' savings during delivery could be wiped out by inefficient license consumption during ongoing BAU. Scheduling separate processes is also usually more complex than for a single 'all in one' process.
If you are running a process every 30 minutes, then ask yourself what the resource is being used for between those runs? If the answer is 'nothing', then perhaps there is a more efficient schedule that would still meet business requirements, ie more infrequent but longer runs. And when discussing requirements with the client, instead of asking them 'when is the
soonest you need the work done', instead ask 'when is the
latest you need it done by'.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------