Weekly Update 10/6

All,

So our schedule is finally done and it is attached to this email. Please keep in mind the Article 46. This schedule is for 31 lines. If we end up losing someone then we will have to remove the Sat/Sun off straight 0900s line (Indicated as line 76 in the graphic). I attached it in that format so you can see what it looks like on bidATC. More info will follow in the facility updates on how to use bidATC.

Other reminders about the schedule:

  • 1330s will have a 10 minute flex prior to shift start time

  • 1600s on Saturdays are NF shifts

  • As mentioned before, a 2230 is an assignable shift and if something happens to prove that we need the mids here at 2230 then mgmt will begin assigning them. I haven’t seen any evidence of that, so hopefully we can keep our 2300 mids.

As for bidding, we can expect to begin on 10/25. Please leave a proxy if you will be unable to access bidATC at that time. We will need to complete the bid no later than Nov 30th to not lose leave slots.

Cliffs notes of bidding:

  • Round 1 will have 3 slots per day year round.

  • At the conclusion of Round 1, Lee and I will redistribute (not reduce) the remaining accrued leave opportunities. He will be trying to reduce OT and will likely want all remaining 3rd slots in the summer redistributed. Keep that in mind when bidding round 1. If you want summer days, TAKE THEM IN ROUND ONE. They may not be there in round 2.

  • I will do my best to keep 3 per day year round, but if it causes OT then it is an uphill battle.

  • When we redistribute, we will have a minimum of 2 leave slots per day and a maximum of 4.

  • Bidding will stop once all of our accrued slots are taken.

We have 3 weeks until the bid so try to get all of your questions out of the way ahead time. Feel free to ask me, Trevor, or Amy about any of this stuff.

In Solidarity,

Drew

Weekly Update 9/29

All,

Hope everyone is having a good week. I have a few quick things to update you on this week.

Article 46 (Realignment of Workforce)

As I am sure you have heard by now (and Derek mentioned in his email as well) mgmt is pursuing an Article 46 realignment that would ultimately pull 1 controller from the C Area and 1 from the D Area. This would be our junior most CPC (MW) if there are no volunteers. However, the contract requires this to be a facility wide solicitation so the A Area would be involved as well. If someone from the A area volunteered then it is possible that the agency would force someone to the A area instead. It is all very messy. We have talked about this a lot as an eboard and we all agree that the B area is hurting but this is just not the right answer. There are many steps that could be taken prior to this that have not been. However, it is a contractual right for the agency. We will continue to do our best to prove to them that this would do more harm than good and hope that they can be shown reason.

As you would expect, this has really thrown a giant wrench into our schedule for next year so just remember that. It has gotten worse since the last time I said it was bad. We are doing the best we can with what we have though.

SEA Metering

Our metering set up is not ideal. We are put in situations where we turn aircraft all over the sky just to hand them off to the B area for them to do the same. Until we get something changed with that process I have two recommendations that you can listen to or not. First is, try sending aircraft back to BLYTZ in Sector 13 and KNGDM in Sector 14 and see if it works for you. I have been doing it and I like it. It helps eat more delay and it also helps the B Area get them all in roughly the same spot. There are published holds at those fixes as well so in the even we go into holding, that would help out a lot. Not a requirement, just a thought.

The other thing we can do to help out is when we do clear aircraft back on course after hitting our meter times is to maybe let the aircraft know that there will likely be delay on the next frequency as well so they can be preparing for it. Again…not a requirement, just something that might help the B Area out in dealing with the whiners.

BLYTZ/KNGDM Routing from ZOA

So we finally have Randy Vincent working on this with us. Apparently there is concern that ZLA would start routing aircraft direct BLYTZ and KNGDM and that would mess with the flow of recently redesigned sectors in ZOA. I do not understand how that is an issue, but nevertheless, our TMO is in contact with their TMO and the ball continues to slowly roll along. Hopefully we hear something soon.

Sector Red Numbers

Sector 14’s “alert parameter” otherwise known as the number that makes it go red will be lowered to 15 at some point next week. We will try that out and see what we think and maybe go 1 lower if we feel like we need it.

I just want to close with a request from you all. If a Supe wants to pull you into the office and have a discussion about anything, please do not hesitate to ask for a rep. They really should be offering you one but that doesn’t always happen. The rule is that if the employee reasonably believes that discipline may result from the meeting then a rep must be provided. So that threshold is entirely up to you to determine. I am more than happy to go into any meeting with you.

That’s it for now.

In Solidarity,

Drew

Weekly Update 9/22

All,

Hopefully everyone is having a good week. Our schedule is not yet finalized for next year but I can share a few pieces about it. It looks like it will be 31 lines so that’s better than we initially thought but still not great.

2230 Mids

As expected, mgmt has decided to make the 2230 mid an assignable shift. We will however, have the 2300 built as the actual line. If something happens during the year that causes us to need a 2230, then mgmt will start shift balancing to it. Hopefully we can address this on a case by case basis.

New Arrival

We have a new arrival to the D arriving in the building tomorrow. His name is Nick Nolke and he is coming to us directly from the academy. Feel free to stop by and introduce yourself to him. I plan to on Wednesday or Thursday.

MAP Numbers

We are making some headway on getting the Supe-tron numbers changed. The plan is to have Sector 14 go yellow with 12 and red with 14.

That’s it for now.

In Solidarity,


Drew

Comment

Weekly Update 9/15

All,

Hope everyone is having a good week. It feels like there is a lot going on in the building and many things being said about it. I would encourage you all to please just ask me if you have concerns about any issue going on. I am happy to explain to you what I can. I would much rather spend my entire break or time on my RDO talking with you about an issue than have misinformation spread.

Mid Shift Start Times

