If QM = Quartermaster, what does YY mean?

You are probably dead on right WO1 Jeff C.

That SUCKS!!!!!!!!!!!!!!! I know one of the YY's from my BOLC, and I know he is branch qualified. Uh oh.......... a year ago, I noticed I kept (I fixed it) showing up on the UMR as NON BRANCH QUALIFIED. I also kept popping as flagged from deployment on one of the systems because it kept saying NON BRANCH QUALIFIED. So whoever pushed that information up from BOLC didn't do it right in the system, and our graduation update didn't take effect system wide.

I went to a lot of trouble getting it fixed, BECAUSE OF THIS VERY WORRY that a system generated error with me not showing as qualified on the UMR would blow back on me at promotion.

I know I fixed my problem because the UMR is correct now. My classmate might not have noticed that because he wasn't in a command position and looking at his monthly UMR for the past 2 years.

I guess I have an e-mail to send to someone.

I believe you gents are correct. This is my biggest pet peeve as an officer (my other is marksmanship). Army data systems are a joke. I come from crunching data files with 10,000,000 records. So I know what can be done. I mean hell we sent someone to the moon with analog technology.

Looks like what happened to my classmate happened to me. My BOLC credentials didn't get communicated system wide from whoever did the out processing packet at Ft Lee QM school. I noticed the problem because I was in a position to see my UMR every month until it was fixed. My classmate was not. I fixed my issue, and my classmate probably never noticed.

Completely unrelated, but I think our system problem stems from the government's contracting and acquisitions process. The Gov only gets from the vendor what is explicitly asked for. The vendor is tired of dealing with the Gov and only gives them what was explicitly asked for instead of anticipating better solutions. How the product works at the end of the contract is irrelevant. In order to get paid it has to be exactly what was in the contract.

All the data systems are individual contracts trying to communicate with one another.

When I was working in banking data inconsistencies drove me nuts when banks merged. However, at the end of the day, we just eventually converted all the data to be uniform so systems could communicate between each other. The Gov is still like a giant bank that merged hundreds of smaller banks, but no one has converted the data, and it continues to be manually consolidated.

Hence................... YY

LTC Jason Mackay I was just going to say that. It's probably a branch immaterial position. If it was unqualified they would have a reporting code that would start with a 09*.

LTC Jason Mackay - Possibly, but when such a position is published in the vacancy listings they are noted as 01A. I noticed too when a language is NOT NEEDED for a vacancy language is noted as YY (like the WO1 mentions). So I think they might be popping hot for non branch qualified.

Plus, the list is of 1LT's and their branch, not the position they are in. Think of it as their signature block.

CPT (Join to see) maybe, but how are they on a promotion list?

LTC Jason Mackay - I can think of a few things. But it's all speculation. I don't know how the list was compiled. I don't know how orders will finally be published. They certainly got promoted to 1LT with RLAS and the UMR incorrect. I know I did.

I understand to the list to mean they CAN BE promoted, not they WILL BE promoted. Otherwise, why weren't orders just cut instead.

So it could very well be this is all moot, because their credentials are iPerm'd, and maybe the final person before the orders are processed validates it.

I just so easily get bent out of shape for the slightest administrative errors because you don't know when those errors will blow back on you. It's more than once I've had OER's pushed back to me for things as slight as a missing period.

The next step in our promotion is to submit a 56R with our 705 (Height/Weight) and the UMR showing us in a O3 position that is not double billeted with anyone else. The danger of the UMR is that it annotates "--" for branch if the system doesn't know they are Branch Qualified.

So I could see how at the end of another two month wait they are notified they are not branch qualified in the system and have to jump through more hoops. The only way to ensure that doesn't happen is to fix it before the 56R packet is submitted.

Additionally, there are over 1900 names on the list. Those names will all be sending in 56R packets with 705s and UMR's and some poor guy or team of guys is going to have to go through each and every one before orders are published. I don't want mine or my classmates to be easily tossed to the side because of "--" on the UMR.

Ironically, I didn't intend to go down this path. I just data crunched the branch code to see which branches made up the most new CPTs so I could get a feel of where future opportunities might be.

I was curious what YY is. I thought it might be a cool Branch I didn't know about.