What I mean is that the software behind the SSE Descent / Project Tomorrow is almost definitely custom...
There's plenty of hardware involved in the photo capture; servers, wifi networks and infrastructure, the camera, lighting.... but you'd imagine it could be replaced for something comparable.
I'm sure that it's overall a custom software installation, but likely a lot of bits of it are based on 3rd party components/modules that Disney stopped getting outside support for years ago.
Given CM-translation, LOL, I don't think it's going to be about physical parts. If it was, it would likely not be "on and off" but broken. The issue sounds like software components ("parts") that Disney cobbled together into one platform in-house that performed add-on functions like photo overlay, etc. It would have been much more cost-effective (short-term) to just buy off-the-shelf software that does that and then integrate it in. This is really common practice in IT.
Given the recent changes in their IT structure, it makes perfect sense that they are having issues and don't know how to fix it. When you have Frankenstein'd systems like that many things can happen - the original company goes out of business, Disney stopped paying for on-going support, the platform may no longer have support available, period, etc. - and the "institutional knowledge" of how to jury-rig it back up is lost with turnover in IT. Code like that is usually ridiculously messy and completely undocumented - because it's likely been hot-fixed countless times.
This is one reason that so much infrastructure runs on 1980's computer code...because it works, and has worked for 30+ years, because it was much more simple. Now, I would bet that nothing at WDW is actually based on unique code - aside from perhaps whatever runs the animatronics. Anything else, dealing with everything from cash registers and ticket booths to audio and video in shows/rides/etc. is likely based on a lot of different bits bought from many different vendors (which explains a lot, doesn't it? LOL).
This is usually cheaper in the short-run (though in the case of MM+ and it's implosion, at this point it would have been cheaper to hire Bill Gates and Steve Wozniak to come in and write it in machine code from scratch, LOL), but in the long run often becomes a problem when you try to upgrade or change anything because it's not based on internally documented code.