Thank you all for responding to the poll I sent out. I got 21 responses and almost all of them had detailed comments. The results were 85.7% in favor of me continuing the fight for 2300 mids and 14.3% against. So I will continue this fight and I will use the arguments that you all left in the comment section on the form. Again, I am concerned that Lee will use his mgmt rights to prevent us from getting 2300 mids, but I will continue to make the argument the best that I can.

Frequency Site Labels

You have probably seen the change in your CEDAR by now. Kevin Miller made us little cards to put on each sector showing what the old and new site labels are. I put them by the keypad in between the VSCS screens.

Metering

Last Wednesday we handed off a MFR AMF departure going to PDX at FL200 to the B area. They called upset and told us we had a 13 minute delay. So I told Kevin Miller in airspace that if we are expected to meter to PDX on the lows then we need to see a list. He told me that the D area is not expected to meter to PDX on low altitude. We are still expected to meter to SEA though so I would like to get that list added to the lows eventually unless someone has an objection to that. Long story short, until we hear otherwise or an agreement is put in place with procedures and all that, we do not meter to PDX on the lows. All that being said, if you happen to see a time and want to do the neighborly thing, I am sure it would be appreciated.

EEO Class

On this pay period that just posted, you will see some overtime and abnormal shift assignments to allow for everyone to attend a mandatory EEO class. This class is on October 15th, 17th, 21st, and 23rd. The times are 10-12 and 1330-1530. Obviously these times are not ideal for our schedule so special accommodations had to be made. Make sure you thoroughly check your schedule around those days as it may not be what you normally have.

Bidding

We are waiting until next week to finalize next year’s schedule because we will have more information about how many people we can bid. I haven’t received hardly any requests for non standard lines or AWSs so make sure you forward those to me or Angie ASAP. We likely won’t be able to accommodate too much with this year being a down year for staffing but feel free to request it. After we complete the schedule, we will just be waiting on MOU briefings and then we can get started bidding. It is looking like early October for that if I had to guess.

In Solidarity,

Drew

Comment

Mid Shift Start Times

All,

Click this link to voice your opinions on mid shift start times. I am not sure what we will be able to get, but I just want to make sure I am actually fighting for what you all want.

https://forms.gle/rHcjVKCZSKbuTEaL7

Drew

Weekly Update 9/8

All,

Derek, Amy, and I wrapped up the bulk of negotiations last week on next year’s MOUs and we hope to have the finishing touches on them in the next week or so. We will send them out to you all after that. We also have a new CPC-IT headed to the D-Area. Katrina Linder from PHL Tower/TRACON arrived last week and is in the training department now. Feel free to go say hi when you get a chance. To answer the question you are all undoubtedly wondering, she is after Hadzick but ahead of Morgan/Dippe in seniority.

BTG Times

Still working on getting both lists added to the scopes. Garret and I are coordinating with Jason Revercomb from FAST but he is on the road right now so it might still be a little while. The biggest question we are trying to figure out is if we display both times, which one goes in the data block? I will let you know when I know more.

Frequency Site Name Change

Tech Ops has requested to change the button labels on the VSCS to more accurately reflect the actual site names and bring the D area in line with the rest of the facility (as well as most facilities in the country). This will be done by 9/18. Nothing is actually moving but the names will be different. As shown below, MFR will say QKN. Site locations of each channel are still in the ERIDs and sector binders. So you might reach for a frequency expecting it to say something different than it does. It is still the same frequency and the same site, just with a different label. This will take some adjustment. You can expect something in your CEDAR about this as well.

This is from Tech Ops to explain the change:

RCAG CH #          VSCS A/G Button Label   TechOps Official Site name

6, 8, & 13             MFR                                       QKN

24                        EUG                                     QXWA

26 &39                FOT                                      QQBA

52                        FJS                                          31A

2020 Schedule

Angie and I have been working on next year’s schedule and I just wanna give it to you guys straight. YIKES. It is not looking good. There are still a few variables in play, but it looks like we will be bidding less lines than last year. We want to be cautious about bidding trainees as FPLs so we don’t end up with holes on the schedule right out the gate or not have the ability to get people trained. All that being said, as always, I am open to any and all suggestions regarding what you think our schedule should look like next year. We aren’t going to have a lot of flexibility for AWSs, but if you have one in mind, please let Angie or me know.

I do want to add one thing about the shifts themselves. I know that you all still really want 2300 mids. I am fighting tooth and nail to keep those. I am citing fatigue among many other reasons as to why we should keep them. The chief argument I am making is that we have them right now (and have for years) with NO ISSUES. So I do not understand why Lee wants to change them. All that being said, we are fighting an uphill battle.

Article 32 Section 3 of the CBA says:

The Agency shall establish three (3) core shifts: Day, Evening, and Midnight shifts and no more than three (3) ancillary shifts attached to each core shift. Absent mutual agreement at the facility level, there will be no more than three (3) ancillary shifts attached to each core shift. Any additional ancillary shifts are to be negotiated at the local level. All core and ancillary shifts will be incorporated in the annual BWS agreement(s).

So the agency shall establish the shifts. I can negotiate to get the 2300 mids added as an ancillary, but without it being a core shift, there is no guarantee that it will be assigned as part of our schedule. Even if it is, they could shift balance us back to the 2230 and not be violating the MOU.

I just want to give you all the fullest picture I can on what we are up against with keeping our 2300 mids.

In Solidarity,

Drew

Weekly Update 9/1

All,

September is finally here, football and PSLs are back! I don’t have a ton to update you on right now. I would like to ask that before engaging in rumors and gossip, please consider what could reflect poorly on our profession. We don’t want any more spotlights on us.

BTG Times

Every response I received regarding seeing 2 lists, one of them being the BTG time, was positive so I will be moving forward with that in the next few weeks.

This past week has been pretty wild with weather and deviations and all that. I am proud to work with such consummate professionals. Just wanted to acknowledge that. You guys are awesome.

In Solidarity,

