What's wrong with the Air Force?

[Herk Driver]

Already happened here. We have two 3Ds assigned to our sq but the group owns them. We even write their EPRs but they don't do any work for us.

Damn if I would write their EPR then.

Posted from the NEW Baseops.net App!

[Azimuth]

Prob not her fault. As of last month the ESD had a backlog of 10K+ tickets for that sort of thing... on purpose. The CC decided that was where they would take the cut to work other tickets instead. Who knows what it's at now.

We've got folks where I'm at going through aircrew upgrade training that never have access to the folders in the training Sq's. Good luck mission planning. Hell, I don't have access to some folders.

Additionally, they're switching the AFSCs of those Amn.. AGAIN. From 3A, to 3D and, back to 3A. Now, word came down that the billets would be assigned to Sq's, but in reality you'll probably see them sucked up to the groups to work their stuff. So.. yea.

Oh, did you know you can submit your own ticket to the ESD now? Have fun with that.

What's the point of the CFP? I'm an IAO in my squadron and now I'm the guy that has to maintain DD Form 2587's, provision/de-provision/move user accounts when they PCS in/PCS out, and fill out Remedy tickets online. Last I checked no 3D briefed with my students, instructed on my sorties, filled out my TAPR's. This shit needs to go back to the CFP. When Comm created the IAO that was a way for them to dole out the shitty jobs they don't want to do.

Already happened here. We have two 3Ds assigned to our sq but the group owns them. We even write their EPRs but they don't do any work for us.

That's something that the Sq/CC needs to address with the OG Superintendent and/or OG/CC.

[HU&W]

Already happened here. We have two 3Ds assigned to our sq but the group owns them. We even write their EPRs but they don't do any work for us.

A couple of 3's would fix it quick.

[Breckey]

That's something that the Sq/CC needs to address with the OG Superintendent and/or OG/CC.

Yeah. The last few months have been a little difficult in the Malmstrom OG. Doubt this is on the front burner.

[17D_guy]

What's the point of the CFP? I'm an IAO in my squadron and now I'm the guy that has to maintain DD Form 2587's, provision/de-provision/move user accounts when they PCS in/PCS out, and fill out Remedy tickets online. Last I checked no 3D briefed with my students, instructed on my sorties, filled out my TAPR's. This shit needs to go back to the CFP. When Comm created the IAO that was a way for them to dole out the shitty jobs they don't want to do.

Exactly. However, "Comm." (as in your local Sq) did not create the current IAO position. Before what it's become now, it was a very useful additional duty to have in every Sq on base. You guys are now abused, and I apologize (for what it's worth) for the hell it's causing.

We're fighting the certification requirements, and ACC A6 is aware of it as well.

A couple of 3's would fix it quick.

Not the 3D's fault and wouldn't fix the problem. Probably have some shoe E9 down their quickly.

BREAK

Someone bitch about something else, I'm tired of posting the awfulness that is the new AF Cyber as I'm writing a Master's paper on a Friday night.

Edited April 19, 2014 by 17D_guy

[panchbarnes]

Someone bitch about something else, I'm tired of posting the awfulness that is the new AF Cyber as I'm writing a Master's paper on a Friday night.

Do you think it's stupid if you are caught sending unencrypted e-mails with PII then your account will be locked and your O-6 has to get involved? Because what if you are sending PII to another .mil account and the encryption doesn't work?

[hispeed7721]

Do you think it's stupid if you are caught sending unencrypted e-mails with PII then your account will be locked and your O-6 has to get involved? Because what if you are sending PII to another .mil account and the encryption doesn't work?

Yeah like a top-3/cc/etc distro list that can't receive encrypted emails...fail.

Sent from my iPhone using Tapatalk

[pawnman]

Do you think it's stupid if you are caught sending unencrypted e-mails with PII then your account will be locked and your O-6 has to get involved? Because what if you are sending PII to another .mil account and the encryption doesn't work?

I think it's stupid that I'm allowed to print out PII (like, say, a recall roster), and enter everyone's phone numbers into my personal cell phone from the paper...but I can't email the recall roster to my personal email address.

[Jaded]

You're not allowed to email it unencrypted to your mil account now either.

[17D_guy]

I finished my paper and mandatory video games.

Do you think it's stupid if you are caught sending unencrypted e-mails with PII then your account will be locked and your O-6 has to get involved? Because what if you are sending PII to another .mil account and the encryption doesn't work?

Yes and yes. I do believe the Wing CC is involved as well, which seems to me an amazing waste of time. I believe PII violations, at least in ACC, are tracked at MAJCOM per base.

We do need to get better about policing up PII and spillage issues. We had a spillage here where over 300 initial users were effected and then it started hitting distro lists. There's been a rash of them at ACC recently and it's shut down at least one MAJCOM office for a few days. It was such a "big deal" that the ACC A6 mandated all communication with that office will now take place over SIPR.

Spillages suck up so much Comm Sq time. PII not so much, at least on the Ops side. You guys see the confiscation of phones and computers, but the reports we're required to write for them are rather extensive and go.. nowhere. I know there used to be some MAJCOM level metrics for it, but I haven't seen any in awhile. No one seems to be punished for spilling SIPR to NIPR or higher. Maybe I'm just more paranoid about that sort of thing.

