title: correct way to structure a complex, multi-package SSIS job
body: <p>I have an SSIS solution that has hundreds of components and approximately 30 packages. <strong>I would like to know what would be the best way to structure such a solution.</strong> </p>
  
  <p>The entire thing looks like this:</p>
  
  <p><img src="https://i.stack.imgur.com/rYK0H.png" alt="enter image description here"></p>
  
  <p>When double clicking on any one of those components, to view the <strong>data flow</strong>, it looks like this:</p>
  
  <p><img src="https://i.stack.imgur.com/Txk3p.png" alt="enter image description here"></p>
  
  <p>As a way to make my work more manageable, I've broken up every individual <strong>control flow component</strong> into its own solution. Another words, I've taken everyone of these:</p>
  
  <p><img src="https://i.stack.imgur.com/jIwjf.png" alt="enter image description here"></p>
  
  <p>and I've created a solution for every one of them:</p>
  
  <p><img src="https://i.stack.imgur.com/S5E34.png" alt="enter image description here"></p>
  
  <p>Now I need to create a master solution. </p>
  
  <p><img src="https://i.stack.imgur.com/KY30I.png" alt="enter image description here"></p>
  
  <p><strong>Question:</strong> How do a structure a "master" solution to run every one of these solutions in a specified order (as specified by the first graphic)?</p>
  
  <p><img src="https://i.stack.imgur.com/ld86V.png" alt="enter image description here"></p>
  
  <p>Thank you so much for your kind and generous guidance and advice. </p>