ADMINISTRATIVE MESSAGE PRIORITY P 031208Z OCT 00 ZYB MIN PSN 356322J21 FM CNO WASHINGTON DC//N1// TO NAVADMIN UNCLAS //N1080// PART ONE OF TWO PART TWO IDENT IS 031209Z OCT 00 NAVADMIN 255/00 MSGID/GENADMIN/N130C// SUBJ/INDIVIDUAL PERSONNEL TEMPO (ITEMPO) PROGRAM// REF/A/DOC/NDAA FOR FY00/05OCT1999// REF/B/DOC/DMRSMAN/09DEC1997// REF/C/DOC/DRAFT USERS MANUAL FOR ITEMPO/25AUG2000// NARR/REF A IS THE NATIONAL DEFENSE AUTHORIZATION ACT FOR FISCAL YEAR 2000, WHICH LEGISLATES ITEMPO. REF B IS THE DIARY MESSAGE REPORTING SYSTEM MANUAL (DMRSMAN). REF C IS A DRAFT VERSION OF THE USER'S MANUAL FOR THE NAVY INDIVIDUAL PERSONNEL TEMPO (ITEMPO) PROGRAM WHICH PROVIDES DETAILED INFORMATION REGARDING ITEMPO POLICIES AND PROCEDURES. A FINAL VERSION IS EXPECTED TO BE PUBLISHED IN THE FIRST QUARTER OF FISCAL YEAR 2001.// RMKS/1. INTRODUCTION: REF A MANDATES THAT THE MILITARY SERVICES MUST IMPLEMENT A SYSTEM TO TRACK AND MANAGE, ON AN INDIVIDUAL BASIS, THE PERSONNEL TEMPO OF EVERY MEMBER OF THE ARMED FORCES. FOR THE NAVY, THIS NEW PROGRAM HAS BEEN DESIGNATED AS THE INDIVIDUAL PERSTEMPO (ITEMPO) PROGRAM. UNLIKE OTHER NAVY PERSTEMPO INITIATIVES WHICH PERTAIN TO A UNIT AS A WHOLE, THIS PROGRAM WAS DEVELOPED TO HELP ACCOUNT FOR, AND MANAGE THE AMOUNT OF TIME EVERY SAILOR IN THE NAVY - OFFICER AND ENLISTED, ACTIVE AND RESERVE - IS REQUIRED TO BE AWAY FROM HIS OR HER PERMANENT DUTY STATION (PDS)/HOMEPORT. AS THE NATION'S EXPEDITIONARY "911" FORCE, WE MUST REMAIN VIGILANT, ALWAYS BE READY TO GO ANYWHERE IN THE WORLD ON A MOMENT'S NOTICE, AND MAINTAIN OUR CONTINUOUS FORWARD PRESENCE AROUND THE GLOBE. HOWEVER, OUR NAVY LEADERS RECOGNIZE THAT WE MUST BALANCE, TO THE GREATEST EXTENT PRACTICABLE, THE NAVY'S GLOBAL COMMITMENTS, ALONG WITH THE TIME SAILORS MUST BE AWAY FROM THEIR HOMEPORT AND SEPARATED FROM THEIR FAMILIES. THE ITEMPO PROGRAM IS INTENDED TO HELP US DO THAT. 2. THE ITEMPO PROGRAM WILL NOT ONLY TRACK UNDERWAY PERIODS FOR SHIPBOARD SAILORS, BUT WILL ALSO TRACK TIME AWAY FROM A PDS/HOMEPORT FOR SAILORS ATTACHED TO OTHER DEPLOYING MOBILE UNITS (SUCH AS SQUADRONS AND SEABEE MOBILE CONSTRUCTION BATTALIONS) AS WELL AS CERTAIN TEMPORARY ADDITIONAL DUTY (TAD) PERIODS FOR SAILORS ASSIGNED TO SHORE COMMANDS. ADDITIONALLY, THE PROGRAM WILL TRACK THOSE OCCASIONS WHEN A SAILOR IS IN HOMEPORT, BUT IS UNABLE (DUE TO MILITARY NECESSITY) TO SPEND OFF-DUTY TIME AT HIS/HER CIVILIAN RESIDENCE. FOR THE RESERVE COMPONENT, THE ITEMPO PROGRAM WILL APPLY IN CERTAIN INSTANCES WHEN RESERVISTS ARE PERFORMING ACTIVE DUTY. THE PROGRAM WILL REQUIRE THE INVOLVEMENT OF EVERY NAVY UNIT AND WILL PROVIDE UNIT CO'S, OIC'S, COMMANDERS, TYCOM'S, ETC., AS WELL AS THE MOST SENIOR LEADERS OF OUR NAVY WITH THE TOOLS THEY NEED TO TRACK AND MANAGE THE ITEMPO OF EVERY SAILOR IN THE NAVY. IT WILL REQUIRE THAT FLAG LEVEL DECISION-MAKERS ENSURE SAILORS ARE CONTINUED ON DEPLOYMENT BEYOND A CERTAIN NUMBER OF DEPLOYMENT DAYS ONLY WHEN NECESSARY, AND LASTLY, IT WILL PROVIDE MONETARY COMPENSATION TO SAILORS WHOSE JOBS, ASHORE AND AFLOAT, REQUIRE EXCESSIVE DEPLOYMENT TIME. 3. COMMENCEMENT OF ITEMPO ACCOUNTING: ACTION OFFICERS FROM BUPERS AND OPNAV (N1) STAFFS HAVE BEEN CONDUCTING BRIEFINGS AROUND THE WORLD IN ORDER TO INFORM THE FLEET ABOUT THE NAVY'S ITEMPO PROGRAM. THIS NAVADMIN, HOWEVER, PROVIDES THE OFFICIAL DIRECTION TO ALL NAVY UNITS, AND ALL NON-NAVY UNITS WITH NAVY PERSONNEL ATTACHED, TO COMMENCE TRACKING THE ITEMPO OF NAVY MEMBERS EFFECTIVE 1 OCT 00. IT ALSO PROVIDES INITIAL GUIDANCE WRT THE ITEMPO PROGRAM AND PROVIDES INFORMATION REGARDING WHERE COMMANDS MAY OBTAIN FURTHER DETAILS CONCERNING ITEMPO POLICIES AND PROCEDURES. OVERVIEW OF THIS NAVADMIN IS AS FOLLOWS: PARA 4 ITEMPO EVENTS PARA 5 NON-ITEMPO EVENTS PARA 6 ITEMPO HIGH-DEPLOYMENT PAY PARA 7 DEFINITIONS PARA 8 ITEMPO DATA SYSTEM/TRANSACTIONS PARA 9 ITEMPO 'GATES' AND FLAG APPROVALS FOR CONTINUED DEPLOYMENTS PARA 10 ADDITIONAL ITEMPO INFORMATION PARA 11 POINTS OF CONTACT PARA 12 CNP COMMENTS AS DISCUSSED DURING THE RECENT ITEMPO BRIEFINGS, SOME CHANGES TO ITEMPO LEGISLATION ARE CURRENTLY BEING CONSIDERED BY CONGRESS. THIS NAVADMIN SHOULD BE CONSIDERED AS AN INITIAL POLICY DOCUMENT. COMMANDS SHOULD REMAIN AWARE THAT ADDITIONAL POLICIES WILL BE PUBLISHED AS ITEMPO ISSUES ARE RESOLVED. 4. ITEMPO EVENTS: FOR PURPOSES OF THE ITEMPO PROGRAM, ITEMPO EVENTS CAN BE DIVIDED INTO TWO BROAD CATEGORIES, I.E., ITEMPO DEPLOYMENT EVENTS AND ITEMPO NON-DEPLOYMENT EVENTS. THESE TWO CATEGORIES ARE DEFINED AS FOLLOWS: A. ITEMPO DEPLOYMENT EVENT: A MEMBER IS CONSIDERED TO BE DEPLOYED OR IN A DEPLOYMENT ON ANY DAY ON WHICH, PURSUANT TO ORDERS, THE MEMBER IS PERFORMING SERVICE AT A LOCATION OR UNDER CIRCUMSTANCES THAT MAKE IT IMPOSSIBLE OR INFEASIBLE FOR THE MEMBER TO SPEND OFF-DUTY TIME IN THE HOUSING IN WHICH THE MEMBER RESIDES IN THE LOCAL AREA OF THE MEMBER'S PDS OR HOMEPORT. ADDITIONALLY, FOR MEMBERS ASSIGNED TO VESSELS, THE MEMBER SHALL ALSO CONSIDERED TO BE DEPLOYED ON ANY DAY IN WHICH THE MEMBER IS ON BOARD THE VESSEL AND THE VESSEL IS AWAY FROM ITS HOMEPORT. FOR ITEMPO PURPOSES, A MEMBER IS NOT CONSIDERED TO BE DEPLOYED WHEN THE MEMBER IS- (1) PERFORMING SERVICE AS A STUDENT OR TRAINEE AT A SCHOOL (INCLUDING ANY GOVERNMENT SCHOOL); (2) PERFORMING MILITARY DUTIES (I.E., PART OF A DUTY SECTION WHICH REQUIRES AN OVERNIGHT PRESENCE ON BOARD THE UNIT) AT THE PDS OR IN HOMEPORT; OR (3) IS UNAVAILABLE SOLELY BECAUSE OF THE HOSPITALIZATION OF THE MEMBER IN THE LOCAL AREA OF THE MEMBER'S PDS OR HOMEPORT OR DISCIPLINARY ACTION TAKEN AGAINST THE MEMBER. B. ITEMPO DEPLOYMENT EVENT ICO OF A RESERVIST: A RESERVIST IS CONSIDERED TO BE DEPLOYED WHEN PERFORMING ACTIVE SERVICE ON ANY DAY ON WHICH, PURSUANT TO ORDERS THAT DO NOT ESTABLISH A PERMANENT CHANGE OF STATION (PCS), THE MEMBER IS PERFORMING THE ACTIVE SERVICE AT A LOCATION THAT- (1) IS NOT AT THE MEMBER'S PERMANENT TRAINING SITE (PTS); AND (2) IS AT LEAST 100 MILES ROUND TRIP OR 3 HOURS ROUND TRIP TRAVEL (VIA AUTOMOBILE) FROM THE MEMBER'S PERMANENT CIVILIAN RESIDENCE. C. ITEMPO NON-DEPLOYMENT EVENT: IN GENERAL, ITEMPO NON-DEPLOYMENT EVENTS INCLUDE THOSE EVENTS DESCRIBED IN PARA 4.A.(1) AND 4.A.(3) ABOVE. THESE ARE ITEMPO EVENTS THAT DO NOT COUNT TOWARDS HIGH DEPLOYMENT PAY BUT MUST BE TRACKED AND REPORTED TO NAVY CORPORATE SYSTEMS. D. EXAMPLES OF ITEMPO DEPLOYMENT EVENTS ARE: UNDERWAY PERIODS FOR MEMBERS ASSIGNED TO NAVY SHIPS OR VESSELS (INCLUDING AT-SEA PERIODS IN THE LOCAL OPERATING AREA); PARTICIPATION IN AN OPERATION, EXERCISE, ETC., OUTSIDE THE LOCAL AREA OF THE PDS OR HOMEPORT; MAJOR DEPLOYMENT; EMBARKATION OF AN AIRCRAFT SQUADRON TO A SHIP OR VESSEL THAT IS HOMEPORTED OUTSIDE THE LOCAL AREA OF THE HOMEPORT OF THE SQUADRON; EMBARKATION TO A SHIP OR VESSEL THAT IS UNDERWAY OR WILL GET UNDERWAY ON THE DAY OF EMBARKATION; SORTIE OF NAVAL AIRCRAFT FROM THE LOCAL AREA OF THE PDS OR HOMEPORT; OFFICIAL TAD/TDY TRAVEL (EXCEPT PERMISSIVE TAD, TAD WITHIN THE LOCAL AREA THAT DOES NOT PREVENT THE MEMBER FROM RETURNING TO HIS/HER RESIDENCE DURING OFF-DUTY TIME, OR TAD/TDY/TEMDU TO ATTEND A SCHOOL); HOME STATION TRAINING (I.E., TRAINING/SERVICE PERFORMED ON BOARD THE PDS, OR WITHIN THE LOCAL AREA OF THE PDS/HOMEPORT, WHICH REQUIRES THE OVERNIGHT PRESENCE OF THE MEMBER); ETC. FOR RESERVISTS, ITEMPO DEPLOYMENT EVENTS WOULD INCLUDE PERIODS OF ANNUAL TRAINING (AT), ACTIVE DUTY TRAINING (ADT), AND ACTIVE DUTY FOR SPECIAL WORK (ADSW) THAT MEET THE DEFINITION IN PARAGRAPH 4.B. IN ADDITION, IF A RESERVIST WERE PERFORMING ACTIVE DUTY THAT IN AND OF ITSELF DID NOT QUALIFY AS AN ITEMPO DEPLOYMENT EVENT, BUT DURING THAT ACTIVE DUTY PARTICIPATED IN AN EVENT THAT MET THE DEFINITION IN PARAGRAPH 4.A., THAT RESERVIST WOULD CONSIDERED TO BE DEPLOYED FOR THAT PERIOD. FOR EXAMPLE, A RESERVIST PERFORMS ONE MONTH OF ADSW ABOARD A NAVY SHIP THAT IS THE RESERVIST'S PTS; DURING THE ADSW THE SHIP (WITH THE RESERVIST ABOARD) GETS UNDERWAY FOR SIX DAYS; THE RESERVIST WOULD BE CONSIDERED TO BE DEPLOYED FOR THE DAYS IN WHICH THE SHIP WAS UNDERWAY. E. EXAMPLES OF ITEMPO NON-DEPLOYMENT EVENTS ARE: DAYS IN WHICH A MEMBER IS TAD/TDY OUTSIDE THE LOCAL AREA OF THE PDS OR HOMEPORT TO A SCHOOL; DAYS IN WHICH A MEMBER IS HOSPITALIZED WITHIN THE LOCAL AREA OF THE PDS OR HOMEPORT; AND DAYS IN WHICH A MEMBER IS TAD/TDY TO A BRIG AS A PRISONER (OR IS OTHERWISE DEPLOYED SOLELY BECAUSE OF DISCIPLINARY REASONS). 5. NON-ITEMPO EVENTS: ALTHOUGH NOT SPECIFICALLY AN ITEMPO EVENT CATEGORY, NON-ITEMPO EVENTS ARE DAYS IN WHICH A MEMBER IS PARTICIPATING IN AN ACTIVITY THAT DOES NOT REQUIRE ITEMPO DATA REPORTING OR DOES NOT MEET THE DEFINITION OF AN ITEMPO DEPLOYMENT EVENT OR ITEMPO NON-DEPLOYMENT EVENT. EXAMPLES OF NON-ITEMPO EVENTS INCLUDE: NORMAL WORKDAYS AT THE PDS, OR IN HOMEPORT (IN THE CASE OF MEMBERS ASSIGNED TO SHIPS OR VESSELS); PCS TRANSIT TIME (I.E., THAT PERIOD OF TIME THAT BEGINS UPON DETACHMENT FROM ONE PDS AND ENDS UPON REPORTING TO THE NEXT PDS); PERIODS OF PERMISSIVE TAD/TDY; LEAVE (MEMBERS ON DEPLOYMENTS SCHEDULED TO EXCEED 120 DAYS WILL CONTINUE TO ACCRUE ITEMPO DEPLOYMENT DAYS WHILE ON LEAVE AS LONG AS THE MEMBER REMAINS IN THE DEPLOYED AREA, AND THE PERIOD OF LEAVE DOES NOT EXCEED FOUR DAYS IN LENGTH); TAD/TDY PERIODS PERFORMED IN THE LOCAL AREA OF THE PDS OR HOMEPORT THAT DO NOT PREVENT THE MEMBER FROM RETURNING TO HIS/HER RESIDENCE DURING OFF-DUTY TIME, ETC. RESERVE SPECIFIC EXAMPLES INCLUDE: PERIODS OF INACTIVE DUTY FOR TRAINING; INACTIVE DUTY FOR TRAINING TRAVEL; MUSTER DUTY; AND FUNERAL HONORS DUTY. 6. HIGH-DEPLOYMENT PAY: REF A ESTABLISHES ENTITLEMENT TO HIGH-DEPLOYMENT PAY FOR MEMBERS WHOSE ITEMPO DEPLOYMENT DAYS EXCEED A CONGRESSIONALLY MANDATED THRESHOLD AND WHO, AT THE TIME THEY EXCEED THE THRESHOLD, CONTINUE TO BE DEPLOYED. THIS PAY, SET AT $100 PER DAY, DOES NOT BECOME EFFECTIVE UNTIL 1 OCT 01. CURRENTLY, SIGNIFICANT ISSUES REGARDING THE PAY REMAIN UNRESOLVED, INCLUDING A CONGRESSIONAL DETERMINATION OF THE APPROPRIATE THRESHOLD THAT MUST BE EXCEEDED IN ORDER TO QUALIFY FOR THE PAY. DUE TO UNCERTAINTIES SURROUNDING HIGH-DEPLOYMENT PAY, AS WELL AS THE FACT THAT IT DOES NOT BECOME EFFECTIVE UNTIL 1 OCT 01, THIS NAVADMIN DOES NOT ADDRESS SPECIFIC DETAILS REGARDING ITEMPO HIGH-DEPLOYMENT PAY. ONCE CONGRESS RESOLVES ISSUES SURROUNDING THE PAY, FURTHER INFORMATION WILL BE PUBLISHED. 7. DEFINITIONS: THE FOLLOWING DEFINITIONS APPLY TO THE NAVY ITEMPO PROGRAM: A. DISCIPLINARY ACTION - THE RESTRAINT OF A MEMBER AS A RESULT OF HIS OR HER MISCONDUCT OR ALLEGED MISCONDUCT SUCH THAT THE MEMBER IS UNAVAILABLE TO HIS OR HER UNIT. B. HOMEPORT/PERMANENT DUTY STATION (PDS) - THE POST OF DUTY OR OFFICIAL STATION, OF A MEMBER INCLUDING A SHIP. THE HOMEPORT OF A SHIP OR OF A SHIP-BASED STAFF TO WHICH A MEMBER IS ASSIGNED OR ATTACHED FOR DUTY OTHER THAN TEMPORARY DUTY (TAD, TDY, TEMDU). THE LIMITS OF THE POST OF DUTY OR OFFICIAL STATION ARE THE SHIP OR THE CORPORATE LIMITS OF THE CITY OR TOWN IN WHICH THE MEMBER IS STATIONED. IF THE MEMBER IS NOT STATIONED ON A SHIP OR IN AN INCORPORATED CITY OR TOWN, THE OFFICIAL STATION LIMITS ARE THE RESERVATION, STATION, OR ESTABLISHED AREA, WITHIN WHICH THE DESIGNATED POST OF DUTY IS LOCATED. C. LOCAL AREA OF THE PDS OR HOMEPORT - THE LOCAL AREA IS THE AREA: (1) WITHIN THE DUTY STATION LIMITS (PERMANENT OR TEMPORARY) AND THE METROPOLITAN AREA AROUND THAT STATION WHICH IS ORDINARILY SERVED BY LOCAL COMMON CARRIERS; OR (2) WITHIN A LOCAL COMMUTING AREA OF THE DUTY STATION, THE BOUNDARIES OF WHICH ARE NORMALLY DETERMINED BY AN ORDER-ISSUING OFFICIAL OR AS PRESCRIBED BY LOCAL SERVICE DIRECTIVES; OR (3) INCLUSIVE OF SEPARATE CITIES, TOWNS, OR INSTALLATIONS ADJACENT, OR CLOSE TO EACH OTHER, BETWEEN WHICH THE COMMUTING PUBLIC TRAVELS DURING NORMAL BUSINESS HOURS ON A DAILY BASIS (AN ARBITRARY DISTANCE RADIUS SHALL NOT BE ESTABLISHED TO DEFINE A LOCAL COMMUTING AREA); OR (4) WITHIN A LOCAL COMMUTING AREA IN WHICH NO ENTITLEMENT TO PER DIEM ARISES AS A RESULT OF TEMPORARY ASSIGNMENT (TAD, TDY, ETC.) FROM ONE ACTIVITY TO ANOTHER WITHIN THE AREA, OR IN WHICH NO ENTITLEMENT TO MOVEMENT OF HOUSEHOLD GOODS ARISES AS A RESULT OF A PCS FROM ONE ACTIVITY TO ANOTHER, BECAUSE THE ACTIVITIES ARE GENERALLY ACCEPTED TO BE LOCATED IN CLOSE PROXIMITY. D. ITEMPO DAY - AN ITEMPO EVENT DAY IS ANY TIME IN WHICH AN ITEMPO EVENT BEGINS ON ONE DAY AND ENDS ON ANOTHER DAY. AN ITEMPO DAY IS NOT REQUIRED TO BE A FULL 24 HOURS. FOR ITEMPO ACCOUNTING/TRACKING PURPOSES THE DAY OF RETURN WILL NOT COUNT AS AN ITEMPO DAY. E. SCHOOL - ANY INDIVIDUAL TRAINING PROVIDED TO A MEMBER UTILIZING FEDERAL GOVERNMENT APPROPRIATIONS THAT HAS A SERVICE-DESIGNATED COURSE OF INSTRUCTION CODE OR NUMBER ASSIGNED. 8. ITEMPO DATA SYSTEM/TRANSACTIONS: AS STATED ABOVE, REF A REQUIRES THAT THE ITEMPO OF EVERY MEMBER BE TRACKED AND MANAGED. BY NECESSITY, THIS REQUIRES THAT DATA COLLECTION MUST ORIGINATE AT THE UNIT LEVEL. OPNAV (N1), BUPERS, AND NRISO HAVE WORKED TOGETHER TO DEVELOP A NAVY-WIDE ITEMPO DATA SYSTEM, WHICH BECAUSE OF THE LIMITED TIME AVAILABLE FOR DESIGN AND DEVELOPMENT, AS WELL AS FUNDING CONSTRAINTS, IS BEING IMPLEMENTED IN THREE BASIC PHASES. A. PHASE 1 (1 OCT 00 - JUN 01): USES ENTERPRISE-WIDE LEGACY SYSTEMS TO IMPLEMENT ITEMPO DATA/STORAGE REQUIREMENTS. DATA (WRT BOTH ACTIVE AND RESERVE MEMBERS) IS SUBMITTED TO CORPORATE DATABASES VIA NAVY GENADMIN MESSAGE USING THE DIARY MESSAGE REPORTING SYSTEM (DMRS) AS THE INPUT VEHICLE. DATA SUBMISSIONS SHALL BE IAW REFS B AND C (THE DMRS MANUAL AND THE DRAFT ITEMPO USER'S MANUAL, RESPECTIVELY). DMRS IS A RELIABLE AND PROVEN SYSTEM, USED FOR MANY YEARS THROUGHOUT THE NAVY (MOST OF ITS FUNCTIONS HAVE BEEN ASSUMED BY THE SOURCE DATA SYSTEM (SDS AND SDS AFLOAT)). ANY UNIT MAY SUBMIT ITEMPO DATA VIA DMRS, INCLUDING THOSE UNITS WHOSE PERSONNEL ACCOUNTING IS PERFORMED BY A PSD; HOWEVER, ITEMPO DATA DURING PHASE 1 MAY ONLY BE SUBMITTED VIA DMRS MESSAGE. NAVY'S ITEMPO SYSTEM CAN NOT RECEIVE DATA VIA SDS OR SDS AFLOAT, NOR VIA THE NAVY STANDARD INTEGRATED PERSONNEL SYSTEM (NSIPS). FEEDBACK REPORTING WILL INCLUDE REPORTS THAT INFORM A COMMAND OF ERRORS IN TRANSACTIONS SUBMITTED, A MONTHLY STATUS REPORT, AND WITHIN THESE TWO REPORTS, NOTIFICATION WHEN ANOTHER UIC HAS SUBMITTED AN ITEMPO TRANSACTION ON A MEMBER OF THE COMMAND. THESE REPORTS WILL BE AVAILABLE TO COMMANDS THROUGH AN ONLINE MAILBOX. ACCESS TO A COMMAND'S MAILBOX IS AVAILABLE VIA THE BUPERS ONLINE (BOL) WEB SITE AT WWW.BOL.NAVY.MIL OR, WHEN ONLINE ACCESS IS NOT AVAILABLE DUE TO LACK OF CONNECTIVITY (OTHER THAN DURING SHORT INTERRUPTIONS), VIA MESSAGE. MORE ADVANCED ELEMENTS OF PHASE 1 (PHASE 1A), SUCH AS USER-INPUTTED PARAMETERS TO RETRIEVE REPORTS ('CANNED' QUERIES) AND THE CAPABILITY FOR COMMANDS TO FORECAST ITEMPO DEPLOYMENT DAYS, WILL BE AVAILABLE VIA THE BOL WEB SITE IN MAR 01. B. PHASE 2 (SCHEDULED TO BE AVAILABLE IN JUL 01): PHASE 2 WILL CONTINUE THE USE OF PHASE 1 CAPABILITIES WHILE ADDING A WEB-BASED ABILITY TO ENTER ITEMPO DATA AND TO ENHANCE THE QUERY CAPABILITIES OF PHASE 1A. C. PHASE 3 (IMPLEMENTATION DATE NOT YET ESTABLISHED): PHASE 3 WILL ELIMINATE THE OBSOLETE ASPECTS OF THE ITEMPO DATA SYSTEM'S APPLICATIONS AND TECHNOLOGY WHILE RETAINING THE BEST ASPECTS OF PHASES 1 AND 2. PHASE 3 WILL ALSO ADD STATE-OF-THE-ART TECHNOLOGY TO THE ITEMPO DATA SYSTEM. D. RESPONSIBILITY FOR SUBMISSION OF ITEMPO DATA: (1) RESPONSIBILITY FOR SUBMISSION OF ITEMPO TRANSACTIONS TO THE NAVY-WIDE ITEMPO DATA SYSTEM SHALL RESIDE AT THE INDIVIDUAL UNIT LEVEL. UNITS SHALL REPORT TRANSACTIONS TO ACCOUNT FOR ITEMPO DEPLOYMENT EVENTS AND ITEMPO NON-DEPLOYMENT EVENTS (AS DEFINED ABOVE) OF THE MEMBERS OF THEIR UNIT (NON-ITEMPO EVENTS ARE NOT TO BE REPORTED). ITEMPO TRANSACTIONS SHALL BE REPORTED AS THEY OCCUR AND UNITS SHALL REPORT ON MEMBERS ATTACHED TO ALL UICS FOR WHICH THE COMMAND IS RESPONSIBLE, BUT FOR WHICH THERE IS NO SEPARATE CO, OIC, ETC. FOR EXAMPLE, ALTHOUGH RESPONSIBLE FOR THE PSD'S UNDER THEIR COMMAND, PSA'S NEED NOT REPORT ON THEIR PSD'S; A PSD IS EXPECTED TO SUBMIT ITEMPO TRANSACTIONS FOR THOSE PERSONNEL ATTACHED TO THE PSD AND ATTACHED TO ANY CUSTOMER SERVICE DESK'S (CSD'S) IT MAY HAVE. (2) AN EXCEPTION TO THE ABOVE REPORTING RESPONSIBILITY IS AVAILABLE IN THE CASE OF MEMBERS WHO MAY BE ASSIGNED IN A TAD STATUS TO ANOTHER UNIT WITHIN THE LOCAL AREA OF THE MEMBER'S PDS/HOMEPORT OR WHO MAY BE SENT UNDER TAD ORDERS TO ANOTHER UNIT OUTSIDE THE LOCAL AREA OF THE PDS/HOMEPORT, AND DUE TO CIRCUMSTANCES AT THE TAD UNIT, THE ITEMPO EVENT CATEGORY STATUS CHANGES (I.E., FROM DEPLOYMENT EVENT TO NON-DEPLOYMENT EVENT OR VICE VERSA). IN SUCH CASES, AND UNDER CIRCUMSTANCES WHERE THE TAD COMMAND CAUSES THE MEMBER'S PARTICIPATION IN AN ITEMPO EVENT, OR CAUSES THE ITEMPO EVENT CATEGORY TO CHANGE, THE TAD COMMAND MAY SUBMIT THE PERTINENT ITEMPO TRANSACTION(S). EXAMPLE 1: A SAILOR IS "ON LOAN" FROM SHIP 'A' TO SHIP 'B' WITHIN THE SAME HOMEPORT. WHILE ABOARD SHIP 'B' THE MEMBER GETS UNDERWAY. SHIP 'B' MAY EITHER, CONTACT SHIP 'A' WITH THE INFORMATION TO ENABLE SHIP 'A' TO SUBMIT THE REQUISITE ITEMPO TRANSACTION(S) ON THE SAILOR, OR, SHIP 'B' MAY CHOOSE TO (OR THROUGH PREVIOUS AGREEMENT WITH SHIP 'A') SUBMIT THE REQUISITE ITEMPO TRANSACTION(S) DIRECTLY TO THE NAVY ITEMPO DATA SYSTEM. EXAMPLE 2: A SAILOR IS SENT TAD FROM SHIP 'Y' TO SHIP 'Z' IN A DIFFERENT HOMEPORT OUTSIDE OF THE LOCAL AREA. SHIP 'Y' SUBMITS THE ITEMPO DEPLOYMENT EVENT TRANSACTIONS. SHIP 'Z' THEN SENDS THE SAILOR TO A SCHOOL IN THEIR HOMEPORT, STILL OUTSIDE OF THE HOMEPORT/PDS/LOCAL AREA OF SHIP 'Y'. SHIP 'Z' OR THE GAINING TRAINING COMMAND MAY EITHER CONTACT SHIP 'Y' WITH THE INFORMATION TO ENABLE SHIP 'Y' TO SUBMIT THE REQUISITE ITEMPO TRANSACTION(S) ON THE SAILOR, OR SHIP 'Z' (OR THE GAINING TRAINING COMMAND) MAY CHOOSE TO (OR THROUGH PREVIOUS AGREEMENT WITH SHIP 'Y') SUBMIT THE REQUISITE ITEMPO TRANSACTION(S) DIRECTLY TO THE NAVY ITEMPO DATA SYSTEM. IN CASES WHERE A UNIT, OTHER THAN THE MEMBER'S UNIT, SUBMITS AN ITEMPO TRANSACTION ON A MEMBER, THE MEMBER'S PERMANENT COMMAND SHALL RECEIVE A FEEDBACK REPORT INFORMING THEM OF THE ITEMPO TRANSACTION AND SUCH TRANSACTIONS WILL ALSO BE REFLECTED IN THE PERMANENT COMMAND'S MONTHLY STATUS REPORT. (3) PSD'S SHALL NOT BE USED TO REPORT ITEMPO DATA FOR CUSTOMER COMMANDS; PSD'S ARE HOWEVER, RESPONSIBLE FOR SUBMITTING ITEMPO DATA THAT PERTAINS TO THE PERSONNEL ASSIGNED TO THE PSD/CSD. (4) DUE TO THE COMPLEXITIES ASSOCIATED WITH THE VARIOUS MECHANISMS/AUTHORITIES WHICH ARE EMPLOYED TO ORDER A RESERVIST TO ACTIVE DUTY, AS WELL AS THE SPECIAL LAWS AND REQUIREMENTS THAT APPLY TO RESERVISTS, SPECIFIC POLICIES AND PROCEDURES REGARDING RESPONSIBILITY FOR SUBMISSION OF ITEMPO TRANSACTIONS THAT PERTAIN TO RESERVISTS ARE DELINEATED IN REF C. E. ITEMPO DATA TRANSACTIONS: SPECIFIC DETAILS AND EXPLICIT INSTRUCTIONS/TRANSACTION CODES (TAC'S) PERTAINING TO ITEMPO DATA TRANSACTIONS ARE FOUND IN REFS B AND C. COMMANDS ARE STRONGLY ENCOURAGED TO BECOME FAMILIAR WITH THESE REFERENCES PRIOR TO SUBMITTING ITEMPO DATA TO THE NAVY-WIDE ITEMPO DATA SYSTEM. GENERAL INFORMATION REGARDING ITEMPO TRANSACTIONS IS PROVIDED HERE SO COMMANDS MAY GAIN A GENERAL UNDERSTANDING OF THE PROCESSES AND PROCEDURES FOR ITEMPO DATA REPORTING. THERE ARE THREE GENERAL TYPES OF ITEMPO DMRS TRANSACTIONS THAT HAVE BEEN DEVELOPED FOR SUBMITTING ITEMPO DATA TO THE NAVY-WIDE ITEMPO DATA SYSTEM. THEY ARE: UNIT TRANSACTIONS, INDIVIDUAL TRANSACTIONS, AND ACCESS TRANSACTIONS. INCLUDED WITHIN THE FIRST TWO TRANSACTION TYPES IS EITHER A "D" INDICATOR FOR ITEMPO DEPLOYMENT EVENTS, OR AN "N" INDICATOR FOR ITEMPO NON-DEPLOYMENT EVENTS. (1) UNIT TRANSACTIONS: A UNIT TRANSACTION IS AVAILABLE FOR USE BY DEPLOYABLE UNITS SUCH AS SHIPS, AIRCRAFT SQUADRONS, NAVAL MOBILE CONSTRUCTION BATTALIONS (SEABEE BATTALIONS), ETC., AND ARE USED TO REPORT ITEMPO EVENTS THAT AFFECT A UNIT AS A WHOLE. ONCE SUBMITTED TO, AND ACCEPTED BY, THE ITEMPO DATA SYSTEM, INDIVIDUAL ITEMPO TRANSACTIONS ARE GENERATED BY THE SYSTEM FOR EVERY MEMBER ASSIGNED TO THE UIC BEING REPORTED UPON. THUS, FOR EXAMPLE, A SHIP THAT BEGINS A PERIOD OF ITEMPO DEPLOYMENT, NEED ONLY SUBMIT A SINGLE UNIT TRANSACTION TO START THE ITEMPO DEPLOYMENT EVENT FOR EVERY INDIVIDUAL ASSIGNED TO SHIP (IF THE SHIP'S MANNING IS ACCOUNTED FOR IN MORE THAN ONE UIC, A SEPARATE UNIT TRANSACTION MUST BE SUBMITTED FOR EACH UIC). SINCE THE NAVY ITEMPO DATA SYSTEM WILL TRANSLATE UNIT TRANSACTIONS INTO INDIVIDUAL TRANSACTIONS FOR ALL INDIVIDUALS ASSIGNED TO A UIC, UNIT TRANSACTIONS MUST BE ACCOMPANIED BY INDIVIDUAL TRANSACTIONS THAT REPORT THOSE MEMBERS THAT WERE "ABSENT ON SAILING", OR "ABSENT ON RETURN", AS THE CASE MAY BE. ADDITIONALLY, TO ENSURE THE ACCURACY OF ITEMPO DATA, IT IS CRITICAL THAT THE GAIN OR LOSS OF A MEMBER TO A UIC BE REPORTED THROUGH NORMAL PERSONNEL ACCOUNTING CHANNELS IN A TIMELY MANNER. IN THOSE CASES, WHERE A GAIN OR LOSS HAS NOT 'POSTED' TO THE NAVY PERSONNEL SYSTEMS PRIOR TO SUBMISSION OF AN ITEMPO UNIT TRANSACTION, SUCH MEMBERS MUST EITHER BE INCLUDED IN, OR EXCLUDED FROM, AN ITEMPO EVENT ON AN INDIVIDUAL BASIS (SEE SUBPARAGRAPH 8.E.(2) BELOW REGARDING INDIVIDUAL ITEMPO TRANSACTIONS). A UNIT TRANSACTION IS USED ON A UNIT BASIS TO 'START', OR 'STOP' ITEMPO EVENTS. THEY ARE ALSO USED TO 'CANCEL' A PREVIOUSLY SUBMITTED TRANSACTION (EITHER IN ITS ENTIRETY OR JUST THE END DATE) OR TO SUBMIT A PREVIOUSLY 'OMITTED' ITEMPO EVENT IN ITS ENTIRETY. IN ADDITION, A UNIT TRANSACTION MAY BE USED TO INFORM THE NAVY'S ITEMPO DATA SYSTEM OF THE NEED TO PROVIDE FEEDBACK REPORTS VIA NAVY MESSAGE IN ADDITION TO THE DEFAULT METHOD OF ACCESS VIA AN ONLINE MAILBOX. THIS TRANSACTION IS DESIGNED FOR THOSE OCCASIONS WHEN A UNIT DOES NOT HAVE ONLINE ACCESS TO THE BOL WEB SITE (EITHER TEMPORARILY OR FOR UNKNOWN DURATION); HOWEVER, UNITS SHOULD ONLY REQUEST THIS METHOD OF FEEDBACK REPORTING WHEN THEIR PERIOD OF CONNECTIVITY BLACKOUT WILL BE SUBSTANTIAL. (2) INDIVIDUAL TRANSACTIONS: AN INDIVIDUAL ITEMPO TRANSACTION IS SUBMITTED WHENEVER AN ITEMPO EVENT PERTAINS TO A SAILOR ON AN INDIVIDUAL BASIS OR WHEN AN EVENT APPLIES TO SEVERAL MEMBERS OF A UNIT, BUT NOT ENOUGH OF THE UNIT TO WARRANT SUBMISSION OF AN ITEMPO UNIT TRANSACTION. SHORED-BASED, NON-DEPLOYABLE UNITS SHALL ALWAYS USE INDIVIDUAL TRANSACTIONS FOR ITEMPO DATA REPORTING. AS WITH UNIT TRANSACTIONS, AN INDIVIDUAL TRANSACTION IS USED ON AN INDIVIDUAL BASIS TO 'START', OR 'STOP' ITEMPO EVENTS. IT IS ALSO USED, ON AN INDIVIDUAL BASIS, TO 'CANCEL' A PREVIOUSLY SUBMITTED TRANSACTION (EITHER IN ITS ENTIRETY OR JUST THE END DATE) OR TO SUBMIT A PREVIOUSLY 'OMITTED' ITEMPO EVENT IN ITS ENTIRETY. AS MENTIONED ABOVE, AN INDIVIDUAL ITEMPO TRANSACTION MUST BE USED TO REPORT 'EXCEPTIONS' TO UNIT TRANSACTIONS, WHEN EITHER ONE OR MORE MEMBERS OF THE UNIT DID NOT ACCOMPANY THE UNIT WHEN IT STARTED A DEPLOYMENT EVENT, OR WHEN MEMBERS ARE NOT WITH THE UNIT WHEN IT RETURNS TO HOMEPORT AND STOPS A DEPLOYMENT EVENT. (3) ACCESS TRANSACTIONS: ACCESS TRANSACTIONS ARE SUBMITTED TO AUTHORIZE OR OBTAIN ACCESS TO A UNIT'S ONLINE MAILBOX FOR A MILITARY MEMBER THAT IS NOT ASSIGNED TO THE UNIT'S UIC, OR FOR A CIVILIAN/MILITARY MEMBER WHO IS ASSIGNED TO THE UIC BUT IS NOT A MILITARY MEMBER OF THE NAVY. FOR UNITS WITH A NAVY CO (OIC, CMDR, ETC.), THE CO, AND THE CO ALONE, HAS BEEN AUTOMATICALLY GRANTED ONLINE ACCESS TO THE UIC MAILBOX BY THE ITEMPO DATA SYSTEM. ONCE ONLINE FOR THE FIRST TIME, THE CO CAN THEN, THOUGH MANIPULATING A SERIES OF ONLINE MENUS/DIALOG BOXES, ASSIGN OTHER NAVY MEMBERS OF HIS/HER COMMAND ACCESS TO THE ONLINE REPORTS. THE ACCESS TRANSACTIONS HAVE BEEN DEVELOPED TO ACCOUNT FOR THOSE CASES WHERE THE ITEMPO DATA SYSTEM HAS NOT AUTOMATICALLY PROVIDED THE CO WITH ACCESS TO UNIT REPORTS FOR ALL UICS FOR WHICH HE/SHE IS RESPONSIBLE, TO PROVIDE A MEANS WHEREBY A CO MAY GRANT ACCESS TO A NON-NAVY MEMBER OF HIS/HER COMMAND, OR FOR THOSE OCCASIONS WHERE THE CO IS EITHER A CIVILIAN OR A MEMBER OF ANOTHER BRANCH OF SERVICE AND THEREFORE CANNOT BE IDENTIFIED IN THE NAVY'S MILITARY PERSONNEL SYSTEMS. ACCESS TO REPORTS SHOULD ONLY BE GRANTED TO THOSE WITH A "NEED TO KNOW". ACCESS TRANSACTIONS MAY ALSO BE USED TO ENABLE CERTAIN HIGHER ECHELON COMMANDS TO OBTAIN REPORTS FOR SUBORDINATE COMMANDS. HOWEVER, AS PREVIOUSLY MENTIONED, IMPLEMENTATION, IN MAR 01, OF PHASE 1A OF THE NAVY'S ITEMPO DATA SYSTEM, WILL CONTAIN A PRE-DEFINED QUERY CAPABILITY THAT WILL ALLOW SUCH HIGHER ECHELON COMMANDS ACCESS TO REPORTS IN A "ROLLED-UP" FASHION FOR UNITS UNDER THEIR COGNIZANCE. 9. ITEMPO 'GATES' AND FLAG APPROVALS FOR CONTINUED DEPLOYMENTS: REF A ESTABLISHES SPECIFIC ITEMPO 'GATES' FOR THE PURPOSE OF MANAGING THE DEPLOYMENT OF INDIVIDUAL MILITARY MEMBERS. MANDATED BY LAW, AN INDIVIDUAL SAILOR MAY NOT BE DEPLOYED BEYOND 182 DAYS OF ITEMPO DEPLOYMENT OUT OF THE PRECEDING 365 DAYS UNLESS APPROVED TO DO SO BY THE FIRST FLAG OR GENERAL OFFICER (OF ANY BRANCH OF SERVICE) IN THE CHAIN OF COMMAND. SIMILARLY, BY LAW, A SAILOR MAY NOT CONTINUE TO BE DEPLOYED BEYOND 220 ITEMPO DEPLOYMENT DAYS (OUT OF THE PRECEDING 365 DAYS) UNLESS APPROVED BY THE DESIGNATED COMPONENT COMMANDER FOR THE MEMBER'S ARMED FORCE IN THE CHAIN OF COMMAND. IN OTHER WORDS, A MEMBER MUST BE APPROVED BY A MORE SENIOR NAVY FLAG OFFICER BEFORE HE/SHE MAY EXCEED THE 220-DAY ITEMPO GATE. IN ORDER TO ENABLE COMMANDS/APPROPRIATE FLAG OFFICERS TO EFFECTIVELY MANAGE THE DEPLOYMENT OF INDIVIDUAL SAILORS WRT THESE ITEMPO GATES, THE ITEMPO DATA SYSTEM HAS BEEN DESIGNED TO CONTINUOUSLY MAINTAIN AN ITEMPO DEPLOYMENT COUNTER FOR EVERY NAVY MEMBER. BASED ON UNIT LEVEL SUBMISSIONS OF ITEMPO DATA TRANSACTIONS, THE SYSTEM CALCULATES THE MEMBER'S CUMULATIVE ITEMPO DEPLOYMENT DAYS COUNTER (OUT OF BOTH THE PRECEDING 365 DAYS AND 730 DAYS). IT ALSO CALCULATES A MEMBER'S CUMULATIVE NON-DEPLOYMENT DAYS COUNTER (OUT OF THE PRECEDING 365 DAYS). DURING PHASE 1 OF ITEMPO DATA SYSTEM IMPLEMENTATION THE COUNTERS WILL BE DISPLAYED ON THE ITEMPO MONTHLY STATUS REPORTS. EFFECTIVE IN MAR 01 (IMPLEMENTATION OF PHASE 1A) COMMANDS WILL BE ABLE TO ASCERTAIN MEMBERS' ITEMPO COUNTERS ON A MORE FREQUENT BASIS USING THE PRE-DEFINED ONLINE QUERY CAPABILITY AS DESCRIBED IN PARAGRAPH 8 ABOVE, AND REF C. ADDITIONALLY, THE REMARKS BLOCK OF THE MONTHLY LEAVE AND EARNINGS STATEMENT (LES) WILL DISPLAY A MEMBER'S ITEMPO DEPLOYMENT DAYS COUNTER AS OF THE EFFECTIVE DATE SHOWN. CLEARLY, A KEY TO THE MANAGEMENT OF THE NAVY'S ITEMPO PROGRAM IS THE FLAG OFFICER APPROVAL PROCESS. THE FOLLOWING SETS FORTH NAVY POLICY AND DESIGNATES APPROPRIATE AUTHORITY WRT APPROVAL BY A FLAG OFFICER TO CONTINUE THE DEPLOYMENT OF INDIVIDUAL SAILORS BEYOND STATUTORILY ESTABLISHED ITEMPO DEPLOYMENT-DAY GATES: A. GENERAL: JUST AS THE RESPONSIBILITY FOR SUBMISSION OF ITEMPO TRANSACTIONS RESIDES AT THE UNIT LEVEL, SO TOO DOES THE RESPONSIBILITY TO SUBMIT, TO THE APPROPRIATE FLAG OFFICER, REQUESTS FOR APPROVAL FOR INDIVIDUAL MEMBERS TO EXCEED ITEMPO DEPLOYMENT GATES. IN ORDER TO ENSURE THE LAW IS NOT VIOLATED, IT IS CRITICAL THAT ANY REQUIRED FLAG OFFICER APPROVALS BE OBTAINED PRIOR TO A MEMBER EXCEEDING EITHER THE 182 OR 220-DAY ITEMPO GATE. FURTHER, AUTHORITY TO APPROVE MEMBERS TO EXCEED AN ITEMPO DEPLOYMENT GATE RESTS SOLELY WITH AN APPROPRIATE FLAG OFFICER, APPROVAL AUTHORITY MAY NOT BE DELEGATED OR DEVOLVE TO ANY OFFICER BELOW FLAG RANK, NOR MAY A CIVILIAN GOVERNMENT EMPLOYEE EXERCISE THIS AUTHORITY. ADDITIONALLY, TO MEET THE REQUIREMENTS OF THE LAW, APPROVALS MUST BE OBTAINED INDIVIDUALLY FOR ANY MEMBER WHOSE ITEMPO DEPLOYMENT DAYS ARE ANTICIPATED TO EXCEED AN ITEMPO GATE (I.E., A UNIT-WIDE APPROVAL THAT DOES NOT LIST AFFECTED MEMBERS INDIVIDUALLY, WOULD NOT CONFORM TO THE REQUIREMENTS OF THE LAW). HOWEVER, TO LESSEN THE ASSOCIATED ADMINISTRATIVE WORKLOAD AS MUCH AS POSSIBLE, UNITS ARE ENCOURAGED TO CONSOLIDATE INDIVIDUAL REQUESTS INTO A SINGLE SUBMISSION AND TO REQUEST APPROVAL FOR ALL ANTICIPATED DEPLOYMENT PERIODS AT ONE TIME. IF A CONSOLIDATED REQUEST IS UTILIZED, AFFECTED MEMBERS MUST BE LISTED INDIVIDUALLY WITH PERTINENT INDIVIDUAL DATA SUCH AS NAME, SSN, ACCRUED DEPLOYMENT DAYS, ETC. REQUESTS MAY BE SUBMITTED IN WHATEVER FORMAT IS ACCEPTABLE TO THE UNIT'S CHAIN OF COMMAND; HOWEVER, APPROVAL REQUESTS MUST CONTAIN THE REQUIRED INFORMATION, MUST EXPLICITLY STATE THE ANTICIPATED DEPLOYMENT PERIOD(S) WHICH WOULD CAUSE MEMBERS OF THE UNIT TO EXCEED ITEMPO DEPLOYMENT GATES, AND, IF APPROVED, MUST BE IN A FORMAT SUCH THAT THE UNIT IS ABLE TO RETAIN DOCUMENTATION OF THE APPROVAL FOR A PERIOD OF THREE YEARS. 10. RELEASED BY VADM NORBERT R. RYAN, JR., N1.// BT