ALWAYS willing to help anybody that is willing to listen. Even for those who don't agree with everything, or even anything, that I might say, often says things like "but it DID make me think about THIS particular aspect, which I had not given any thought to before", so it usually works out. Also, there are certainly those with more experience than I have in a great many areas, so I' am by far not the be all and end all, by a long shot, but I do know enough to get somebody going in the right direction and avoid any obvious, or sometimes not so obvious, mistakes when it comes to component selection and configuration.
So, as far as that build goes, there are a few things I'd want to discuss. First one is the water cooling. Don't do it would be my advice. I'm going to copy pasta from another thread I'm working on where the guy is using a very high end X299 configuration, so some of it won't apply to you, but much of it may.
I tend to like air better because it does offer some beneficial airflow by way of residual cooling to the VRMs and memory components, but certainly if you are going to do an advanced open loop then who am I to knock that? Air also has the added benefit of not risking your very expensive hardware due to leakage. And don't think it can't happen.
Even though the designs have gotten much better, even the best open loop hardware, installed by highly skilled water cooling enthusiasts, can still have failures. Recently one of our moderators had a leak on some EK hardware that took out his motherboard, memory and graphics card. I also recently came across a forum thread over on Overclockers where a guy who has many custom loop builds under his belt lost almost the whole setup, including CPU, motherboard, GPU card, power supply and two 1TB SSDs all in one shot due to a leak.
First rule of electronics says to keep them away from water. I agree. Water cooling will never find it's way into any system of mine.
Also, if speed is a major consideration for this system, especially if there will often be a need for sequential copying of large files from drive to drive or even if there is not, since the random operations are still far faster than even with a standard SATA SSD, you might REALLY want to consider the use of an NVME PCI M.2 drive or multiple drives even. Long term longevity is good and incremental saves or loading of large projects will tend to be MUCH faster, which means productivity will go up and frustration from waiting on operations to finish will go down. They are certainly a lot more expensive but if you can get the ok for budgeting said drives by explaining the great potential for increased performance they offer, you will absolutely be doing whoever uses this system maybe the best service of all.
If you were comparing PC storage to automotive racing, NVME PCI M.2 drives would be considered to the Top fuel category for drive performance.
As you can see from the random performance here:
https://www.anandtech.com/show/10754/samsung-960-pro-ssd-review/7
And the sequential performance here:
https://www.anandtech.com/show/10754/samsung-960-pro-ssd-review/8
The difference is FAR more than minor, likened to the difference between using a hard drive to a regular SSD. Even a very good SATA SSD like the 850 Pro can't even remotely compare. So that might be something you want to consider. It doesn't really matter how fast your graphics card and CPU can process or render your Solidworks project if you're having to wait on the drive to either read from it or write to it.
Also, the platform you've chosen, while certainly capable for it's day, is now more than 3 years old. I certainly understand the price consideration versus a newer workstation CPU, but the bottom line here is that there are better solutions if performance is a larger consideration than EEC memory support. If EEC memory support is mandatory, then stick with what you have outlined. If not, then let's discuss other options. For far less than what that E5 Xeon costs, you can get an i7 or i9 processor with much higher clock speeds, turbo profiles and FAR faster memory support.
I say it's not worth it and the risks of NOT running EEC memory are EXTREMELY minimal, in fact, in most cases EEC memory is NOT going to protect you against the primary causes of data loss and corruption which are hardware, not software, related.
To ECC or not to ECC?
When it comes to most desktop CAD design, ECC largely doesn’t make economic sense for a self-build. Right off the bat, you’re spending money for an issue – correctable memory errors – that statistically will only affect 8% of your hardware, and only if the hardware undergoes a server-like utilization. At lower utilization, as is the case for most CAD workflows, error counts are 2-3 times less in the worst case.
But perhaps that’s not enough justification for you. Know then that ECC is not a magic bullet, and requires a server-style maintenance philosophy to utilize effectively, otherwise it’s a waste. The Google data indicates that modules with correctable errors are up to 900 times more likely to suffer from uncorrectable errors. You should have one of two reactions to this:
Holy crap, I should be monitoring my ECC memory! Then you better read up on Windows Hardware Error Architecture (WHEA) and keep some spare sticks around. Get ready to spend both time and money.
Wait, I have to monitor my ECC memory? If you haven’t bothered, and think ECC will save your bacon on its own, you’re deluding yourself. You may have already suffered uncorrectable errors without noticing. If you’re happy with uncorrectable errors, then you would likely be happy with non ECC RAM. You just spent your money for nothing. You’re doing it wrong.
Finally, all of this assumes perfect software. While it seems really unpleasant to have a system crash because a star on the other side of the universe farted a million years ago, it’s peanuts compared to how many crashes and problems you’re going to experience because your CAD software is broken. Even in the case of a system crash, most file versioning and backup strategies are a more cost-effective investment. If you don’t mind rebooting, you don’t need ECC.
ECC only makes sense in server-like workflows such as FEM analyses or rendering, where a bump in the road costs hours of time. Well, unless you plan to design in space. But then you have a whole other set of problems, like how to keep George Clooney from eating the only piece of lettuce available.
**Why EEC Memory matters, but probably not for most CAD design**
So you have to decide if this is something that is actually a necessary consideration. I've run various CAD applications for years, using non-EEC memory, although probably not on the scale that your machine will be used for, and I've never had a problem at all in any of the applications I've used which includes Solidworks, SketchUP, AutoCAD, CorelCAD, TurboCAD, Autodesk Maya, Solidworks Visualize, 3dS max, POV-ray, Blender, Cinema 4d, Photoshop, Illustrator, FreeCAD and Poser.
Again, I'm not a super advanced user of any of these applications, although I do have a fair amount of experience with each of them, and I don't use any of them professionally or 40 hours a week like you will likely be, so my exposure to data corruption through errors is probably somewhat reduced, but I DO know people personally who DO use these applications professionally on a daily basis who do not run EEC memory and are no worse for the lack of it.
EEC is absolutely essential for the server, but aside from a few very specific instances, it's not essential for or possibly even beneficial for a workstation.
So, these are all considerations you might want to discuss with your boss, and share the information I've offered here as well. If this is solely your decision and you are knowledgeable enough to weigh these considerations, then great, otherwise I'd have a discussion about it and see what shakes out.