Drew

Weekly Update 8/25

All,

Hopefully everyone is having a good week. MOU negotiations are scheduled to begin on 9/4. I will keep you all apprised of what I can, when I can. On to the update.

OT Cancellation Inside 7 Days

Last week I had mentioned that an overtime was canceled inside 7 days and I was trying to sort out whether or not they broke any rules by doing so. Since the contract says “shall not normally”, it is still a gray area for me. However, after consulting with our ARVP I decided not to file a grievance on it. The agency’s take is that anything outside of their control, they can cancel OT inside 7 days. I don’t personally agree with this interpretation but it is my understanding that fighting them on it would not be beneficial at this juncture. I have more to add to this that I don’t feel comfortable putting in an email so feel free to ask me about it if you care.

SEA Traffic Flow Issues

BLYTZ/KNGDM:

  • Apparently this is still being worked on. Our illustrious TMO, Randy Vincent, will be back in the building on Sept 1 and I have been told that he will help us get this accomplished then. I am not thrilled about how long this has taken but with the way bureaucracy moves around here, I will take it.

Seeing the BTG Time:

  • I know this is something we have kicked around quite a bit in the past but I wanted to take another shot at it. We do have a way to display our time and the BTG time. We just can’t toggle it on and off, we will have to see both. Is this something we want to try out and see what we think?

In Solidarity,

Drew

Weekly Update 8/18

All,

Hope everyone is having a good week. The days are getting shorter and football is almost back so enjoy what’s left of the summer! As many of you already know, Miles Hamper has resigned from the agency and headed back home. I wish him the best in all his future endeavors. I will be advocating heavily for us to get the next possible person we can to replace him in our pipeline.

Tracker on 13

The current idea on the table is to remove the overhead VSCS from Sector 10 and place it above sector 13 to more easily accommodate a tracker position. Does anyone have any issues with this? I had Sentry Eagle concerns but as far as I have found out, no one knows if they are doing that any time soon. Also, I don’t think we even used a tracker on 10 during the last one anyway. Let me know your thoughts on this.

OT CEDAR Notifications

As per the OT MOU, mgmt is only required to notify you about overtime assignment or cancellation via one of the following methods:

  1. In Person

  2. In Writing

  3. Via telephone conversation on a recorded line

  4. CEDAR

Any one of those options is acceptable. I am personally not a fan of them canceling an OT 3 days out and only putting the notification in CEDAR, but they have met their requirement to notify you if they do that. If you do not check your CEDAR to see it then there is nothing I can do about it. Back on 5/5 I sent an email showing how to turn on CEDAR notifications that are sent to your personal email and I have attached the same screen grabs to the bottom of this email as well. That being said, I do not believe that notifications were made in CEDAR (or any other approved method) for OT assignments on PP19. I have brought this to mgmt and as far as I know they have not addressed it. If this does not get fixed soon, I will be filing a grievance to address it.

As for the cancellation of OT inside of 7 days, Article 38 Section 9 states:

Overtime shall not normally be canceled without seven (7) days notice.

I believe that someone turning in bid annual leave is a normal situation and does not meet the abnormal threshold set by Article 38 Section 9 and thus should not be given as a reason for cancelling inside of 7 days. The agency, however, has taken the position that they can cancel the OT inside 7 days if the reason is “outside of their control.” Meaning that they have no control over whether or not someone turns in annual so they are clean to cancel the OT inside 7 days. I have been told by management that this was a decision made by the ETR (regional big whig) and is a settled matter. I have asked for this in writing and if I can’t get that then I will likely file a grievance to address it.

NCEPT Update

You may have already read this from the National Office but here is the latest on NCEPT:

NCEPT Process Update

The Parties at the national level recently met to review the NCEPT process. The review included the number of CPC’s actually on board and the number of trainees (CPC-ITs and developmentals) presently in the system. We also discussed the joint goal of increasing CPC certifications to improve facility staffing.

As a result of these discussions, we modified the Decision Lens tool which assists in prioritizing facility rankings for the NCEPT process. We put extra weight onto the staffing health of each facility, and lowered weight of criticality to the NAS. The goal of this was to bring the lower staffed facilities up to the top of the ranking list, regardless of their affiliation (Core30, Enroute, mid-level, etc). Facilities that normally do not see the top 30 rankings because of their size or type facility, yet still are very low staffed, should now move higher up on the facility priority list.

We also agreed to the temporary modifications to the NCEPT process below which are intended to help increase in the number of CPCs in our facilities.

Temporary NCEPT Changes:

1. Apply ERR MOU Section 12 A. Category 2 as follows:

Category 2: CPC Current and Projected AOB >85%. Release dates shall be within twelve (12) months of selection.

2. Apply NCEPT SOP paragraph 3.5.5 as follows:

Consideration of ERR requests will generally occur up to a projected CPC to target of at or below 85%. ERR requests above 85% of projected CPC to target will be considered on a case-by-case basis. Requests for transfer to Facility Pay Level (FPL) 9 and below facilities up to 100% of the projected CPC to target percentage will only be considered for extenuating circumstances after all other ERR requests have been reviewed. The NCEPT panel may expand consideration up to 100% to include additional FPL facilities. A facility will normally not be considered to receive employees if the ratio of CPC-IT/DEV to total number of controllers is at or above 30%.

We conducted a simulated NCEPT on the above changes and based on the results, agreed to move forward with scheduling the NCEPT on Sept. 30, 2019. The next ERR submission deadline is Aug. 29, 2019. You can find more information on the members side of the natca.org website.

Thats all for now.

In Solidarity,

Drew

Weekly Update 8/11

All,

Hope everyone is having a good week. Not a ton going on right now just a few reminder items.

Refresher Training

Matt Dippe is working hard on our refresher training but is currently the only one who has volunteered. Ideally we would have 4 people to help do this so the workload is lightened a little. If you have an interest in this, please let me or your supervisor know ASAP.

