All,

Hope everyone us having a good week. Just a few things going on now.

ERAM Sustainment Tech Refresh 2

That’s what they are calling the addition of some giant ass scopes to our area. The new scopes are 43”. If that sounds like it’s big it is because it is big. The main concern I have right now is how it will affect our strip bays on low altitude. I imagine we will have to move or remove them.

Phase 1 of the install starts in Feb of 2020 (supposedly). When the TTL gets the displays installed, we will have an opportunity to set up different strip bay configurations to see what works best for us. We are also the 9th site to get the install, so I’m sure other facilities will find solutions to similar problems that we will have. Frank Champaco will be working with each of the area reps to ensure we get the best possible setup in each area. We are still about 7 months out from phase 1, so I’m sure there will be much more discussion going forward.

Click here to see what they will look like.

See All Function

The “see all” function that has always been on Sector 10 has been added to Sector 15. It can be a useful tool to train or whatever you want to use it for. To use it just type SA and then the sector number you want to see. To exit the see all function, hit clear on the keyboard. This is different from quick look in that it shows you everything that the sector is doing. Trackball movement, keyboard entries, everything. I have used it a few times to see the B area’s delays and it has helped out.

ZOA35/36 Boundary

The ZOA 35/36 boundary is depicted on our maps now. I think it is usually used as a low altitude boundary in ZOA. I think the reason it is on their high map (and how it ended up on ours) is because I am guessing they can put the high part of 35 either on 36 or on the existing sector 35 low part. If this line on 15 is annoying to you guys, let me know and I will have them remove it on the next map drop.

Schedule Stuff

It never ceases to amaze me how many ways the schedule can get screwed up. Supes are approving all sorts of wild ass shit that I have to go back and have them fix. You guys are rock stars about catching it and bringing it to me though so keep that up. Just a few bullet points to help us try to avoid even being in supe caused situations with the schedule.

  • Once OT is determined as necessary, it can NEVER be replaced with credit.

    • If an OT is canceled and then days later a credit added, I would say that is a reasonable amount of time that things could have changed. If OT is canceled and credit approved in the same minute — NOT OK.

  • Everything goes first come first serve. EVERYTHING.

    • If someone has a request in to go from a 7 to a 6 and someone else has a request to work credit in after the 7 to 6 request, the credit can only be approved in a way to accommodate the 7 to 6 request or that person needs to pass their request.

    • This is tricky for supes because the webscheduler does not put them in order for them. They are in different sections and they have to click to see time stamps.

Nothing that anyone is doing request wise (that I have noticed) is against any rules. However, you can really help the team out by knowing the rules and catching the supes from approving something they shouldn’t. It will keep your buddy from getting screwed over and make my breaks more pleasurable. :)

If you have any suggested changes to the MOUs, be thinking about those and let me, Amy, or Derek know what you want done differently and we will see if we can make it happen.

In Solidarity,

Drew