***PLEASE DO NOT ATTEMPT TO SUBMIT AN SRB OR STAR REQUEST IN NSIPS. SYSTEM FUNCTIONALITY HAS NOT BEEN FULLY RESTORED. PREVIOUS ATTEMPTS TO SUBMIT SRB REQUESTS AS “INCOMPLETE” HAVE FAILED. DO NOT SUBMIT AN SRB REQUEST AS “INCOMPLETE.” AS SOON AS NSIPS FUNCTIONALITY IS FULLY RESTORED, THIS WEBSITE WILL BE UPDATED. ANY ADDITIONAL REQUIRED ACTIONS WILL THEN BE DETAILED ON THIS WEBPAGE.***
***The System outage associated with the NES and OPINS consolidation to NSIPS continues***
The original outage schedule was scheduled to conclude on July19. System functionality has not been fully restored yet. Your continued patience is appreciated.
Please do not attempt to submit STAR or SRB submissions via NSIPS. These user interfaces are not functioning, despite the appearance they may be working. If an attempt was made to submit a STAR or SRB request during any part of the system outage, it will not have been received at BUPERS 328 for processing. Continue to monitor this webpage for updates. As soon as system functionality is restored, requests should be made via NSIPS. Requests previously attempted during the outage should be resubmitted to ensure receipt at BUPERS 328.
NES and OPINS business functionality will deploy into NSIPS in July. This will necessitate a system outage for approximately two weeks in support of deploying the software changes and migrating data to NSIPS. NES and OPINS will become read only on July 3. NSIPS is projected to be online with full user access on July 19. During that period of time, we will be unable to process SRB and STAR requests. We will also be unable to process SDAP correction requests for effective dates more than 240 days old. This will have no impact on the upcoming annual SDAP recertification process. SDAP recertification will be announced soon via NAVADMIN and will be unaffected by the consolidation of NES and OPINS function into NSIPS.
To mitigate the impact of this system outage, actions will be taken as follows:
For SDAP corrections, we will process all correction requests received during this period once system functionality is restored. There should be no net negative outcomes for Sailors. Payment will be further delayed, but processing will be possible once systems are restored.
For STAR requests, we will process all incoming requests once system functionality is restored. We have already taken action to update business practices to align with improved system functionality. This process is detailed on the SRB website under the STAR section. MILPERSMAN 1160-100 requires all STAR requests to be submitted at least 60 days in advance. We will continue to be flexible with his time requirement, as we have been historically. A system outage of approximately two weeks should not result in any net negative Sailor outcomes given the long lead time normally required. We are currently working STAR requests in real time as they are received. We anticipate we will be able to manage future requests without impacting requested reenlistment dates.
The SRB Program throughput is much higher than STAR and SDAP. Nearly 1000 SRBs are approved every month. To mitigate the impact of a two week outage, SRB approvals will be temporarily pushed out much farther than normal. Typically, SRBs are approved two weeks in advance. We will have all pending requests for SRB reenlistments for dates on, or before, 210813 approved prior to the system outage. This will ensure all SRB approvals are received by commands early enough support execution. For Sailors who have not requested an SRB reenlistment yet, we will manage all requests submitted after the system is restored on a case by case basis. We understand there may be cases where the system outage will make it impossible to request an SRB 35-120 days in advance. CCCs are encouraged to contact the SRB Desk directly with questions relating to the impact of the outage for A reenlisting Sailor. Call with SSN available. We will still be able to view all Sailor data, and we will coach the command on how to manage that particular case during the outage. A 35 Day Waiver may not be required in most cases. Do not presume one is, or is not, required. Contact the SRB Desk directly for assistance. Our goal is to employ flexibility in policy application to ensure Sailors are not disadvantaged by the unavoidable system outage. It would not be possible to address all potential scenarios. SRB requests continue to be managed on a case by case basis because each case has a unique set of circumstances. An answer given for a specific case may not be applicable to other cases. When in doubt, the CCC should call the SRB Desk.
Some commands still continue to request SRBs directly via OPINS. This will not be possible once OPINS becomes read only on July 3. Commands must gain appropriate CCC access for NSIPS if they do not already have it. Commands that have been using OPINS to submit SRB requests should stop, and begin entering all SRB requests via NSIPS.
The system outage will also remove our ability to adjust requested or approved reenlistment dates or terms. SRB reenlistments are required to be executed as approved. SRB reenlistments that are executed for a different date and/or term of reenlistment are subject to cancellation. Permission must be gained in advance of execution. If the command is unable to execute a previously approved SRB reenlistment, or desires to adjust the date and/or term, the command is required to notify BUPERS 328. Contact the SRB Program Manager for assistance in managing changes during the system outage.
Selective Reenlistment Bonuses (SRB)
Current SRB Award Levels
OPNAVINST 1160.8B and NAVADMIN 108/20 govern the SRB Program. BUPERS 328 does not produce a cheat sheet or desk guide. If you are using one, then it likely does not reflect current policy and processes. Work from the above linked source documents only. When in doubt, ask the SRB Desk at BUPERS 328.
Shutdowns and Reductions
SRBs are reenlistment incentives used to maintain desired manning in specific ratings and NEC'S. SRB levels are subject to change in response to the needs of the Navy in managing community manning. SRB Shutdowns may be managed by NAVADMIN, promulgated by memo, or through an update to the Current SRB Award Level table linked above.
SRB Award Limitations
SRB ceiling caps are governed by the current SRB NAVADMIN and Department of Defense Instruction (DoDI) 1304.31. In no case can an SRB exceed $100,000.00. Current federal policy further limits SRBs to a maximum of $30,000.00 per year of additional obligated service (AOS). This limit is not currently programmed into any corporate data system. A manual intervention is required by BUPERS 328 to manually cap the SRB. Any request exceeding this criteria will initially be rejected by BUPERS 328 until the SRB can be manually capped and approved. The below linked table is provided as a tool to help determine the maximum SRB payable under the $30k cap broken down by months of AOS.
$30k LIMIT BY MONTHS OF AOS LINK
SRB Submission Guidance
SRB requests must be submitted between 35-120 days prior to reenlistment date via FORMAN / OPINS or CIMS(NSIPS).An SRB request submitted greater than 120 days will not properly upload into OPINS and cannot be prescreened. Requests passing the prescreening process will normally be processed for approval approximately one week prior to re-enlistment. Once the request is approved, the command will be notified via message traffic. Any request failing to prescreen will be rejected and a message will be sent to the command. A best practice is to view the status of the request in BOL two to three workdays after submission. A valid request should reflect a pending SRB for the date requested, and the total award should match the expectations of the requestor.
35 Day Waiver Guidance
SRB requests must be submitted 35-120 days prior to the reenlistment date. A waiver request should be viewed as a significant course of action and should be used in the rare case of Career Development Team oversight. That oversight may include an unreasonable delay in routing, inadequate or incorrect career counseling to the member, SRB reductions and closures are not in themselves justification to waive the 35 day requirement. There would need to be some other failure attributable to the command that prevented the member from acting reasonably to submit a request that could beat the reduction and still meet 35 days from the time of the original request. 35 Day Waiver Requests must include the following IAW the below linked Decision Memorandum:
A CO endorsed request for a 35 Day Waiver on command letterhead
A copy of any reenlistment request chits and any other supporting documentation to help explain why the request
could not be submitted on time
An ISIC endorsement to the CO’s request
NOTE: BY DIRECTION SIGNATURES ARE NOT AUTHORIZED ON WAIVER REQUESTS
Decision Memorandum link
35 Day Waiver Letter Example
Forward complete 35 Day Waiver request to ETNCM(SW/AW) James Gale at INCENTIVE PAY firstname.lastname@example.org and ensure the subject line states "35 Day Waiver Request ICO (MEMBER) FOR REENLISTMENT ON (DATE)".
Selective Training and Reenlistment (STAR)
MILPERSMAN 1160-100 and Career School Listing (CSL) governs the STAR program. The STAR program offers career designation to first term enlisted members who enlist or reenlist and thereby become eligible for the following career incentives:
Guaranteed assignment to an appropriate Class “A” or “C” School (but not both).
Possible advancement from Petty Officer Third Class (PO3) to Petty Officer Second Class (PO2)
upon completion of a Class “C” School, which is listed in the Career Schools Listing (CSL).
Advancement to PO3 upon completion of Phase I of an Advanced Electronics Field (AEF)
Class “A” School under automatic advancement procedures for the AEF program.
Selective Reenlistment Bonus (SRB), if eligible (not guaranteed).
Opens SRB window to one year prior to EAOS.
To be eligibility for a STAR re-enlistment the enlisted member must be on their first enlistment, with more than 21 months active duty and less than 6 years active duty. The member must also have no evaluation grade below 3.0 for 2 years prior to the submission date to BUPERS 328, no NJP for 18 months prior to the submission date, nor may not have been accepted for any commissioning programs.
STAR Submission Guidance
Submit STAR requests directly in NSIPS. OPINS functionality is in the process of being migrated to NSIPS. BUPERS-328 will no longer manually enter STAR requests directly into OPINS in response to 1306/7 requests submitted by commands. Do not submit 1306/7 requests via email or MNCC. 1306/7 requests submitted via email or via MNCC will be returned without action. For commands with OPINS access, do not attempt to submit a STAR request directly into OPINS. Commands must gain appropriate NSIPS access, and submit all requests via NSIPS.
The ability to submit a STAR request via NSIPS is an existing functionality of NSIPS. BUPERS-328 has continued to support STAR requests via 1306/7 because the evaluation data fields in NSIPS do not transmit correctly to OPINS because of date formatting conflicts. STAR requests submitted previously via NSIPS required the command to separately email the evaluation data to BUPERS-328 for manual entry. Evaluation data must still be separately transmitted to BUPERS-328 after the STAR request has been submitted in NSIPS. This short term bridging action will be necessary until the migration is complete. This inconvenience is unavoidable, and is temporary. As soon as this additional step is no longer necessary, the SRB website will be updated.
The BUPERS-328 processing time for a STAR request will be markedly improved once the system migration is complete. This will allow BUPERS-328 to remain flexible with the MILPERSMAN 1160-100 requirement to submit the STAR request at least 60 days in advance while the system migration is in process.
CAREER SCHOOL LISTING (CSL)
The career schools listing, which establishes specific eligibility requirements for automatic advancement via the Selective Training and Reenlistment (STAR) program. In keeping with the Navy's total force integration, these programs further the training of our high-quality Sailors and reward them for their valuable contributions. This update supersedes all previous career schools listings.
Career School Listing (CSL)
Effective: 1 July 2020
Point of Contact for CSL: HMCS Jason Marnne, email@example.com
Point of Contact for STAR: PSC Kisha Granger, firstname.lastname@example.org
Special Duty Assignment Pay (SDAP)
SDAP is a monthly incentive pay used to entice qualified personnel to accept designated assignments and to sustain adequate manning levels.
In order to qualify for SDAP, member must be assigned to and working in a valid billet via the Billet Based Distribution System. The NEC/Billet must be authorized on the current SDAP Levels Chart. The member must hold the NEC and be filling billet type in order to qualify for SDAP and be authorized by the Command Officer. The CO's signature verifies the command is not exceeding Billet Authorized; member is working in a valid NEC/Billet type on the NAVADMIN, and holds the NEC (if paid based on NEC vice Billet Type).
Current SDAP Levels
SDAP Levels with Admin Updates
For members receiving SDAP for a special duty assignment that is marked for reduction, the reduction will take effect 60 days(4 Jan 2021) after release of the Eligibility chart announcing the reduction. For all new personnel becoming eligible for the special duty assignment after the release of the Eligibility chart, SDAP will be started at the lower SD level.
Effective: 21 July 2021
OPNAVINST 1160.6 (series), the current SDAP NAVADMIN, and the SDAP Levels Chart governs the SDAP program. SDAP Levels is directive in nature and applies to levels for both USN and FTS personnel. Specific policy guidance associated with this plan, as well as assignments authorized to receive SDAP, are contained within. Commands and servicing PSDs are responsible for administering all applicable changes to SDAP in accordance with referenced policy and Eligibility Chart.
SDAP Submission Guidance
Per NAVADMIN 139/18, PSDs may start the SDAP of a Sailor up to eight months retroactive to the date of the SDAP memo of the command. SDAP requests that are greater than eight months must be submitted to BUPERS-328 via the Incentive Inbox or directly to the SDAP POC. The request also requires a letter signed by the Immediate Superior in Command of the command explaining why the SDAP of the member was not processed in a timely manner. NOTE: BY DIRECTION SIGNATURES ARE NOT AUTHORIZED. Any request that exceeds eight months that does not have the ISIC endorsement letter or is signed by direction will be returned without any action taken.
Submitted via INCENTIVE PAY email@example.com
SDAP Pay Decision Logic Chart IAW NAVADMIN 139/18 Para. 6
The following OPNAV N130 process has been developed to establish the method for submitting request for SDAP changes.
SDAP CHANGE REQUEST
Point of Contact for SDAP: PSC Kisha Granger, firstname.lastname@example.org
Point of Contact for SDAP Change Request: CTRCM(IW/SW) Eric Titus, email@example.com
SDAP ANNUAL RECERTIFICATION
The Special Duty Assignment Pay Recertification is conducted annually to ensure commands are maintaining an accurate account of member’s eligibility for SDAP.
The recertification begins with release of NAVADMIN 146/21 and must be received by BUPERS 328 by 31 August.
Effective: 03 July 2021
Commands will be able to download the spreadsheet that covers their respective UIC and verify the re-certification was received. Commands with subordinate commands are strongly encouraged to check on their tenant and subordinate commands. Please allow 5 to 10 days after submission for the webpage to be updated.
SDAP 2021 RECERT 14JUL2021
If prompted for CAC cert hit cancel and it should pull up file
Enlistment Bonuses (EB)
OPNAVINST 1160.9 governs the EB Program. Commander Navy Recruiting Command (CNRC) will periodically release Program Messages offering various types of EBs to Sailors to incentivize enlistment. These messages can be located on the CNRC Webpage.
FSC Great Lakes will initiate payment of EBs associated with successful completion of Basic Training upon graduation. Enlistment Bonuses for Source Ratings should be paid by the servicing PSD associated with the A School. If the member is detached from A School prior to payment, then the gaining command will need to take action to request processing and payment of the bonus.
The EBPFA is offered as an incentive to increase physical readiness upon reporting to RTC. The PFA under consideration is the baseline PFA administered in the first week of training. Not everyone who is offered EBPFA will earn it. If the baseline PFA is passed, the bonus should be paid by Great Lakes upon graduation. If the member was guaranteed an EBPFA bonus, yet remains unpaid, odds are quite high the member did not actually pass the baseline PFA at RTC. If the member is insistent they passed, then the command should coordinate with their servicing PSD to contact the Bonus Section at FSC Great Lakes. The Bonus Section staff can quickly validate whether the EBPFA was earned by reviewing the baseline PFA data if they are provided the member’s full name and RTC division number. The PFA under consideration is not documented in PRIMS.
If a member has not received payment for any other earned enlistment guarantee, then the command CPPA should submit the member’s DD Form 4 and applicable Annex to DD Form 4 to their servicing PSD via TOPS and request processing. The servicing PSD will then be able to process the request using the authority and procedures outline in Military Pay Advisories (MPAs) 16-19 and 17-19.
BUREAU OF NAVAL PERSONNEL THREE (BUPERS 3)
MILITARY COMMUNITY MANAGEMENT
ATTN: (BUPERS 328) BLDG 453 RM 338
5720 INTEGRITY DRIVE
MILLINGTON, TN 38055-0003