MOU Season

We are getting closer and closer to beginning MOU negotiations. Please let me, Derek, or Amy know if you have something you didn’t like from last year’s MOUs that you want to see changed so we can try to do that.

Nominations are Open

Don’t forget! Nominations are only open until Thursday. Nomination forms are by the reading room. Fill one out and drop it in the black box.

That’s all I have for now!

In Solidarity,

Drew

Weekly Update 8/4

All,

I hope everyone is having a good week and enjoying this amazing weather we are having. Nominations are open for all positions on the Local Executive Board so be thinking about who you want to nominate or if you want to run. Forms are by the reading room. Just fill out and place in the black box by Thursday, August 15th.

ZOA 35/36 Boundary

I have spoken to Kevin Miller and this boundary will be removed as soon as he can get it done but no later than the chart change next month.

OSHA Issues

Derek got the air quality test results from the SOC and I have passed those along to our national OSHA rep who in turn has given them to our independent Certified Industrial Hygienist for review. The CIH is now in contact with the contractor doing the work and will follow up with us once they know more.

That’s it for now.

In Solidarity,

Drew

Weekly Update 7/28

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

Weekly Update 7/21

All,

My apologies to everyone who enjoys reading this update with their morning coffee on Sundays. I got it out a little late this week due to not having cell service by the Lochsa River. I’m on the road all day tomorrow and back to work Tuesday.

Cascade Handoff Issues

Garret did some research on this for us so I wanted to pass along his findings to you all:

I did some digging (and filed an AIMS trouble ticket) on another handoff issue that Caleb and Jackson experienced this past week. FAST and Airspace are actively trying to figure out how to reduce/eliminate these but in the meantime, I learned a few things that might help everyone understand what is happening and how to fix it more easily when issues arise:

  1. Unless an altitude is entered on a VFR flight plan (e.g. VFR/125), ERAM by default processes it at 045. In that case, when a VFR target overflies Cascade airspace, the STARS computer on the Cascade side "keeps" the flight plan within the first approach sector (EUG or MFR) it passes through and won't process it to the next Cascade sector unless a handoff was accomplished.

  2. One method to alleviate this is to enter a specific VFR altitude into the flight plan so that it processes as expected.

  3. Another method, if a handoff to Cascade is flashing to the wrong sector, "E1E" for EUG or "E1R" for MFR, we can try to address the handoff directly to either one by entering "E1E CID" or "E1R CID" accordingly.

If anyone experiences an issue, simply writing down the date/time/callsign and sending it to me or Kevin Miller in Airspace will help immensely in trying to fix the issue going forward.

Fix Posting Bay Headers

Those new ones should be coming soon. I need to coordinate with Lee a little more when I get back.

Tracker for Sector 13

I got some great feedback from the area regarding this and it seems like if we choose to put a tracker in for Sector 13 we should do it in split mode on the VSCS. The conversation about how to do this is ongoing so let me know (if you haven’t already) if you have any feedback about it.

Let me know if you have any issues.

In Solidarity,


Drew

Weekly Update 7/14

All,

Hope everyone is having a good week. Looks like summer might finally have arrived so that’s good. I am currently on the road to Montana where I will be for the next week visiting family. I am still pretty accessible but in case something urgent comes up, feel free to just go to Amy with it. Alright, here’s the update:

Fix Posting Bay Headers

We will be changing the fix posting bay headers for the lows to be mostly blank but have a memory aid to indicate whether sector 05 is open or closed. This decision is based on the feedback I received from you all.

Tracker for Sector 13

Brian Kayner mentioned the idea of using a tracker on sector 13 since it gets so busy these days. To officially install a tracker position we would have to take from 10 (which we might need during Sentry Eagle) or from sector 14, which I am not comfortable with either. I could maybe pursue trying to cannibalize another area’s equipment but I doubt I would be successful. In the interim, VSCS can be placed in split mode on the R-Side, one VDM will support the radios and the other VSCS will be ground-to-ground (there is radio monitoring functionality included). This would allow for the R-side to operate the radios only, the D-side will be unaffected, and the tracker will be able to listen to the radios and effect coordination if necessary. The tracker would be reaching over the R-side to interact with the VSCS so that would be a drawback. When I was at ZFW we would use a tracker every now and then and when we did the D and R side would both forward to the tracker and the tracker would make and take phone calls while the D side handled computer entries and the R side just did the talking. Not everyone did it this way; there are lots of different ways to handle it. Let me know if this is something you want me to pursue.

VFR not processing from EUG to MFR airspace

It was brought to my attention that some aircraft transitioning from MFR airspace to EUG airspace or vice versa end up having to be RFed to be handed off. I asked Kevin Miller about it and he sent me this: Cascade approach has been known to "Terminate Beacon" on flights that transit both facilities, which kills the coordination with the subsequent STARS facility. I had a discussion with them about that a few months ago. If it happens again, you might have the OSIC give them a call.

Sector 05 Processing

Sometimes if you PVD a data block to Sector 05 is shows not active or that it is rejected. If you get a reject message it should tell you where sector 05 is and you can do the point out to that sector. If you are unclear on it, you can always just call. If you get the not active message, a handoff will always process correctly to tell you where sector 05 is and thus will tell you whether or not a point out is required. So if you PVD an aircraft to 05 and it rejects it, flash it to 05 and if it goes to 35 then you know it is combined. All other situations should be pretty rare. Please continue to let me know about each instance as it happens so I can address it. I have attached a document regarding this. We can expect a fix in September.

In Solidarity,

Drew

Weekly Update 7/7

All,

Hope everyone had a good and safe Fourth. Last week I sent out an email that had a fair amount of substance to it. I got no replies on some things that I was surprised I got no replies on. If your silence means that you are fine with whatever I decide - I am good with that. I just wanna make sure you all have the chance to share your opinions ahead of time. I am going to include some of those same topics in this email in hopes of getting replies.

