An official announcement will be coming within the next few days that go over the TCS power shutdown on June 1. However, you should start working with your stakeholders now to prepare them for this shutdown from a TCS data center shutdown perspective. I'm going to be sending a CELS (MCS/LCF/CLS) announcement *after* the official announcement on the building shutdown comes out. I don't want to start a panic/rush prior to the official lab communication hitting. The data center will be without power from (planned) 7AM until late afternoon. To play it safe, I would presume the downtime window to be 7-7 in terms of what I will announce to my users. Obviously, LCF has a longer window than that due to their spin-up time. In the official announcement, tenants of building 240 will be advised to work from home (or elsewhere on campus) and that building 240 will be closed to all but essential personnel involved in the work that day. However, if their work involves accessing equipment located in building 240, that's not going to be accessible. This includes data center machines, desktops, tinkerlab, etc. If it's in 240, consider it offline. I've already let Folker know (since we was in the meeting we were discussing this in) but we need to give the other stakeholders a heads up to start planning. I'd rather do a targeted announce to leads in these areas to get the ball rolling. Here are the affected CELS services and who should work with the stakeholders on planning for the shutdown. MCS computer/logins/file services: Craig LCRC: Ti PADS: Ti Chameleon/FG: Ti SEED: Dan MG-RAST: Dan Breadboard/Radix: Craig Cosmea: Ti EVS racks: Craig I2U2: Max ALCF (n/a, they're already on it) BIO racks in 240: Max Magellan (KBase): Dan Beagle: Joe CI secondary web and mailing list services: Craig/David -- Craig