Migrating to Juniper back-end, change network design to VC?

Hi Everyone,

I am working on the plan for migrating our Avaya backend to all Juniper routers. To keep is simple, I was planning on leveraging VC as much as possible (even across buildings if possible). After implementing a mesh topology, I was planning on using VC to aggregate the bandwidth but to also add redundancy as well. At the moment, the network is flat, multiple routers are being used as distribution points and all feed into one building using basic VLAN trunks. There the main router just has a static route to the firewall. Basically, there is no routing protocol in effect between any other device on the network. My initial thought when planning all of this was to keep the network simple to manage, but also to provide redundancy between our respective buildings. I perform multiple roles (server admin, network admin, dev, etc) and if I ever were to go, I wanted it to be easy for someone to come in and keep the network afloat. My question for you all is: do you believe Junipers VC is a decent route to take? Or is avoiding robust routing protocols like IS-IS and OSPF a bad idea?

Thanks,