Feeling Sick at Work/OSHA Concerns

I posted this in slack as well — Several people have mentioned getting headaches and feeling rundown at work as well as a metallic taste in their mouth. This was reported to B area supe Joe Herrera who turned it in to Kevin Nolan. He talked to the SOC about it and they discovered a fan belt that was broken on something in that hallway right outside the control room. They fixed it and think that it might solve the issue. They said it was not attached to the HVAC system. They also said there is no reason to believe it is asbestos related.

I am not going accept that as a final answer though and I have reached out to see what our regional OSHA rep says. I’ll let you guys know more as I know more.

LMT/LKV ROUTINGS (repeat topic)

As you all know, we have been working on getting the arrival changed to have the routes to SEA be over KNZIE and KAATH. That is still a ways out so I have been looking for a way to make minor changes in the meantime. I am reluctant to try to get ZOA to send all SEA arrivals back over BTG because that would undo all of the work that we put into having built in holding at KNGDM and BLYTZ. So that being said, what do you all think about giving ZOA the ability to send SEA arrivals direct to KNGDM or BLYTZ at their discretion? This would move that traffic flow slightly while still putting the aircraft over fixes that have a published hold. I would like to think this would also help ZOA, but after talking to airspace about it, I have some concerns that they might push back on it. Either way, let me know your thoughts on this so I can try to start making moves to accomplish whatever you guys want, regardless of what that is.

REFRESHER (still need volunteers)

Refresher is a great opportunity to teach the whole area something that you see as a deficiency. Maybe a pet peeve you want to straighten people out on?

D-Area is scheduled for September 9-13, 2019. Let me know by 7/13 if you want to be an instructor or have recommended topics.

D-Side Class

We still need volunteers for the upcoming D-Side Class (Elliot Ford and Robert Morgan). The dates are 8/26-10/18. Please let me or your supe know by 7/13 if interested.

FIX POSTING BAY HEADER THINGS

So last week I gave options between fix posting strips. I got one vote that was for the cleaner one. I am onboard with that. I just want to clarify that as it stands now, we have to post when sector 05 is open. Using the strip without that memory aid would mean that we need to post the GI to indicate it is open. What would you guys rather have? Memory aid on the strip or the GI?

Lots of tricky schedule stuff going on these days. Don’t hesitate to ask if you are confused or concerned about how something was approved/denied. One last thing, big thanks to ZD for volunteering for SGET duties. If anyone else is interested, please let me know ASAP.

In Solidarity,

Drew

Weekly Update 6/30

All,

Big thanks to everyone who came out to the Half Christmas Cookout, it was a blast! Hopefully you had fun. If you couldn’t make it, hopefully you can next year. Lots of important stuff this week so do your best to read it all.

LMT/LKV Routings

As you all know, we have been working on getting the arrival changed to have the routes to SEA be over KNZIE and KAATH. That is still a ways out so I have been looking for a way to make minor changes in the meantime. I am reluctant to try to get ZOA to send all SEA arrivals back over BTG because that would undo all of the work that we put into having built in holding at KNGDM and BLYTZ. So that being said, what do you all think about giving ZOA the ability to send SEA arrivals direct to KNGDM or BLYTZ at their discretion? This would move that traffic flow slightly while still putting the aircraft over fixes that have a published hold. I would like to think this would also help ZOA, but after talking to airspace about it, I have some concerns that they might push back on it. Either way, let me know your thoughts on this so I can try to start making moves to accomplish whatever you guys want, regardless of what that is.

Flight Data Relaying Clearances

As we adjust to the flight data relaying clearances, please try to be patient with them. I know it is not an ideal situation but there isn’t much we can do. Earlier this week, a pilot called the D area desk asking for his clearance. I know this occasionally happens and isn’t a big deal but this guy said he was given the number by flight service. Hopefully they meant to give him the flight data number and this is a one off situation, but please let me know if these things happen in the future.

Cascade LOA Changes

So first off, regarding the tick marks, the majority of replies requested that the tick marks be on the 3 mile area map button so we will go with that for now. If we decide later that we want to add them to the D low map, we can do that.

Secondly, the Cascade LOA changes are in effect on tomorrow and the agency did an absolutely horrible job of briefing you all about it. There were “mandatory” briefings all week that we sent 13 people to. That is unacceptable and I have addressed that with Lee. He agrees and plans to get on the supes more about making sure people get to briefings.

As for the 70% of you that didn’t make the briefing, you are stuck doing it in CEDAR so I downloaded the powerpoint and attached it here so you can look at it now if you want to. Click here for that.

Highlights are:

  • MFR North Flow – At or descending to 12,000 ft., except aircraft filed between the OED VORTAC 120R-180R, must cross 35 NM southeast of the OED VORTAC at 12,000 ft.

  • Eug North Flow – Descending to 10,000 feet, except aircraft filed between the EUG VORTAC 125R-180R, must cross 30 NM southeast of the EUG VORTAC at 10,000 ft.

  • Seattle ARTCC has control on contact for aircraft landing RBG and OTH

  • Control for up to 30 degrees instead of 20.

Refresher (yay.)

D-Area is scheduled for September 9-13, 2019. Let me know if you want to be an instructor or have recommended topics.

Fix Posting Bay Header Things

I think we have this narrowed down to two options. The recommendation was made that we need a memory aid as to whether or not Sector 05 is open so that is one of the options here. Would you guys rather have….

Option 1

or

Option 2

Please let me know which of these you want or if you have a suggestion to add something to them, let me know. I am trying to keep the information on them to a minimum. I believe that most people use the ERIDs/AI function to look things up like ASOS frequencies and runway configs for airports. As always though, I am open to feedback on this and any other issue. Don’t be afraid to come talk to me.

