Not disjointed at all.
Solutions Architect does the high level design
Technical Architect does the detailed design
Projects Team implement
Support Team support
The Solutions Architect has a high level overall knowledge of a reasonable number of technologies where as the Technical Architect has more detailed knowledge in various areas and in the setup of a selection of Customer estates.
We just define what elements can be used by the Architects and how they can use them following the policies and standards set by ourselves and our CTO department. We also check that the Architects are doing what they should and that what comes out the other end will work and be supportable by making sure things are being implemented properly.
The Project team receive the hardware and software they require and implement as per the design with reference to our cookbooks on how to configure things. Once they have built the system(s) they then go through an acceptance process into support.
Moving too much into the Projects area has caused way to many issues in the past and led to things being agreed to and implemented which should have never happened. Particularly when the infrastructure may be being used across multiple Customers.
The Projects team will also being working on multiple projects at once for different project managers, (we have >70 solution/technical architects last I heard who produce a lot of things to be implemented).