Ladies and gents - I was given reputable information today that Navy (and USMC) PEB has had a large technical failure related to data storage and process work flow.
PEB has the capability to do boards, but there is currently no system to process cases, send or receive findings, transmit info to PERS/MMSR-4, or do internal admin.
If your case is anywhere post-IPEB hearing, my understanding is that you are currently at ALL STOP.
Now I will leave the realm of fact and go to supposition. I would expect delays in communication, between you and your PEBLO, but also your PEBLO and the PEB. There's most likely just not going to be any information while this casualty is in progress. Makes sense, right, if you don't know how long the system is going to be down, you have no idea how far back everything is going to be pushed.
I would personally expect that your command will not get an official notification of this. It is probably in your best interest to let your command know that there is a process delay, and you have no idea how long it's going to be at no one has control of it right now. Again, that is just an opinion, based on principles of good communication.
Also, I want to stress that this is not a personal failure. This is no one's fault, at least no one at PEB or PEBLO level. So my advice would be to try to handle this with as much grace as you can muster, and avoid alienating your PEBLO. Being a jerk to them isn't going to solve the software/system issue at another command.
I am sure this is going to add to some people's stress load, but I figured it was better to know and understand why you might start seeing delays, rather than just get frustrated and blame the people or the overall process. Best of luck to all of you.
PEB has the capability to do boards, but there is currently no system to process cases, send or receive findings, transmit info to PERS/MMSR-4, or do internal admin.
If your case is anywhere post-IPEB hearing, my understanding is that you are currently at ALL STOP.
Now I will leave the realm of fact and go to supposition. I would expect delays in communication, between you and your PEBLO, but also your PEBLO and the PEB. There's most likely just not going to be any information while this casualty is in progress. Makes sense, right, if you don't know how long the system is going to be down, you have no idea how far back everything is going to be pushed.
I would personally expect that your command will not get an official notification of this. It is probably in your best interest to let your command know that there is a process delay, and you have no idea how long it's going to be at no one has control of it right now. Again, that is just an opinion, based on principles of good communication.
Also, I want to stress that this is not a personal failure. This is no one's fault, at least no one at PEB or PEBLO level. So my advice would be to try to handle this with as much grace as you can muster, and avoid alienating your PEBLO. Being a jerk to them isn't going to solve the software/system issue at another command.
I am sure this is going to add to some people's stress load, but I figured it was better to know and understand why you might start seeing delays, rather than just get frustrated and blame the people or the overall process. Best of luck to all of you.