And one last thing, Devin wanted me to let those of you who like to hang out in the ladies lounge know that your internet booster is offline there due to the major mechanical project going on. There is no estimated date of it being returned to service. I hope you all make it through this tough time.

In Solidarity,

Drew

INPUT NEEDED -- MFR/EUG TICK MARKS

All,

We need to get this submitted to Kevin Miller by the end of the week so please reply ASAP on what you would like to see. With the upcoming changes to the Cascade LOA we will be placing tick marks on the scope to indicate the radials and distance that you are required to have aircraft down by. Attached is a picture of what they will look like. The question is — Do you want them on the D-Low Map so they are always there or do you want them on the 3 mile area button? We do not currently have any available buttons so we can’t give it its own button. So again, the choices are:

D-Low Map

or

3 Mile Area Button

Reply to this email and it will go directly to me.

Thanks,

Drew

Weekly Update 6/23

All,

Hopefully everyone is having a good week.  Don’t forget the two events this week!  My Half Christmas Cookout and the NEB meet and greet.

Half Christmas - Monday, June 24th @ 3pm at my house (more info in the link at the bottom)

NEB Meet and Greet - Tuesday, June 25th from 6-9pm at Virtual Sports in Tukwila.  (Flyer above)

Alright, on to the update:

XTE vs RDO Swap vs Shift Change Request

There has been some confusion amongst the supes about what order to address XTE, RDO Swaps, and shift change requests.  As they are all technically shift change requests, they are all addressed in the order received.  This presents a challenge for the supervisors because the XTE requests are in a separate section on the webscheduler.  There have been 2 instances over the last week of a supervisor approving credit onto a swing and then editing the shift back to a day ahead of someone requesting to go from the swing to the day.  Lee agrees with me that that is not appropriate.  I believe I got both issues addressed, but keep your eyes peeled for possible future instances of this.

In an effort to further clarify how I expect the supes to handle this, I will give an example.

Employee A is on an RDO

Employee B is on a scheduled 1500 with a request in to go to a 0800.

Employee A then subsequently requests XTE on a 0800 shift.

Employee A is in line behind Employee B in trying to get a day shift.  Employee A’s 0800 cannot be approved without Employee B’s being approved first.  Employee A may be offered an XTE 1500 shift to accommodate Employee B’s request but that is not a requirement for the supervisors to do.  So be aware of this and know that we can help each other out a bit here.  This type of thing has the potential to create many situations where Employee B is never going to get a 1500 to an 0800 but decides not to pass for Employee A and nobody gets their request approved.  I know this type of thing can be pretty complicated so if I’ve done a poor job of explaining it and you have further questions, please let me know.

Red Sector Numbers

Does anyone have any objections to lowering our TSD numbers?  By that I mean changing the point at which sectors go yellow/red.  The purpose of having lower numbers would be to encourage the supes to actually look at the sectors as they go red.  I know we often have a green sector that is completely down the shitter.  We probably only need to lower them for 14 by itself and all the lows combined.  I have also been told that this might help us to get more help from ZOA when we request it.

The recommendation made to me was:

14 only - Yellow at 12, Red at 14

Lows combined - Yellow at 10, Red at 12

Keep in mind that if you guys agree we should do this, it may still take some time to get it done.  I am not sure what hoops I will need to jump through.  If there are no objections then I will begin pursuing this this week.

Green Fix Posting Bay Headers

Our current fix posting bay headers have a bunch of holding information on them that may or may not even be accurate anymore due to changes in MIAs and other things over the years.  Amy has been working to try to come up with the most efficient way for us to update those.  After doing some research and asking around, here is what she and I both think are the best fix posting bay headers to use moving forward:

ACV, CEC, OED, OTH, LMT, RBG, LKV.

This will all have their respective ASOS frequencies on them (OED will have MFR and SIY) as well as OTH and LMT will have a section to write the current ATIS, runway in use, and approach advertised.

Click here to see what that would look like.

If you recommend doing anything different, please let me know ASAP.  Without objections, I plan to move forward on replacing the fix posting bay headers next week.

That’s it for this week.  Hope to see you all at the Half Christmas Cookout!

In Solidarity,


Drew

 

Weekly Update 6/16

All,

Hopefully everyone is having a good week and Happy Father’s Day to all the dads out there. For those that weren’t at the meeting last week at Rainbow Cafe, you missed a good one. It was probably the highest turn out of any meeting in my time at ZSE. We were able to discuss the upcoming MOUs and what you would like to see done differently as well as many other things. We did make 2 changes to our constitution. Elections are now decided by a plurality of the votes cast as opposed to a majority and election timelines have moved up to where they now must be completed by September 15th as opposed to November 30th. Good discussion was had on these and both passed almost unanimously. The amendment proposed to require a special election for unfilled terms of office did not receive a second and was not heard.

Reminder that my Half Christmas cookout is on 6/24 and the very next day is the NEB meet and greet at Virtual Sports in Tukwila @ 6pm. (Flyer at the top of this email).

PDX Metering

Much has been said about last week’s metering to PDX. Probably mostly by me. If you have questions or concerns, please don’t hesitate to bring them to me or Trevor. We are at the very beginning of a very slow process to try to make metering work for us. We have many obstacles in our way on that journey so any help or suggestions would be appreciated. As far as we have been told, there will be no more metering to PDX until September at least. We have been lied to about that before though so please let me know if you have any issues come up as it relates to PDX metering.

CRU-X/ART

So this comes up every so often as something the agency likes to push us on. Per the MOU from 2010, the only time you are NOT required to sign yourself in is if you report at your scheduled shift start time. Meaning if you show up at 0700 for a 0700 shift, you don’t have to sign in. If you want the flex time, you have to sign in.

The MOU also says this:

A bargaining unit employee who takes leave during or at the end of the shift must make the appropriate sign out entries in the system.

