Ok, i appreciate your help and your time.
Problem is, in our case, this is part of our DR setup, as well as dev test and all of that and its all stood up already.
Its all been coded in Orchestrator for all the background tasks like netowrk creations, and uses vRealize Automation for some of the blueprint tasks as well as for the customer portal. It's pretty neat. It deploys clones of any and all prod machines into a microsegmentated NSX environment, automatically creates all needed networks, DLR's and edge services. Creates access through Horizons view into those environments and allows users to build, test, bug fix, and destroy on demand without contacting the IT Team. I just wanted to make sure that the DC's not coming up at the same time weren’t going to be a problem. Honestly, it might not even be a problem in the long run. Right now the last 2 DC's come out about 10 min after the last one finished. Might not cause any problems.. .. might cause problems. At this point I don’t know, but it seemed there would be some 'wait' command out there to delay the boot of a VM until another VM is done, but so far that doesn't seem to be the case. Just trying to avoid future issues.