Navy PEB processing timeline to be delayed

PERS-95

Well-Known Member
PEB Forum Veteran
Registered Member
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.
 
Any news on how long it will take to have the system back up and running? I cant see them taking months to fix something that they've had for years.
 
Any news on how long it will take to have the system back up and running? I cant see them taking months to fix something that they've had for years.
I don't know the answer to that, but it's not as simple as just getting the system up and running. They are also *potentially* dealing with data loss. They just don't know the scope of the problem yet as far as I am aware.
 
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.

Might be a difficult question to answer, and honestly I don't expect you to have an official answer, but is the system the Navy and USMC potentially tied to other service branches, i.e. do they all use the same system?

I only ask, since I have been in the IPEB process for close to 2 months and everytime I inquire about a status I always get a different narrative for the same situation as if they don't actually know because there is nothing to look at.
I appreciate any info.
 
Might be a difficult question to answer, and honestly I don't expect you to have an official answer, but is the system the Navy and USMC potentially tied to other service branches, i.e. do they all use the same system?

I only ask, since I have been in the IPEB process for close to 2 months and everytime I inquire about a status I always get a different narrative for the same situation as if they don't actually know because there is nothing to look at.
I appreciate any info.
I don't know, that's a really good question. I don't know the full scope of what Navy lost, but my guess is that they probably don't use the same system, just based on my knowledge of how the individual services work. And, it just happened within the last couple of days, so any issues in the weeks or months prior to this were not related.
 
UPDATE UPDATE UPDATE
Distributed 9/14
----------

For 27 years, Joint Disability Evaluation Tracking System (JDETS) has served as the PEB’s internal case-tracking system. Unfortunately, in early August PEB personnel started losing access to JDETS due to what is believed to have been an Oracle Client error. Efforts to locate the problem and find a solution were immediately begun with the assistance of DON CIO and initially we thought we had rebounded. However, two weeks ago, PEB personnel again started losing access to JDETS and by last Friday, all access was lost. We have been told that NMCI may have inadvertently removed some Oracle software from the network that led to the JDETS disconnect. We have no estimate as to when, or if, the Oracle software will be reinstalled on the network.

Prior to the loss of JDETS, we had already been in the process of developing a new case-tracking system (Naval Disability Integrated Tracking System (NDITS)), however, NDITS is at least a year out from being fielded. When the first degradation occurred in early August, we anticipated additional problems and started work on an interim tracking system as a stopgap measure until NDITS comes on line. At this time, we do not have an estimate as to when the interim tracking system will be ready to deploy, although significant progress has been made in the past two weeks. Since the PEB does not currently have the capability to actively process the 3,700+ cases at the PEB, we are limited, if not hindered completely, in our capability to:

--Issue Informal PEB, Formal PEB, or Petition for Relief findings
--Process Elections of Options or VA Reconsiderations
--Finalize cases.

The PEB is:

--Accepting new cases, though not inserting them into the PEB process
--Accepting Temporary Disability Retired List exams, though not adjudicating them
--Accepting Elections of Options, though not processing them
--Conducting Formal PEB hearings, though not issuing the findings
--Accepting Petitions for Relief.

The PEB is NOT:

--Issuing the weekly JDETS report
--Presume accepting cases.

The JDETS system failure has not resulted in the loss, compromise, or spillage of any case data or individual Service member PII or HPI. For those who work with individual Service members, please assure them that their personal information has not been compromised. Additionally, the data of existing cases has not been lost and will be ported over to the interim tracking system. None of the 3,700+ cases at the PEB will have to be rebuilt or restarted. For now, the primary unfortunate result of the JDETs failure will be longer case processing times, though I do not anticipate processing times to rise to the unprecedented levels experienced earlier this year.

This remains a very fluid situation that we are striving to resolve as soon as possible. More to follow.

This email is approved for further distribution.
 
UPDATE UPDATE UPDATE
Distributed 9/14
----------

For 27 years, Joint Disability Evaluation Tracking System (JDETS) has served as the PEB’s internal case-tracking system. Unfortunately, in early August PEB personnel started losing access to JDETS due to what is believed to have been an Oracle Client error. Efforts to locate the problem and find a solution were immediately begun with the assistance of DON CIO and initially we thought we had rebounded. However, two weeks ago, PEB personnel again started losing access to JDETS and by last Friday, all access was lost. We have been told that NMCI may have inadvertently removed some Oracle software from the network that led to the JDETS disconnect. We have no estimate as to when, or if, the Oracle software will be reinstalled on the network.

Prior to the loss of JDETS, we had already been in the process of developing a new case-tracking system (Naval Disability Integrated Tracking System (NDITS)), however, NDITS is at least a year out from being fielded. When the first degradation occurred in early August, we anticipated additional problems and started work on an interim tracking system as a stopgap measure until NDITS comes on line. At this time, we do not have an estimate as to when the interim tracking system will be ready to deploy, although significant progress has been made in the past two weeks. Since the PEB does not currently have the capability to actively process the 3,700+ cases at the PEB, we are limited, if not hindered completely, in our capability to:

--Issue Informal PEB, Formal PEB, or Petition for Relief findings
--Process Elections of Options or VA Reconsiderations
--Finalize cases.

The PEB is:

--Accepting new cases, though not inserting them into the PEB process
--Accepting Temporary Disability Retired List exams, though not adjudicating them
--Accepting Elections of Options, though not processing them
--Conducting Formal PEB hearings, though not issuing the findings
--Accepting Petitions for Relief.

The PEB is NOT:

--Issuing the weekly JDETS report
--Presume accepting cases.

The JDETS system failure has not resulted in the loss, compromise, or spillage of any case data or individual Service member PII or HPI. For those who work with individual Service members, please assure them that their personal information has not been compromised. Additionally, the data of existing cases has not been lost and will be ported over to the interim tracking system. None of the 3,700+ cases at the PEB will have to be rebuilt or restarted. For now, the primary unfortunate result of the JDETs failure will be longer case processing times, though I do not anticipate processing times to rise to the unprecedented levels experienced earlier this year.

This remains a very fluid situation that we are striving to resolve as soon as possible. More to follow.

This email is approved for further distribution.
can you keep updating this as emails come around? thank you.
 
This info from PERS-95 is spot on accurate. While the powers that be are working on an interim fix, some PEBLOs nationwide have taken the initiative by providing an abridged version of the email sent to key Navy DES personnel to provide to your command if needed. They can do so because the message was authorized for redistribution. This may be necessary for those of you in need of extensions due to the approach of your EAOS while an interim fix is being put into place.
 
@PERS-95

Thank you for the update. It will be helpful to many.

Ron
 
UPDATE UPDATE UPDATE 9/20

System has been returned to operational. Navy and Marine Corps cases are moving again.
Thank you very much and I can confirm, my buddy got his findings today. I am 3 days behind him so hopefully will be getting mine this week.
 
Top