Often times supervisors or CIC will sign us out when we leave early, don’t expect them to always do this. If you are going home on leave at 1500 and you get out on break at 1430, make sure the Supe has agreed to sign you out. Even still I wouldn’t trust it because technically that is something you are required to do per the MOU.

Here is the MOU for reference.

Not much else to be said right now, y’all let me know if you run into any issues!

In Solidarity,

Drew

Weekly Update 6/9

All,

I hope everyone having a good week.  Don’t forget about our upcoming member’s meeting.  We will be honoring the 2018 Archie League Honorable mention recipients at this meeting.  For the D area that will be Jared Zautner, Matt Williford, Matt Dippe, and Chris Hadzick.  We will also be voting on proposed changes to the ZSE Local Constitution.  Proposed changes can be found HERE. Looking forward to seeing you all there!

Members Meeting is June 13th @ 2:30pm.  Rainbow Cafe in Auburn. 

Also my annual Half Christmas Cookout is on June 24th so make sure you RSVP to that at the end of this email.  Alright, on to the update.

Training Detail Solicitation

We are currently soliciting for an upcoming Article 5 detail to be a lab instructor.  The dates of the detail are 8/26-10/11.  Please volunteer to me, Angie, or your supervisor by 6/28 if interested.

Sector 35

Garret posted this is in the slack yesterday: Talked with Kevin Miller in Airspace this week. He is in total agreement that it was never their intent for 13 to feel forced to work the RDM area arrivals down to 150. We will work on changing the language for a better fit.

So if you have recommendations on wording for that, let us know.

There have been several complaints made about how the B area is not properly notifying us when they split sector 05 from 35.  I have passed this issue along to the powers that be.  Let me know if this continues to be an issue. Specific times would be helpful.

OT Swapping

We haven’t had a lot of OT in my time as rep so there are definitely some issues that I am unfamiliar with.  Recently we had someone work an OT for someone else. I was under the impression that only the person originally assigned the OT would be charged. I asked Derek Adams to clarify this for me and apparently when you swap an OT, both people get charged.  I did not realize this. 

In Section 3(e) of our OT MOU it says: An overtime opportunity is defined as the number of hours or minutes originally assigned.  A BUE who vacates an overtime opportunity for any reason will be charged with the opportunity.

That led me to believe that only the person originally assigned it would be charged.  I think this is something we will look to explicitly clarify in the future in our MOU.  If you have thoughts on how that should look, feel free to let any one of your 3 D area eboard members know.

Cascade LOA

The long awaited reworked Cascade LOA will be in place soon.  This is the change we made that requires us to get aircraft down when EUG and MFR are in a north flow.  We will be getting tick marks added to our scopes as well to indicate the radials and distance for these restrictions.  You can expect those to be on the map change on 7/18.  They will look like an “L” and a backwards “L” to indicate the radial and distance.  You will be briefed on all of this before it takes effect.

PDX Runway Closure

Starting tomorrow there is a 7 day runway closure at PDX.  I was told by TMU that they as long as the weather is good, they should be able to offload the box haulers to 3/21. The rate for single runway VFR at PDX is 28-32. They will also be able to manage demand with a CFR.  This should prevent us from having to meter but that is not guaranteed.  If you are asked to meter, just make sure the instructions are clear and let me know how it goes as we do not currently have procedures for PDX metering in place.  Coincidentally, the first meeting for the PDX Metering Art 114 workgroup is tomorrow as well. 🤞🏻

SEAD-3

In CEDAR there is a briefing item for a reporting system called SEAD-3.  If I read it correctly, and I would like to think that I did, we are now required to report/request permission for any trips outside the country as well as any relationships with foreign nationals. Seems like kind of a big change to just stick in the ole CEDAR.  I have asked Derek to look into it and see what we can find out.  I will let you know what we find out.

Break “Expectation”

Apparently at the last supes meeting they decided to brief controllers what their break “expectation” was.  I think they see this as a preventative step on the road towards attempting to implement a break “policy.”  Either way, the way I see it, they can have all the expectations they want to.  If they begin to counsel people or give PRCs for break times that they don’t like, then we are having a different conversation.  That being said, the expectation I was told was 50 minutes.

For those wondering why a break policy is such a hot topic, Title 5 of the USC gives us the right to be involved in what we refer to as I&I bargaining.  That is the Impact and Implementation of a change mgmt wants to make.  We cannot necessarily stop the change from happening, but we get to negotiate its impact and implementation on the work force.  Here is some  more in depth info on that if interested.  Those of you who stuck around this long into my email are probably bailing out now so thanks for stopping by, see you later!

The Federal Service Labor-Management Relations Statute (the Statute) specifically excludes certain "management rights" from an agency’s duty to bargain. These rights are set forth at 5 USC 7106(a). They include such things as the right to:

determine the agency’s organizational structure

hire, assign and discipline employees

assign work

Although agencies are not required to bargain over whether these management rights will be exercised, the union is entitled to bargain as to how these rights shall be exercised. To that end, Section 7106(b)(2) of the Statute requires the agency to negotiate over union-proposed "procedures" for exercising a particular management right. 

The agency is also required, by virtue of Section 7106(b)(3), to negotiate "appropriate arrangements" for employees who will be adversely affected by the exercise of a management right.

The process of negotiating over the procedures and arrangements is commonly referred to as "impact and implementation" bargaining, though that term does not actually appear anywhere in the Statute. 

An agency that refuses to engage in "impact and implementation" bargaining violates its duty to negotiate in good faith with the union under Section 7116(a)(5). Such a refusal may also be construed as a violation of the agency’s duty to consult with the union before implementing a substantive change in conditions of employment. See 5 USC 7117(d)(2)(A)

Key Criteria:

In order to determine whether an agency has a duty to bargain over the impact and implementation of a change it is about to institute, you should ask yourself the following questions:

1. Does the change at issue concern "conditions of employment"?

2. Does the change affect "bargaining unit employees"?

3. Does the change represent the valid exercise of a management right?

4. Will the change have more than a de minimis impact on unit employees? 
    
5. Is the change outside the coverage of the collective bargaining agreement

If the answer to all five of these questions is "yes," the exclusive representative has the statutory right to bargain over the impact and implementation of the change. This section will examine each of these requirements one at a time.

Question 1: Involves Conditions of Employment?

The term "condition of employment" is defined by Section 7103(a)(14) of the Statute as: "personnel policies, practices and... other matters affecting working conditions, whether established by rule, regulation or otherwise." 

This is a broad definition, but there are several important exceptions to it. Section 7103(a)(14) expressly excludes from the definition--and, therefore, from the duty to bargain--any policies, practices or matters relating to:

a. prohibited political activities

b. the classification of any position

c. matters specifically provided for by Federal statute

Question 2: Affects Bargaining Unit Employees?

Unions are entitled to negotiate only on behalf of employees who occupy positions within bargaining unit they represent. Therefore, as a general rule, the duty to bargain is limited to matters that directly address the conditions of employment of unit employees. 

The working conditions of supervisory and management personnel do not concern conditions of employment of unit employees and thus are not within the duty to bargain. 

The Authority has ruled that an agency may be required to bargain over a condition of employment that "vitally affects" unit employees even if it impacts upon the working conditions of non-unit employees. 

For example, a union proposal that has some impact upon non-supervisory employees who are not represented by a union, or upon non-employees--such as contractor personnel--it will still be bargainable if it "vitally affects" the interests of union-represented employees. 

But if a proposal primarily affects either: 

  • employees in other bargaining units, or

  • supervisory personnel 

it is outside the agency’s duty to bargain, even if it concerns a matter that "vitally" affects unit employees.

Question 3: Exercise of a Management Right?

One good way to get a handle on what impact bargaining is, is to pin down what it's not.  Specifically, it's not what practitioners usually refer to as substantive bargaining; that is, negotiation as to whether a specific decision will be made or implemented at all (substance)

Rather, I&I bargaining focuses on what will be done to mitigate the impact of a decision that is solely management's to make. So if the agency has a management right to make a particular determination--such as an internal security measure--the union's right to bargain extends only to the impact and implementation of the decision. 

It follows, therefore, that the duty to engage in I&I bargaining occurs only in those situations in which an agency is about to exercise one of the management rights reserved to it  by Section 7106(a) or 7106(b)(1)

Section 7106(b)(1) of the Statute specifies an additional list of management rights that are open to negotiation if the agency "elects" to do so. They include: 

the right to determine the numbers, types and grades of employees or positions assigned to any organizational subdivision, work project, or tour of duty; and

the right to determine the technology, methods and means of performing work.

Because these matters are negotiable only "at the election of the agency," they have traditionally been referred to as "permissive" subjects of bargaining. In other words,  agencies have not been required by the Statute to bargain over these matters.

Keep in mind, however, that even if management elects not to bargain over the substance of a Section 7106(b)(1) matter, it is still obligated to negotiate regarding the impact and implementation of its decision (appropriate arrangements and/or procedures).

Question 4: Produces More than De Minimis Impact?

The Authority long ago recognized that requiring agencies to bargain over every single management action, no matter how slight, would be impractical. Consequently, it has held that agencies are obligated to bargain over the impact and implementation of a management action only if the changes effected by that action will have more than a de minimis effect on conditions of employment. 

In determining whether a change is de minimis, the Authority will consider the nature of the change and the extent to which it will impact bargaining unit employees. In applying this standard, keep the following FLRA pronouncements in mind:

The overall size of the bargaining unit is irrelevant. 

The Authority will consider the number of employees affected by the change, but this factor is not controlling.

A change that has a major impact on just one employee will not automatically be considered de minimis.

The Authority will take "equitable" considerations into account, such as the underlying reasons for the change.

The duration of a change can be an important factor.

The point at which a change becomes more than de minimis can be difficult to ascertain, but, as the term implies, it doesn’t take much. For example:

  • The Authority recently ruled that an increase in the workload of certain employees, though "slight," was more than de minimis

  • It held that the removal of a water cooler from an agency building had more than a de minimis impact.

  • It ruled that the relocation of a telephone from a supervisor’s office to a less private area had more than a de minimis impact on unit employees who used the phone. 

In short, it's unwise to assume that a change is de minimis without carefully considering exactly what's involved in it. And if there are any doubts whatsoever, case law demonstrates that agencies are better served by erring on the side of caution; i.e., when in doubt, assuming a change is not de minimis

Question 5: Matter Not "Covered By" the Contract?

Unions are not entitled to engage in I&I bargaining over a change if the manner in which the change is to be implemented is already spelled out in a collective bargaining agreement. On the flip side, agencies cannot make changes that conflict with the agreement.  

To cite an obvious example, a union would not be entitled to bargain over the "change" of giving an employee an overtime assignment if the procedures for doing so were--as is usually the case--already contained in the contract.

In this situation, the "change" would be viewed as being "covered by" the parties’ contract--and therefore not open to further negotiation every time an overtime assignment is made. The theory behind the "covered by" doctrine, obviously, is that parties should not have to engage in further negotiation over matters that they have already settled.

Sometimes it's not as clear as it is in the sample situation whether a matter is already "covered by" a contract, however, since a variety of factors can come into play. For example, a specific topic may not appear in the contract, but if it was deliberately excluded as the result of negotiations, the matter will likely still be considered "covered by" the agreement for its term. Other instances involving the covered by doctrine such as contractual work schedule changes may still have to be negotiated if requested.

No way you read this far.  You skipped some.  It’s ok.

In Solidarity,

Drew