I'm not sure the impetus behind the massive focus behind it since I was in a joint community at the time. To be honest.. they should treat the spillages like they're treating PII. Why we can't have gateways that scan for PII that's unencrypted, (SSN, phone number, etc, are a common data format), kill the email and send a note is beyond me.

Yeah like a top-3/cc/etc distro list that can't receive encrypted emails...fail.


Sent from my iPhone using Tapatalk

You should be able to expand the distro list in your To: box which will break out each individual addressee. Usually there's a little (+) before the name. However, I'll check into it.

Org boxes that regularly need to send/receive PII can get token/certs for encryption.

[Stretch]

Playing passenger on a rotator to/through AUAB and stopping in Ireland. The entire pax section is elated to have a beer, especially those heading further downrange for a long stint whom have always wanted to try some name brand stout from an Irish tap.

Wheels down and the troop commander (solo O-6) makes a decision - no booze. Anyone. Back to Little Boy/Little Girl rules. He proceeds to walk the entire airport holding area from end to end in order to make sure everyone is following direction.

FFS, its Ireland and the only thing open at this hour is the airport bar and an O'Quick-Stop. We sat there, unimbibed, for several hours. I hope this admittedly minor practical but dick-move morale decision was worth it for him.

On the bright side, we still continued to Camp Cupcake and most everyone had or has time to enjoy their beer(s).

TD:LR - Having to fly to an Islamic county in order to get a beer thanks to cultural AF squeamishness over alcohol and risk avoidance.

[Toro]

All the CFP BS made me think of another idiotic antiquated issue we have. If I want to pick up the phone and make a long distance call....I can't. Eventhough every phone company in the US has free long distance phone calls, the Air Force still hasn't figured it out. When I worked in safety, this become a big issue when we had a mishap - we weren't able to make calls to the FAA and ATC folks, and since cell phones don't get reception in our building, we were running back and forth from our office to the front doors on our cell phones while trying to run safety checklists.

After the fact we tried to get access on our phones for long distance calling and were told that we could:

a) Be issued a long distance PIN that we'd have to enter prior to every long distance call

b) Have a phone granted long distance access, but every long distance call would have to be logged.

Both of these are kind of inconvenient when there's a smoldering jet on the airfield, so we just stuck with cell phones and jogging.

[SocialD]

After the fact we tried to get access on our phones for long distance calling and were told that we could:

a) Be issued a long distance PIN that we'd have to enter prior to every long distance call

b) Have a phone granted long distance access, but every long distance call would have to be logged.

Both of these are kind of inconvenient when there's a smoldering jet on the airfield, so we just stuck with cell phones and jogging.

This! The only reason I can make long distance calls is because I have "acquired" a pin that has been passed down for quite a while.

Can we bitch about DTS in this thread? I submitted an authorization >30 days ago for a TDY that was supposed to start last week. It's still sitting in CTO submit, waiting for my airline ticket to be booked. Life was so much better when I could e-mail/call our SATO chicks and have tickets w/in minutes!

One of our part time LTCs was supposed to airline out to a TDY. Showed up and surprise, no tickets. After he tried SATO (no answer) and the emergency number (couldn't help because it wasn't after hours), he called the PROJO and told him to scratch his name off he list, that he was going back home.

What else...

- Along with doing a DTS voucher, I now have to go into the portal and E-certify my orders after every TDY.

- Every TDY I travel on a mil transport I have to re-print my VRED (I thought we had it centrally located for a reason?). But for some reason it's not required if I fly my own plane...

- I have to fill out a new 2587 every time I go TDY to an AD base. Holy fuck, how haven't they figured this out yet! I can go to any other Guard base and have full access with just my ID.

Edited April 19, 2014 by SocialD

[magnetfreezer]

I think it's stupid that I'm allowed to print out PII (like, say, a recall roster), and enter everyone's phone numbers into my personal cell phone from the paper...but I can't email the recall roster to my personal email address.

https://www.spi.dod.mil/ewizard_down.htm - DoD produced Java encryption tool - approved for download on DoD or personal computers. Run it, encrypt the roster with a password, then email the encrypted file to your email and decrypt it on your laptop. Longer process but decent workaround.

[Guest]

https://www.spi.dod.mil/ewizard_down.htm - DoD produced Java encryption tool - approved for download on DoD or personal computers. Run it, encrypt the roster with a password, then email the encrypted file to your email and decrypt it on your laptop. Longer process but decent workaround.

Hypothetically, let's say I rename the recall roster from April999MDGrecall.docx to something like horseradish.bmp, then email that to a personal email, then rename the file back to the correct file type on my home computer. What's the chances of being busted or exposing PII?

Sent from my HTC One X+ using Tapatalk

[Majestik Møøse]

