Others have said it, but the two things I would do, in order:
1. De-cluster the three floors. Each floor should become its own cluster with its own VC.
2. On the two upper floors where 115s and 225s co-exist, set the 225s to operate in 11n mode, as much as possible. You may only want to try to run with 20MHz channel widths, as well, which will allow ARM more adjustment points/channels to go to on 5GHz. (BTW, what type of clients are predominant on your network?)
3. Also, if you have them enabled, it might be wise to turn off 802.11k, 802.11r, and ClientMatch and only turn one on at a time while trying to isolate the issue. If you're not doing wireless voice and/or video, then relying upon the clients' native roaming features while trying to isolate the issue should not be a problem. I suspect that TAC have already tried this particular approach (turning fast roam and CM OFF), and they've also likely paid attention to real-time ARM power/channel assignments to see if the power window ARM is set in is appropriate for the environment/install.