All the CFP BS made me think of another idiotic antiquated issue we have. If I want to pick up the phone and make a long distance call....I can't. Eventhough every phone company in the US has free long distance phone calls, the Air Force still hasn't figured it out. When I worked in safety, this become a big issue when we had a mishap - we weren't able to make calls to the FAA and ATC folks, and since cell phones don't get reception in our building, we were running back and forth from our office to the front doors on our cell phones while trying to run safety checklists.

After the fact we tried to get access on our phones for long distance calling and were told that we could:

a) Be issued a long distance PIN that we'd have to enter prior to every long distance call

b) Have a phone granted long distance access, but every long distance call would have to be logged.

Both of these are kind of inconvenient when there's a smoldering jet on the airfield, so we just stuck with cell phones and jogging.

Travis did away with long distance call codes at least a year ago. We just dial the number now. I didn't know the rest of the AF was still using them.

[panchbarnes]

Hypothetically, let's say I rename the recall roster from April999MDGrecall.docx to something like horseradish.bmp, then email that to a personal email, then rename the file back to the correct file type on my home computer. What's the chances of being busted or exposing PII?

Sent from my HTC One X+ using Tapatalk

The problem is using this TTP you are still breaking the rule set by "The Man" and you can still receive punishment if someone found it on your hard drive.

You should not get in trouble for e-mailing a recall roster to yourself. What's next? Getting a LOR for losing your cell phone with you coworker's contact info? How about LOR for losing a paper copy of the recall roster?

[stract]

10 years ago, when I was in charge of the ops desk, we had a recall, and folks were having to step outside to call others with long distance numbers...so I called the telephone folks who gave me a form to fill out requesting an unrestricted line, and voila, a day later it was done. No log to be maintained, no code/PIN to input. I considered it a minor victory.

[Guest]

The problem is using this TTP you are still breaking the rule set by "The Man" and you can still receive punishment if someone found it on your hard drive.

That wasn't my question.

[Bode]

Hypothetically, let's say I rename the recall roster from April999MDGrecall.docx to something like horseradish.bmp, then email that to a personal email, then rename the file back to the correct file type on my home computer. What's the chances of being busted or exposing PII?

Sent from my HTC One X+ using Tapatalk

We had a mandatory squadron briefing from OSI after someone emailed a mission data card to their personal email. All because it had drop times for a local training sortie.

[17D_guy]

All the CFP BS made me think of another idiotic antiquated issue we have. If I want to pick up the phone and make a long distance call....I can't. Eventhough every phone company in the US has free long distance phone calls, the Air Force still hasn't figured it out. When I worked in safety, this become a big issue when we had a mishap - we weren't able to make calls to the FAA and ATC folks, and since cell phones don't get reception in our building, we were running back and forth from our office to the front doors on our cell phones while trying to run safety checklists.

After the fact we tried to get access on our phones for long distance calling and were told that we could:

a) Be issued a long distance PIN that we'd have to enter prior to every long distance call

b) Have a phone granted long distance access, but every long distance call would have to be logged.

Both of these are kind of inconvenient when there's a smoldering jet on the airfield, so we just stuck with cell phones and jogging.

Yep. Best part about where I'm at.. we lost the ability to log. So we're making people use PINs or get "Class-A" lines (unrestricted) and can't verify anything. Never mind the fact almost no-one has a local number anymore. Damn.. I'm so used to this stupidity I didn't think we could change it. If Travis has, perhaps we can do something.

For these issues call your CS Ops Flt CC and he should be able to hook you up as long as he's not a douche and remember what the mission is.

Also, the AF just did away with the AFI requiring the additional duty position, TCO - Telephone Control Officer, in each squadron who would verify phones/pins...but requires it as an inspectable program. Figure that one out.

Edited April 19, 2014 by 17D_guy

[Champ Kind]

Do you no longer have to be a TCO to submit a WOMS request?

For those of you who dont know what that is... Be thankful.

[HercDude]

Hypothetically, let's say I rename the recall roster from April999MDGrecall.docx to something like horseradish.bmp, then email that to a personal email, then rename the file back to the correct file type on my home computer. What's the chances of being busted or exposing PII?

I wouldn't ops check that one. One of the joys of being a PII investigating officer and drafting the 69 page report for the Wg/CC was learning that he NWS (Network Warfare Squadrons?) continually monitor every email leaving the .mil domain, and will quarantine anything that looks suspicious. In the case I had to investigate, the attachments were named something generic, but it was still discovered that they contained SSNs and next-of-kin.

ProTip: When I need to send PII shit out of the .mil domain I just log into my gmail, draft a message, then attach the file. I don't send it, but I can still access the draft and any attachments from anywhere I have access to gmail.

[deaddebate]

ProTip: When I need to send PII shit out of the .mil domain I just log into my gmail, draft a message, then attach the file. I don't send it, but I can still access the draft and any attachments from anywhere I have access to gmail.

Good advice. My current method of updating recall information into my phone is to log-in to gmail contacts at work and typing everything in, which will push updates to my phone.

[snoopyeast]

ProTip: When I need to send PII shit out of the .mil domain I just log into my gmail, draft a message, then attach the file. I don't send it, but I can still access the draft and any attachments from anywhere I have access to gmail.

Ahh, the ole Petraeus technique.