Manage the Deployed Theater Accountability System (DTAS) October 2015

Manage the Deployed Theater Accountability System (DTAS) October 2015
HR Plans and Operations Course Senior Leader Training Division Adjutant General School SHOW SLIDE 1: EMPLOY THE DEPLOYED THEATER ACCOUNTABILITY SOFTWARE (DTAS) SECTION I. ADMINISTRATIVE DATA Academic Hours/Methods 1hrs/00 mins Small Group Instruction 1 hrs/00 mins Practical Exercise (Performance) 2 hrs/00 mins Total Hours SECTION II. INTRODUCTION: Today we are going to discuss Deployed Theater Accountability System Method of Instruction. Conference/discussion Instructor to Student Ration: 1:16 Time of Instruction: 5 mins Media: Small Group Instruction INSTRUCTIONAL GUIDANCE: Before presenting this lesson, instructors must thoroughly prepare by studying this lesson and identified reference material. Throughout this lesson, solicit from students the challenges they experienced in the current operational environment (OE) and what they did to resolve them. Encourage students to apply at least 1 of the 8 critical variables: political, military, economic, social, information, infrastructure, physical environment and time. MOTIVATOR: As the S-1, your knowledge of DTAS is critical as you Direct Personnel Accountability (PA) and Strength Reporting (SR) on the battlefield. PA and SR has a direct impact on the tactical employment and sustainment of the force. The commander requires timely and accurate strength data for short and long range planning and decision making. Manage the Deployed Theater Accountability System (DTAS) October 2015

Terminal Learning Objective
Action: Manage the Deployed Theater Accountability System (DTAS) Conditions: In a classroom environment, with internet connectivity and the DTAS training application loaded, DTAS Functional Guidance (current version), AHRS DTAS Dashboard User’s Guide (current version), DTAS Mobile Application User Manual (current version), and Applicable HR Field Manuals and References. Procedures and awareness of Operational Environment (OE), variables and actors. Standard: Students will meet the standard of 70% accuracy when they: 1. Identify the objectives of DTAS 2. Identify the three sub-systems of DTAS 3. Identify S-1 DTAS responsibilities and planning considerations 4. Employ the DTAS Mobile system 5. Manage the DTAS APOD module 6. Manage the DTAS Dashboard function 7. Manage the DTAS Major Command Level module SHOW SLIDE 2: TERMINAL LEARNING OBJECTIVE NOTE: Read and discuss the TLO with the students. NOTE: Inform students of the TLO requirements. SAFETY REQUIREMENTS. In a training environment, leaders must perform a risk assessment in accordance with FM 5-19, Composite Risk Management. Leaders will complete a DA Form 7566 COMPOSITE RISK MANAGEMENT WORKSHEET during the planning and completion of each task and sub-task by assessing mission, enemy, terrain and weather, troops and support available-time available and civil considerations, (METT-TC). Note: During MOPP training, leaders must ensure personnel are monitored for potential heat injury. Local policies and procedures must be followed during times of increased heat category in order to avoid heat related injury. Consider the MOPP work/rest cycles and water replacement guidelines IAW FM , NBC Protection, FM , CBRN Decontamination. No food or drink is allowed near or around electrical equipment (CPU, file servers, printers, projectors, etc.) due to possible electrical shock or damage to equipment. Exercise care in personal movement in and through such areas. Avoid all electrical cords and associated wiring. In event of electrical storm, you will be instructed to power down equipment. Everyone is responsible for safety. RISK ASSESSMENT LEVEL. Low. ENVIRONMENTAL STATEMENT. Environmental protection is not just the law but the right thing to do. It is a continual process and starts with deliberate planning. Always be alert to ways to protect our environment during training and missions. In doing so, you will contribute to the sustainment of our training resources while protecting people and the environment from harmful effects. Refer to FM Environmental Considerations and GTA ENVIRONMENTAL-RELATED RISK ASSESSMENT. EVALUATION: You will be evaluated on your ability to successfully employ DTAS. INSTRUCTIONAL LEAD-IN. The Deployed Theater Accountability System (DTAS) application provides the U.S. Army with a reliable, timely, and efficient mechanism for: Tracking Deployed Soldiers Providing Visibility of Location and Duty Status of Deployed Soldiers Reporting the Visibility of Location and Duty Status of Deployed Soldiers at both the Army Enterprise level (top of the system) and the unit level (bottom of the system).

References Personnel Accountability Branch;
DTAS Access Request Form for initial authorization to the system along with applicable HR Field Manuals and References; Theater DTAS Manager phone number: DSN: SHOW SLIDE 3: REFERENCES NOTE: Inform the students of the references that will be used for this lesson. a. DTAS Mobile Application User Manual (current version) b. Then select DTAS Access Request Form for initial authorization to the system along with applicable HR Field Manuals and References. c. Theater DTAS Manager phone number: DSN: /6068

Introduction to DTAS The Army developed DTAS to provide accurate personnel accountability in a theater of operation. DTAS provides HR professionals and commanders with a tool to accurately account for military and civilian personnel in a deployed Theater by NAME, UNIT, LOCATION, and DATE DTAS is comprised of three (3) distinct levels or sub-systems: Mobile System Level (User Level) Major Command Level Enterprise Level DTAS is the “vehicle” to capture what the Commanders and 1SGs know DTAS resolves the by-name accountability deficiency and is the cornerstone of accurate accountability of the deployed force SHOW SLIDE 4: INTRODUCTION TO DTAS Learning Step/Activity 1. a. Prior to the fielding of DTAS, S-1s performed PA and SR functions, for deployed Soldiers, utilizing various management tools. Each S-1 created their own way of tracking deployed personnel utilizing Excel spreadsheets, word processing, and Access programs. Because of the variance of experiences and systems, human error factored significantly in to our inability to properly account for personnel during OEF/OIF. DTAS is the program created to enable the S-1s to utilize one standardized system with established procedures, for accounting for personnel. b. DTAS is a software application designed to account for military and civilian personnel in a deployed Theater by NAME, UNIT, LOCATION and DATE. Presently the Army and Marine Corps utilize DTAS; however, if a unit has Air force or Navy personnel assigned or attached, these personnel will be added to DTAS. c. DTAS is composed of three distinct levels or sub-systems: (1) Enterprise (2) Major Command (MACOM) Level (formerly “Theater Level”) (3) Mobile

DTAS Objectives The primary objectives of DTAS are to:
Provide a standard Army system for deployed personnel accountability Provide accurate and timely deployed personnel accounting data to the Army Staff, Department of Defense and Commanders Enable deployed commanders, at all echelons, to account for personnel by name, unit, location and date Improve accountability near-term with focus on OIF/OEF/HOA (multi-theater capable) Provide a standard accountability tool and a standard procedure to capture 1SG/CDR knowledge (effort is to simplify the process) SHOW SLIDE 5: DTAS OBJECTIVES Learning Step/Activity 2. d. The primary objectives of DTAS, for the Army, are to provide PA of military personnel and civilians and report other strength-related information such as duty status, unit of assignment, and location as of a particular date and time. This system provides readiness managers, at all levels, the data necessary to analyze personnel strength as a component of personnel combat power. e. The primary objectives of DTAS are to: (1) Provide a corporate database for DA/DoD inquiries (2) Provide accurate and timely deployed personnel accounting data to the Army Staff, Department of Defense, and warfighting commanders (3) Enable deployed commanders, at all echelons, to account for personnel by name, unit, location, and date (4) Improve accountability with a focus on OIF/OEF/HOA (multi-Theater capable) (5) Provide a standard accountability tool and a standard procedure to capture 1SG/CDR knowledge (intent is to simplify the process)

DTAS Functional Tenets
The functional tenets of DTAS include: Providing daily PA reports to units that are close to real-time Synchronizing information from the bottom to the top Tracking personnel deployment history Providing disconnected operations capabilities Producing manifests that provide in-transit Theater visibility Capabilities exist for multi-service SHOW SLIDE 6: FUNCTIONAL TENENTS Learning Step/Activity 3. f. The functional tenets of DTAS include: (1) Providing daily PA reports to units that are close to real-time (2) Synchronizing information from the bottom to the top (3) Tracking personnel deployment history (4) Providing disconnected operations capabilities (5) The production of manifests that provide in-transit Theater visibility NOTE: Capabilities exist for multi-service usage NOTE: Ask the students if anyone has ever utilized DTAS. Discuss student answers to determine their prior knowledge and experience with DTAS. Encourage students to share real-world experiences that will help clarify DTAS capabilities and use. Ensure students fully understand the objectives of DTAS. NOTE: Conduct a check on learning and summarize the learning activity. Q: What is the mission of DTAS? A: The mission of the Army's DTAS system is to provide personnel accountability of military personnel and civilians; report other strength-related information such as duty status, unit of assignment, and location.

DTAS Sub-System Levels (on SIPRNet)
Enterprise (Army G-1/HRC) - serves as the “Strategic” or top level database of deployed service member data. Theater (Major Command) - serves as the “Operational” level database. Transfers historical records daily to the Enterprise server Mobile (Unit) - serves as the “Tactical” level database of deployed service member data for that particular unit Provides the ability for commanders to track daily status of all personnel SHOW SLIDE 7: DTAS SUB-SYSTEM LEVELS h. There are three distinct levels of DTAS. This functional guidance is divided into these three levels: (1) The Enterprise Database houses the central database, which contains Soldier data obtained from Electronic Military Personnel Office (eMILPO) as well as information on current Soldier location and duty status as entered into mobile systems and passed to the enterprise database system. The enterprise database also interfaces through a secure High Assurance Guard (HAG) or trusted gateway with eMILPO and receives data from the Defense Manpower Data Center (DMDC) and the Marine Corps Operations Data Store Enterprise (ODSE). In addition, the enterprise database includes an integration broker that manages the messaging among DTAS component systems. The enterprise database also houses a data warehouse that contains historical data for each deployed Soldier, such as a transaction history of those attributes for which DTAS is the authoritative source. Adhoc reporting is configured to run against the DTAS Enterprise data warehouse. (2) The Theater Database consists of the theater manager application and a core database. The theater manager application allows theater-level users to manage mobile systems and UIC structure, and provides reporting capabilities, such as the Joint Personnel Status (JPERSTAT) report and support for adhoc queries. The theater database is a subset of the enterprise database. The theater database communicates with both the enterprise and mobile systems. Message queuing is used for communications between the theater and enterprise databases. The theater database uses web services to support data communications with occasionally connected DTAS mobile systems. (3) The Mobile System provides the company level with a micro-database, reporting capabilities, and personnel accounting tools. The mobile database contains information on the Soldier’s current location and duty status as well as a mini-record, and allows the user to update location and duty status, while providing several predefined, roster-based reports. The mobile system is deployed on laptop or desktop computer and communicates using web services because these systems may only occasionally be connected to the network. While a mobile system is disconnected, any DTAS work performed is stored in a message in its micro-database. When the mobile system is connected, the stored messages are sent to the theater database via web services in the order they were produced.

APOD MANIFEST SITE IN TPS MAJOR COMMAND LEVEL SYSTEM
Architecture Electronic Military Personnel Office Operational Data Store Enterprise Defense Manpower Data Center Synchronized Pre Deployment Operational Tracker G1/HRC PENTAGON MANIFEST SITE TPS PPP/CRC EMILPO ODSE DMDC Domain Solution SIPRNET CONUS ENTERPRISE SYSTEM NIPRNET AFRICOM G1 IRAQ G1 ARCENT G1 AFGHANISTAN G1 APOD MANIFEST SITE IN TPS SIPRNET KUWAIT ONE WAY TRANSFER VIA DISK MAJOR COMMAND LEVEL SYSTEM SHOW SLIDE 8: ARCHITECTURE b. DTAS is composed of three distinct sub-system levels: Mobile which is located at every Bn size unit; Major Command Level which is located at AFRICOM, IRAQ, ARCENT, and AFGHANISTAN; and Enterprise which is the historical database located at Fort Belvoir, Virginia. c. DTAS uses the following authoritative systems to validate information and populate data fields: (1) Army - eMILPO (Electronic Military Personnel Office) (2) Marine - ODSE (Operation DataStore Enterprise) (3) Air Force - DMDC (Defense Manpower Data Center) (4) Navy - DMDC (Defense Manpower Data Center) (5) Civilians - DMDC (Defense Manpower Data Center) d. Currently there are over 450 DTAS Mobile Systems active across the CENTCOM AOR with over 3500 Deployed Unit Identification Codes (DUICs) managed. MNFI/MNCI IRAQ CJTF-76 AFGHANISTAN MARINE MASTER MOBILE MARCENT CORPS ARCENT KUWAIT CJOA-HOA DJIBOUTI DIV BDE BDE BDE BDE BDE BN BN BN BN BN MOBILE SYSTEM

The Users Point of View. . . Looks Like This:
But Technically, It’s This: BDE CORPS DIV MACOM Level BN DIV BN BDE MACOM Level BN - CORPS - - DIV - - BDE - - BN - SHOW SLIDE 9: THE USER POINTS OF VIEW e. All Mobile Systems connect directly to the MACOM Level System and do not follow the traditional Battalion, Brigade, Division, Chain of Command. BN BDE BN DIV BN BN DIV BN CORPS BDE

Battlefield Flow SHOW SLIDE 10: BATTLEFIELD FLOW
Commanders account for Soldiers by reporting strength accountability and duty status changes though DTAS. This software is not always at the lowest echelon due to connectivity limitations. Units below the connectivity level send the accountability and duty status changes to the level of connectivity. These entries flow directly to the theater database and are then visible to the all levels of command.

Enterprise/Major Command Level
Capabilities Mobile – Unit Level Enterprise/Major Command Level Simple front end user tool – BN S-1 Disconnected operations Synchronized Generation of reports Relevant data set Near real-time deployed data Historical deployed data Asset-level of detail Supports all services/types of personnel Powerful querying tool & robust datastore Responsive to Task Orgs. Provides accountability Eliminates double counting Acts as a locator service Validates pay SHOW SLIDE 11: CAPABILITIES f. This slide reiterates what we have discussed. Please note the sub-bullets on the bottom-left portion of your screen. DTAS also acts as a locator and may be utilized to validate pay some transactions.

Requirements/Limitations
Requires commanders’ support to ensure compliance Requires user discipline and network availability Requires high bandwidth/low latency Reports only near real-time data Requires access to SIPRNET Data transfer to NIPRNET systems COGNOS search application is not intuitive SHOW SLIDE 12: REQUUIREMENTS/LIMITATIONS g. As with any other system, there are limitations to the use of DTAS. Commander's must ensure the strict adherence to compliance; further, DTAS requires user discipline. In other words, user's must standardize their entries and comply with the business rules consistently. Refer to Section Business Rules PERSTAT Report in the DTAS Mobile Application User Manual. h. Connectivity is required to transmit data to the MACOM level and SIPRNET access is required. The system updates every 20 minutes. NOTE: COGNOS is a separate software package designed to enhance existing systems by enabling users to extract data, analyze it, and assemble reports. COGNOS is powerful; but not intuitive. Users typically need training and/or experience with the program to maximize its potential. NOTE: Conduct a check on learning and summarize the learning activity. Q: What are the three sub-system levels? A: Enterprise, MACOM, and Mobile 12

Check On Learning Q: What is the mission of DTAS?
A: The mission of the Army’s DTAS system is to provide personnel accountability of military and civilian personnel and to report other strength-related information such as duty status, unit of assignment and location. Q: DTAS is comprised of how many levels or sub-systems? What are they? A: Three; Enterprise, Theater; and Mobile. Q: What is the Enterprise Database? A: The Enterprise Database houses the central database, which contains Soldier data obtained from Electronic Military Personnel Office (eMILPO) as well as information on current Soldier location and duty status as entered into mobile systems and passed to the enterprise database system. SHOW SLIDE 13: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q. What is the mission of DTAS? A. The mission of the Army’s DTAS system is to provide personnel accountability of military and civilian personnel and to report other strength-related information such as duty status, unit of assignment and location. Q. DTAS is comprised of how many levels or sub-systems? What are they? A. Three; enterprise, theater; and mobile. Q: What is the Enterprise Database? A: The Enterprise Database houses the central database, which contains Soldier data obtained from Electronic Military Personnel Office (eMILPO) as well as information on current Soldier location and duty status as entered into mobile systems and passed to the enterprise database system SUMMARY: We have just completed Learning Activity 1, Identify the Objectives and Recognize the Sub-systems of DTAS. Next we will Analyze S-1 Responsibilities and Planning Considerations.

S-1 Planning Considerations
Coordinate with S6 for SIPRNET connectivity and identify classified computers w/rights capabilities Prepare personnel file to upload (eMILPO, TPS, EXCEL) Determine when DTAS operators deploy (ADVON) Train S-1 personnel (BDE and BN) Brief chalk commanders Include DTAS in OPORD Obtain DTAS software and the Theater IP address from the MACOM Manager Provide task organization (UIC hierarchy) to MACOM Manager SHOW SLIDE 14: S-1 PLANNING CONSIDERATIONS i. S-1s should consider these planning factors when preparing their unit's for deployment. (1) Coordinate with the S6 prior to deployment to ensure the computers used for DTAS have the appropriate capabilities, permissions, etc. to support SIPRNET connectivity. Consider how many systems are needed and their location (split based operations). (2) As near as possible to each units’ departure, prepare a personnel file using eMILPO, TPS, or EXCEL for the unit to use when they upload into DTAS (in Theater). Make multiple copies and retain one copy at the rear detachment until the deployed unit has verified their DTAS account. (3) Determine when DTAS operators deploy (ADVON); consider that accountability (PERSTAT) reporting requirements begin immediately upon arrival in Theater. Train BDE and BN S-1 personnel to operate DTAS and the Theater and Unit requirements for timeliness of transactions, report deadlines, etc. Ensure the unit SOPs are current and synched. Brief chalk commanders on their requirements for manifesting and reporting any changes to the deployment of personnel (to the S1) as soon as possible upon arrival in Theater. (6) Build DTAS training and execution requirements into the OPORD and rehearse as possible prior to deployment. (7) Coordinate with the MACOM Manager to download the current version of the DTAS software and obtain the Theater IP address. Without the correct IP address, units will not be able to connect and transmit data to the MACOM level (and up to the Enterprise level). (8) Verify the deploying unit(s) task organization; specifically the UIC hierarchy and provide it to the MACOM Manager upon arrival in Theater. This is important as it allows the units’ personnel to be uploaded quickly and reduces the number of changes required later. NOTE: Ask the students what additional factors might they have to consider in planning. Also, ask how they might ensure that their units receive DTAS training prior to arrival at the mobilization site. 14

S-1 Responsibilities (1 of 3)
Reconcile DTAS with JPERSTAT Generate a daily “Morning Report” (JPERSTAT) Ensure that updates are sent to the MACOM Level DTAS LAPTOP MACOM Level DTAS APOD/SPOD Validated Arrival to Theater SHOW SLIDE 15: S-1 RESPONSIBILITIES (1 of 3) j. S-1’s are responsible for generating and reconciling the daily JPERSTAT and ensuring that updates are captured in the MACOM Level sub-system. To accomplish this, the units must diligently scrub the data; looking for any discrepancies between the previous day’s report, the current DTAS data, and any additional information the S1 may have (e.g. changes in task organization, unit/personnel moves, etc.) This allows the Commanders and HR managers at all levels to have the most accurate accountability data; which in turn, impacts operational decisions. 15

Ensure that DTAS is continually updated to coincide with the current picture on the ground (by NAME, UNIT, LOCATION and DATE Confirm the S-1/APOD swipes/entries are validating arrivals to Theater LAPTOP MACOM Level DTAS APOD/SPOD Validated Arrival to Theater SHOW SLIDE 16: S-1 RESPONSIBILITIES (2 of 3) k. S-1’s must ensure that DTAS is continually updated and at all times best reflects the current status of the units represented. One action to consider is ensuring that the S-1/APOD swipes are validated. Students should know that personnel enter into the Theater through an APOD (Ali Al Salem) where they are entered into DTAS by Personnel Accountability Team (PAT) Personnel. When there is movement, the S1 must perform the DTAS transaction and move personnel where necessary (i.e., updating physical location). When individuals depart Theater, they are removed from the system at the APOD by the PAT. 16

Add, when required, a record for joint service, DoD civilian, contractor, coalition forces, foreign nationals Change Duty Status (PDY, Hosp, R&R Leave, Casualty Categories) Attaches units and personnel Updates other personnel and unit data elements as necessary APOD/SPOD Validated Arrival to Theater SHOW SLIDE 17: S-1 RESPONSIBILITIES (3 of 3) l. S-1’s will continually oversee input to unit and personnel entries within DTAS. This is accomplished in an effort to provide continual factual reporting to the local Commander and to the top of the system. S-1’s can begin to properly comply with the standards by first knowing who is and is not accounted for in DTAS. LAPTOP MACOM Level DTAS 17

Accounted Personnel US Military (Active, Guard, and Reserve)
Army, Marines, Air Force, and Navy units/personnel attached to Army units Assigned, Attached, and Operational Control (OPCON) Under Tactical Control (TACON) or Administrative Control (ADCON) Civilians DoD Civilians US Contractors Other Civilians - Civilians not employed by DoD but deployed in support of the Service Component or JTF (i.e. USO, Red Cross, Consultants) Foreign Nationals SHOW SLIDE 18: ACCOUNTED PERSONNEL NOTE: Briefly discuss the personnel statuses listed on the slide. Instructor Note: Operational Control. OPCON is inherent in Combatant Command (COCOM). It is the authority to perform those functions of command that involve organizing and employing commands and forces, assigning tasks, designating objectives, and giving authoritative direction necessary to accomplish the mission. OPCON may be exercised at any echelon at or below the level of the combatant command. It can be delegated or transferred. Army commanders use it routinely to task organize forces. The secretary of defense must approve transferring OPCON of units between combatant commanders Tactical Control. TACON is authority normally limited to the detailed and specified local direction of movement and maneuver of forces to accomplish a task. It allows commanders below combatant command level to apply force and direct the tactical use of Combat Service Support (CSS) assets but does not provide authority to change organizational structure or direct administrative or logistic support. The commander of the parent unit continues to exercise those responsibilities unless otherwise specified in the establishing directive Combatant commanders use TACON to delegate limited authority to direct the tactical use of combat forces. TACON is often the command relationship established between forces of different nations in a multinational force. It may be appropriate when tactical-level Army units are placed under another service headquarters. Army commanders make one Army force TACON to another when they want to withhold authority to change the subordinate force organizational structure and leave responsibility for administrative support or CSS with the parent unit of the subordinate force. Administrative Control. Unless the secretary of defense specifies otherwise, administrative control (ADCON) of Army forces remains within the Army chain of command, from lowest levels to the ASCC to the secretary of the Army. Administrative control is the direction or exercise of authority over subordinate or other organizations with respect to administration and support. It includes organization of service forces, control of resources and equipment, personnel management, unit logistics, individual and unit training, readiness, mobilization, demobilization, discipline, and other matters not included in operational missions of the subordinate or other organizations. ADCON is synonymous with Title 10 USC administration and support responsibilities. 18

Non-Accounted Personnel
Personnel who are under Tactical Control (TACON) or Administrative Control (ADCON) to a unit Exception: Units with no Operational Control (OPCON) reporting chain in Theater default to Administrative Control (ADCON) reporting for DTAS and JPERSTAT Third country nationals or host nation civilians Special Operations Forces (SOF) and personnel supporting SOF SHOW SLIDE 19: NON-ACCOUNTED PERSONNEL NOTE: Briefly discuss those personnel who are not accounted for in DTAS. Also speak to TACON and ADCON and indicate that these categories will be further discussed in unit manning. If unit manning has previously been taught, ensure that students understand the difference. Refer to Standard Operating Procedures for Deployed Theater Accountability System (DTAS, Chapter 2, 2-1(d). NOTE: Conduct a check on learning and summarize the learning activity. Q: What is the network requirement for DTAS? A: SIPERNET Q: What report must be reconciled with DTAS on a daily basis? A: JPERSTAT

Check On Learning Q: Name four of the planning factors (DTAS) that the S-1 should consider when preparing for deployment. A: (1) Coordinate with S6 for SIPRNET connectivity (2) Identify classified computer w/rights capabilities and downloaded software from HRC (3) Provide task organization (UIC hierarchy) to theater manager (4) Obtain theater IP address from theater manager (5) Prepare personnel file to upload (eMILPO, TPS, EXCEL) (6) Determine when DTAS operator deploys (ADVON) (7) Train S-1 personnel (BDE and BN) (8) Brief chalk commanders (9) Include DTAS in OPORD SHOW SLIDE 20: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q: What are the planning factors (DTAS) that the S-1 should consider when preparing for deployment. A: (1) Coordinate with S6 for SIPRNET connectivity (2) Identify classified computer w/rights capabilities and downloaded software from HRC (3) Provide task organization (UIC hierarchy) to theater manager (4) Obtain theater IP address from theater manager (5) Prepare personnel file to upload (eMILPO, TPS, EXCEL) (6) Determine when DTAS operator deploys (ADVON) (7) Train S-1 personnel (BDE and BN) (8) Brief chalk commanders (9) Include DTAS in OPORD SUMMARY: We have just completed Learning Activity 2, Analyze S-1 Responsibilities and Planning Considerations. Next, we will discuss Input Unit Personnel Files to the DTAS Database.

MAJOR COMMAND (MACOM) SHOW SLIDE 21: MAJOR COMMAND (MACOM)
NOTE: TRANSITION SLIDE NOTE: Have students log-in to the MACOM Manager using the following URL with their assigned username and password:

Major Command Level A MACOM is defined as a level two unit (a unit one level below the top unit in the Global Unit Hierarchy) and all of its subordinate units. Level two units cannot be relocated (either via an assignment or an attachment) within the hierarchy. The MACOM System consists of the MACOM Management Application, the APOD module, and a MACOM Datastore that reflects that particular major command. This system is a subset of the Enterprise System and communicates with both the Enterprise System and all Mobile Systems. SHOW SLIDE 22: MAJOR COMMAND LEVEL a. A Major Command is defined as a level two unit (a unit one level below the top unit in the Global Unit Hierarchy) and all of its subordinate units. Level two units cannot be relocated (either via an assignment or an attachment) within the hierarchy. b. The Major Command System consists of the Major Command Management Application, APOD module and a Major Command Datastore that reflects their particular Theater and major command. This system is a subset of the Enterprise System and communicates via message queuing with both the Enterprise System and all Mobile Systems. NOTE: There are several Theater-level responsibilities that the Major Command Manager must manage to ensure successful DTAS operations and accurate data. An overview of these procedures is outlined in this section. Additional guidance and standard operating procedures are provided to the unit upon arrival in Theater.

Access to Major Command Level
Major Command Managers Help Desk Clerks (limited) Select units in Theater (limited, as needed) SHOW SLIDE 23: ACCESS TO THE MAJOR COMMAND LEVEL c. The Major Command Level is managed by a Major Command Manager who is responsible for Theater-wide oversight of DTAS. Full access to this level is only given to Major Command Managers. Limited access is given to help desk clerks and select units in Theater. NOTE: The Major Command Manager was previously known as the Theater Manager. The responsibilities are still the same.

MACOM Manager’s Responsibilities (1 of 2)
Account for USA, USMC, USN, and USAF attached to Army units, DOD Civilians and contractor personnel Update command database at all levels Collect, validate processes, and store critical information on all personnel in Theater Provide support, training, and resolve program issues to users through a website and helpdesk that initiates the DTAS program Coordinate, monitor, and train units during the RSO&I process SHOW SLIDE 24: MAJOR COMMAND MANAGER’S RESPONSIBILITIES (1of2) d. The MACOM Manager has various duties and responsibilities within Theater. These responsibilities include: They must account for USA, USMC, USN, and USAF attached to Army units, DOD Civilians, and contractor personnel in Theater on a daily basis by name, unit, and location. Update the command database at all levels in order to analyze personnel strength as a component of combat power. Collect, validate current processes, and store critical information about military and civilian personnel in Theater. (4) Provide support, training, and resolve program issues to users through a website and helpdesk that initiates the DTAS program. Coordinate, monitor, and train units during the Reception, Staging, Onward Movement, and Integration (RSO&I) process in support of the personnel accountability mission. **MAJOR COMMAND MANAGER WAS FORMERLY CALLED THEATER MANAGER**

Major Command Manager’s Responsibilities (2 of 2)
Solicit organizational DUIC Hierarchy documentation from new organizations as they arrive in Theater Adjust Theater Hierarchy to include Mobile System User’s Organizational Hierarchy Assign Unit DUIC as a Mobile System Provide Theater System IP address and Mobile System Activation Key to Mobile System Users Assign DOD Service Component, Command Code, and Unit Level to all DUICs Monitor DTAS Mobile System Status Code Coordinate with HRC Global Theater manager to move DUIC from losing MACOM to gaining MACOM Review the Mobile Activation Log daily to ensure all Mobile Systems are still activated Update POC Name, phone number, SIPR/NIPR , Location, and UIC SHOW SLIDE 25: MAJOR COMMAND MANAGER’S RESPONSIBILITIES e. The MACOM Manager has several responsibilities in Theater within the DTAS program. (1) Solicit organizational DUIC Hierarchy documentation from new organizations as they arrive in Theater Adjust Theater Hierarchy to include Mobile System User’s Organizational Hierarchy, or changes, as provided (3) Assign Unit DUIC as a Mobile System upon request (4) Provide Theater System IP address and Mobile System Activation Key to Mobile System User upon request (5) Assign DOD Service Component, Command Code, and Unit Level to all DUICs (6) Monitor DTAS Mobile System Status Code using the Major Command Management Application during Initialization Process. System is fully activated when the Mobile System Status Code changes to ‘I’ (7) Coordinate with HRC Global Theater manager to move DUIC from losing MACOM to gaining MACOM (8) Review the Mobile Activation Log daily to ensure all Mobile Systems are still activated (9) Update POC Name, phone number, SIPR/NIPR , Location, and UIC

Major Command Manager Application
The Major Command Manager Application is a valuable DTAS management tool for the MACOM Manager. This tool consists of 9 functions: Functions Administrative Hierarchy Operational Hierarchy Static Table Maintenance Strength Management Document Manager APOD Manager Mobile Config System Administration Workflow ***This lesson will only review Administrative Hierarchy, Operational Hierarchy, Static Table Maintenance, APOD Manager, and Mobile Config**** SHOW SLIDE 26: MAJOR COMMAND MANAGER APPLICATION The Major Command Manager Application consist of nine main functions that allow the MACOM Manager to manage DTAS. The MACOM Manager uses these functions to manage the following: (1) Administrative Hierarchy – the creation and editing of UICs within hierarchies Operational Hierarchy - attaching and release from attachment within hierarchies Static Table Maintenance – tables whose values are dynamic Document Manager – wartime requirements for each DUIC in Theater APOD Manager – Arial Port of Debarkation (APOD) UICs and APOD user accounts Mobile Config – sending sync service configuration changes to the targeted mobile system Mobile Activation Log – a snapshot of system activation activity for the previous week (8) System Administration – assign permissions to MACOM Managers and users (9) Workflow-tracking personnel returning from a period of attachment. NOTE: This lesson will only review Administrative Hierarchy, Operational Hierarchy, Static Table Maintenance, APOD Manager, and Mobile Config because these are the most commonly used functions.

Example of Major Command Level Functions
SHOW SLIDE 27: EXAMPLE OF MAJOR COMMAND LEVEL FUNCTIONS

Hierarchy Management The Unit Hierarchy provides a visual indication of which units are assigned to the Mobile System, attached to the Mobile System, and which are assigned to the Mobile but attached elsewhere: When a unit’s command structure changes for any reason, (unit operational moves and reassignment, unit redeployment, etc.), the hierarchy must be adjusted in DTAS This process is usually performed only when a unit arrives or is departing from Theater. However, it can also be used to create a task force organization in DTAS for a particular operation There are two types of hierarchies: Administrative and Operational SHOW SLIDE 28: HIERARCHY MANAGEMENT g. The Unit Hierarchy provides a visual indication of which units are assigned to the Mobile System, attached to the Mobile System, and which are assigned to the Mobile but attached elsewhere. Hierarchy management occurs when a unit’s command structure changes for any reason, (unit operational moves and reassignment, unit redeployment, etc.), the hierarchy must be adjusted in DTAS This process is usually performed only when a unit arrives, or is departing from a Theater. However, it can also be used to create a task force organization in DTAS for a particular operation There are two types of hierarchies: Administrative and Operational

Hierarchy Management Responsibilities
Hierarchy Management consists of the following responsibilities: Ensure that each unit’s DUIC is placed in the MACOM hierarchy Execute timely updates to the DUIC hierarchy. This includes additions, deletions, and edits; to include attachments and release from attachments Create DUIC(s) to accommodate Task Force operations, other branches of service, and civilian organizations Ensure that each requested unit attachment is completed SHOW SLIDE 29: HIERARCHY MANAGEMENT RESPONSIBILITIES h. Hierarchy Management consists of the following responsibilities: The Major Command Manager will ensure that each unit’s DUIC is placed in the Theater hierarchy. The Major Command Manager must solicit hierarchy documentation from new organizations as they arrive in the Major Command Manger’s area of operation Execute timely updates to the DUIC hierarchy. This includes additions, deletions, and edits; and attachments and release from attachments. The Major Command Manager can not delete DUICs from the Major Command hierarchy until all personnel have been redeployed from the Mobile System Create DUIC(s) to accommodate Task Force operations, other branches of service, and civilian organizations by updating the DOD Service Component and Command Code, and unit level (4) Ensure that each requested unit attachment is completed NOTE: Careful consideration should be given to hierarchy changes for DUICs or groups of DUICs that contain 5000 or more personnel. Every hierarchy change produces four messages per person. Mass DUIC hierarchy changes can overload and crash a Major Command Level server. Careful consideration should be given to hierarchy changes for DUICs or groups of DUICs that contain 5000 or more personnel. Mass DUIC hierarchy changes can overload and crash a MACOM Level server.

Hierarchy SHOW SLIDE 30: HIERARCHY
i. The MACOM Manager uses the Major Command Manager as the managing point for all actions within DTAS. One of their major responsibilities includes establishing the hierarchy, so it is important to understand how to access this portion of the system. NOTE: Have the students click the “Administrative Hierarchy” tab on the left side of the screen.

Administrative Hierarchy Creating a UIC
The new UIC will be here SHOW SLIDE 31: ADMINISTRATIVE HIERARCHY The Administrative Hierarchy is the MACOM structure that makes DTAS work and drives the ability to see units and update records on Mobile Systems. This module allows the MACOM Manager to manage the MACOM UIC hierarchy. From this screen you can create, add, and edit a UIC. (1) Click the UIC assigned to you by the instructor. The UIC selected will appear at the bottom of the “Create UIC” box. (2) In the “Create UIC” box, type the first four characters of your assigned UIC, followed by “ZZ”, and enter your last name as the “Name” of the unit. (3) Select the DOD Service Component, Command Code, and the Unit level of the new UIC (4) Click “Create” to see the newly created UIC under your assigned UIC. (5) In the “Hierarchy” box, select the radio button to the left your newly created UIC. (6) In the “Action” box, select “Remove” to remove your newly created UIC from the Hierarchy.

Administrative Hierarchy Adding and Editing a UIC
SHOW SLIDE 32: ADMINISTRATIVE HIERARCHY l. This module allows the MACOM Manager to search for a MACOM UIC and add it to a hierarchy. Type in the UIC you created in the previous exercise. Click “ Search” and the UIC will populate in the white box Select the DOD Service Component, Command Code, and the Unit level of the new UIC (4) Click “Add” in the lower left corner of the “Add UIC” block. You will see the UIC added as a child under the your assigned UIC. (6) In the “Hierarchy” box, select the radio button to the left your newly added UIC. (7) In the “Action” box, select “Delete” to remove your newly created UIC from the DTAS database. NOTE: When the UIC is unknown, an error will return stating “No rows returned matching the Search UIC value.” INSTRUCTOR NOTE: This is a building slide. Click next slide. This module allows the MACOM Manager to edit by moving, removing, or deleting an existing UIC and assign a UIC as a DTAS Mobile System. (1) Click the “edit” tab on the upper right hand of the screen. (2) Find the UIC given to you under the hierarchy and click the radio button. The UIC will populate in the “Edit UIC” block. (3) Change the Command Code from ARCENT to PACOM and click “Edit” (4) Change the Command Code back to ARCENT and click “Edit” to undo the change

Operational Hierarchy
SHOW SLIDE 33: OPERATIONAL HIERARCHY NOTE: Click “Operational Hierarchy” on the left hand side of the screen. n. The Operational Hierarchy allows users to create attachments and release from attachments. To create an attachment follow the sequence below: (1) Click on the Brigade UIC given to you Click on the small “plus sign” next to the Battalion UIC. The units below this UIC will appear Click on the circle next to the Company UIC. On the right hand of the screen, Company UIC will appear in the Selected UIC box (4) Click “Attach” for the Company UIC with all descendents to the BDE UIC. The Company UIC will appear with a green arrow showing the attachment to the Brigade o. To release from attachment follow the sequence below: (1) Click on the circle next to Company UIC. On the right hand of the screen, Company UIC will appear in the Selected UIC box (2) Click on Release Company UIC with all assigned descendants. The green arrow will disappear once the unit is no longer attached to the parent unit NOTE: Have the students click on “Static Table Maintenance” on the left hand side of the screen.

APOD Manager SHOW SLIDE 34: APOD MANAGER
p. This is a screenshot view of the APOD Manager module under the MACOM Manager login. This module is used to create new APOD locations in DTAS. INSTRUCTOR NOTE: Using the live system, demonstrate the various views and capabilities of the APOD Manager. The students will not be able to manipulate the APOD Manager.

Static Table Maintenance
Static Table Maintenance allows the Major Command Manager to update the following: Employer Code, Command Code, Operation Code, Assigned Location, Static Tables, Hospital Lookup, Patient Condition Lookup, Patient Disposition Code Lookup, and Patient Status Code Lookup The Major Command Manager can only add new records or edit existing records in the Static Tables. They can not edit the Assigned Locations. SHOW SLIDE 35: STATIC TABLE MAINTENANCE q. Static Table Maintenance allows the Major Command Manager to update the Employer Code, Command Code, Operation Code, Assigned Location Static Tables, Hospital Lookup, Patient Condition Lookup, Patient Disposition Code Lookup, and Patient Status Code Lookup. r. The Major Command Manager can only add new records or edit existing records in the static tables with the exception of Assigned Location. Mobile System Users can not make any changes to records in the static tables, and must contact the Major Command Manager to update, or add records to the static tables. NOTE: Mobile System Users must contact the Major Command Manager to update or add records to the Static Tables NOTE: It is important that no two locations have the same grid coordinates. If two locations are entered with the same grid coordinates, physical location data for these two locations cannot be displayed on the Unit Roster of the Mobile System. This will cause the user’s Unit Roster to error, and the report will not produce correctly.

Static Table Maintenance Locations
SHOW SLIDE 36: STATIC TABLE MAINTENANCE LOCATIONS Assigned Location allows mobile users to update the assigned and physical locations for a selected individual. Assigned Location refers to the location of a unit where a person is assigned. Users are required to select a country out of a country pick-list before they are permitted to select a location. After a user has selected a country, the application will populate the location pick-list with locations that are programmed within the selected country. u. Physical location is the actual camp, city, or grid coordinates where the person is located. Example: A Soldier is assigned to 1-4 Cav at Camp Saber, Iraq, but is forward in Camp Victory. His assigned location is Camp Saber; his physical location is Camp Victory. Requests to add new Locations to DTAS must be forwarded to the DTAS Theater Manager. The DTAS Theater Manager has access to add new Locations using this same module. NOTE: Instructor can create a new Assigned Location to demonstrate the function to students. Ensure you delete the new Assigned Location to maintain a clean training database.

Check on Learning Q. Who has access to the Major Command Level and what is their access level? A. Major Command Managers have full access. Helpdesk Clerks and select units have limited access. Q. What are the two types of Hierarchies within DTAS? A. Administrative and Operational SHOW SLIDE 37: CHECK ON LEARNING Q. Who has access to the Major Command Level and what is their access level? A. Major Command Managers have full access. Helpdesk Clerks and select units have limited access. Q. What are the two types of Hierarchies within DTAS? A. Administrative and Operational

APOD AND APOD MANAGER SHOW SLIDE 38: APOD AND APOD MANAGER
NOTE: TRANSITION SLIDE a. One of the MACOM Manager’s responsibilities includes establishing the APOD UICs for each APOD with the APOD Manager. After the UIC is created, the APOD Manager will assign incoming and/or outgoing units to an APOD UIC when they arrive or depart Theater. NOTE: This portion of the lesson will review the process and responsibilities of the APOD Manager. If you are assigned as an APOD Manager, you will receive additional training in Theater. NOTE: Have students log-in to the APOD Manager using the following URL with their assigned username and password:

Aerial Port of Debarkation (APOD)
Allows the MACOM Manager to manage Aerial Port of Debarkation (APOD) UICs and APOD User accounts. The APOD tool consists of two separate interface components: APOD Web Application Used by PAT Teams throughout APODs Create/Upload TRN files (a personnel data file generated by the Tactical Personnel System (TPS)) APOD Manager Managed by MACOM Managers Add/Remove/Update APOD SHOW SLIDE 39: AERIAL PORT OF DEBARKATION (APOD) b. The Major Command Manager Application includes an APOD tool that allows the MACOM Manger to track individuals as they enter the Aerial Port of Debarkation and assign them to a specific UIC within Theater. The APOD tool consists of two separate interface components: APOD Web Application and the APOD Manager. (1) The APOD Web Application is used by the PAT Teams and allows the creation and uploading of TRN files (2) The APOD Manager is a function that allows the MACOM and APOD Manager to manage the APOD UICs and APOD User accounts. The MACOM Manager manages the activities and responsibilities of the APOD Manager and ensures that all APODs are added, removed, or updated in DTAS NOTE: Remind students that they have previously discussed creating data files for DTAS during the eMILPO class and will discuss it again during this lesson when covering the Mass Assign/Add transaction.

APOD Module Process Completed by APOD Manager Scan individuals as they arrive at a Theater gateway TRN file is loaded into web-based APOD module Provide each individual with an accurate arrival date in Theater Capture their Projected Gaining UIC (PGUIC) Place personnel in an assigned location in Theater with a duty status of “In-transit, local reassignment” SHOW SLIDE 40: APOD MODULE PROCESS c. The APOD module process occurs when an individual or unit arrives in Theater. The process includes multiple steps and activities that must be performed by the APOD Manager to allow the DTAS system to properly track individuals arriving in Theater. Scan individuals as they arrive at a Theater gateway. This step generates a TRN file The TRN file is loaded into the web-based APOD module Provide each individual with an accurate arrival date to Theater Capture the Projected Gaining UIC (PGUIC) Place the individual in an assigned location in Theater with a duty status of “In-transit, local reassignment” As the Mobile User adds personnel to the unit’s mobile system, they are pulled from the APOD module and placed in their hierarchy with a duty status of Present for Duty (PDY) Completed by Mobile User

APOD Module Capabilities
The APOD tool allows all APODs to perform the following updates directly to the MACOM server with the Tactical Personnel System (TPS) generated TRN file via a Web Browser: Mass Add personnel entering the Theater for the first time on current deployment Update the Deployed Duty Status and Physical Location for personnel returning to Theater from TDY, emergency leave, R&R leave, etc Update the Deployed Duty Status and Physical Location for personnel departing Theater for any reason Update the Deployed Duty Status and Physical Location for personnel moving within Theater SHOW SLIDE 41: APOD MODULE CAPABILITIES d. The APOD tool allows all APODs to perform the following updates directly to the Theater server with the Tactical Personnel System (TPS) generated TRN file via a Web Browser: (1) Mass Add personnel entering Theater for the first time on current deployment (2) Update the Deployed Duty Status and Physical Location for personnel returning to Theater from TDY, emergency leave, R&R leave, etc. (3) Update the Deployed Duty Status and Physical Location for personnel departing from Theater for any reason (4) Update the Deployed Duty Status and Physical Location for personnel moving within Theater e. The capabilities of the APOD tool allow users to perform transactions at a greater speed, process incoming individuals all at one time, and improve the tracking capabilities of individuals within Theater.

APOD Main SHOW SLIDE 42: APOD MAIN
This is a screenshot view of the APOD Manager Main screen, APOD Batch report, and the APOD Batch Error report. This module is used to capture mass updates in DTAS for arriving and departing personnel and provides APOD reports. INSTRUCTOR NOTE: Using the live system, demonstrate the various views and capabilities of the APOD Manager Main. The students will not be able to manipulate the APOD Manager. INSTRUCTOR NOTE: This is a building slide.

Ideal Depart for R&R Example
SPC Todd departs for R&R through departure APOD APOD uploads TRN file updating SPC Todd’s location SPC Todd on CONUS R&R APOD (Departure Theater) TPS MOBILE SYSTEM SPC TODD is in RED/RNR status while on R&R leave APOD (Within Country) TPS MOBILE SYSTEM SHOW SLIDE 43: IDEAL DEPART FOR R&R EXAMPLE g. This is an example showing how a Soldier who is scheduled to return back to CONUS for R&R is processed in DTAS. INSTRUCTOR NOTE: This is a building slide and requires multiple clicks (1) SPC Todd departs from his unit for R&R; his DTAS Mobile Clerk will change his duty status code from PDY to RED/RNR (Redeployed/Rest and Recuperation). (2) SPC Todd will then arrive at an APOD location in Theater (the location can change based on Theater location). The APOD Manager will upload a departure TRN file and select if the location is “In Theater” or “CONUS or OCONUS”. This will allow the APOD web application to translate the TPS departure duty status automatically. (3) Next, SPC Todd will depart to another APOD within country. When he arrives the APOD Manager will upload another TRN file updating SPC Todd’s location. (4) When SPC Todd departs for his CONUS R&R location the APOD Manager ensures that SPC Todd’s duty status is RED/RNR. NOTE: At each location SPC Todd is required to swipe his CAC card in TPS. This creates the TRN file. SPC Todd departs through APOD for R&R APOD uploads TRN file updating SPC Todd’s location within country PDY (Unit Location) SPC Todd departs from his unit for R&R DTAS Mobile Clerk changes duty status code from PDY to RED/RNR DTAS MOBILE SYSTEM

Ideal Return from R&R Example
SPC Todd returns from R&R and enters into Theater APOD uploads TRN file updating SPC Todd’s physical location SPC Todd on CONUS R&R APOD (Initial Entry into Theater) TPS MOBILE SYSTEM SPC Todd is in RED/RNR status while on R&R leave TPS MOBILE SYSTEM APOD (Within Country) SHOW SLIDE 44: IDEAL RETURN FROM R&R EXAMPLE h. This is an example showing how a Soldier who is scheduled to return back from R&R leave is processed in DTAS. INSTRUCTOR NOTE: This is a building slide and requires multiple clicks SPC Todd returns to Theater from his CONUS R&R; at this time the APOD Manger will upload a TRN file updating SPC Todd’s location. SPC Todd departs this location and arrives at an APOD location in country. The APOD Manager will upload an arrival TRN file to update SPC Todd’s current location. (3) Next, SPC Todd will depart to his unit. (4) When SPC Todd arrives at his unit, his DTAS Mobile Clerk will change his duty status code from RED/RNR (Redeployed/Rest and Recuperation) to PDY. This process will ensure accountability of SPC Todd at all times while he is in Theater. SPC Todd returns from R&R through an APOD in country APOD uploads TRN file updating SPC Todd’s physical location SPC Todd Returns from R&R to his unit S1. DTAS Mobile Clerk changes status code to PDY and updates his physical location PDY (Unit Location) DTAS MOBILE SYSTEM

APOD Errors (1 of 2) Failed to Load TRN Record Errors - this error can occur immediately after a file is uploaded into memory. Type of Error Resolution Formatting errors User must generate the file for failed records with TPS Arrival duty status errors Verify and Change “Traffic Flow” Departure duty status errors Invalid duty status errors User must regenerate the file with valid APOD duty status SHOW SLIDE 45: APOD ERRORS (1 of 2) i. For each TPS-created TRN file that is submitted via the APOD web application, two types of errors may be generated. The first error is “Failed to Load Record Errors”. These type of errors can occur immediately after the file is “Uploaded” into memory. During the upload process, the web application checks for the following: (1) Formatting Errors-This occurs when the file is corrupt or manually manipulated. Resolution: TPS User must regenerate the file for failed records with TPS. (2) Arrival Duty Status Errors-This occurs if a departure duty status is uploaded with an arrival manifest and has an incorrect duty status. Resolution: User must ensure that the “Arrival’ has the correct “Traffic Flow” option. If the “Traffic Flow” option is incorrect, the user must upload the TRN file again with the “Departure” “Traffic Flow” selected. (3) Departure Duty Status Errors-This will occur if an “Arrival” duty status is uploaded with a “Departure” manifest. Resolution: User must ensure that the “Departure” has the correct “Traffic Flow” option. If the “Traffic Flow” option is incorrect, the user must upload the TRN file again with the “Arrival” “Traffic Flow” selected. (4) Invalid Duty Status Errors-This will occur if an invalid duty status is uploaded with any manifest. Resolution: User must use TPS to regenerate the file with a valid APOD Duty Status for failed records.

APOD Errors (2 of 2) APOD Theater Processing Errors-Occurs when the database receives and process the uploaded TRN file. Type of Error Resolution Adding a new person failed Resubmit; if continues, contact Help Desk Updating DUIC failed Updating duty status failed Updating assigned location failed Updating physical location failed Invalid INECCD value in input Determine the value; regenerate file Duty status is not valid for departure to CONUS or OCONUS Change destination; regenerate file Individual does not exist in DTAS Theater No action; contact MACOM Manager SHOW SLIDE 46: APOD ERRORS (2 of 2) j. The second error is “APOD Theater Processing Errors”. These type of errors can occur when the DTAS MACOM database receives and processes the uploaded TRN file. The possible errors include: (1) Adding a new person failed. Resolution: The user must research the MACOM database to determine the reason for failure and resubmit the update. If the user is unable to resolve the error, the user should contact the MACOM Help Desk for assistance. (2) Updating DUIC failed. Resolution: The user must research the MACOM database to determine the reason for failure and resubmit the update. If the user is unable to resolve the error, the user should contact the MACOM Help Desk for assistance. (3) Updating Duty Status failed. (4) Updating Assigned Location failed. Updating Physical Location failed. Invalid INECCD value in input -the record in the TPS file contained an invalid person type code. Resolution: The user must research the record in the TRN file to determine the incorrect (Incorrect Person Type) INECCD value. If necessary, the user must use TPS to regenerate the file with a valid INECCD for failed records. (7) Duty Status is not valid for Departure to CONUS or OCONUS - there are three departures (TPS) Duty Statuses that can only be used to depart personnel to “In Theater”: OLV, (Reassignment) RSG, and TRA. Resolution: If the individual is departing to “In Theater”, the user must upload the TRN file again and choose the correct destination. If the individual is departing for CONUS or OCONUS, the user must regenerate the file with valid departure Duty Status for the failed records. (8) Individual does not exist in DTAS Theater - this occur when a person does not exist in the DTAS Theater database. Resolution: No action is required by the APOD, the MACOM Manager must work with the unit to resolve the problem.

Preventive Measures Identify correct pending gain unit identification codes (PGUIC) for personnel on the TRN file. Coordinate with unit LNOs as necessary to facilitate the flow of information regarding movement and appropriate PGUICs. Ensure all TRN files generated by TPS have the correct computer clock time and date. Upload the TRN files into the APOD Module UIC associated with their location a minimum of twice daily or more as flights dictate. Designate personnel entering Theater in a temporary duty (TDY) status for less than 30 days to a PGUIC of ‘VISITR”. Designate personnel entering Theater in a TDY status from more than 30 days to the PGUIC of the unit they are in Theater to visit or support. SHOW SLIDE 47: PREVENTIVE MEASURES k. The APOD Manager can prevent the majority of the errors in the APOD tool by taking several preventive measures. These actions include: (1) Identifying the correct pending gain unit identification codes (PGUIC) for personnel on the TRN file (2) Coordinate with the LNOs as necessary to facilitate the flow of information regarding movement and appropriate PGUICs (3) Ensure all TRN files generated by TPS have the correct computer clock time and date (4) Upload the TRN files into the APOD Module UIC associated with their location a minimum of twice daily or more as flights dictate (5) Designate personnel entering Theater in a temporary duty (TDY) status for less than 30 days to PGUIC of “VISITR” (6) Designate personnel entering Theater in a TDY status from more than 30 days to the PGUIC of the unit they are in Theater to visit or support

RSO Division Assistance (Reception Staging and Onward Movement (RSO)
Determine need for APOD Module locations ICW ARCENT G1, publish policies and standards for APOD Operations ICW ARCENT G1, train PAT teams on correct APOD Module procedures Train PAT Teams on TPS execution Assist with updating outdated user list for APODs ICW ARCENT G1, perform oversight of APOD TRN uploads and identify and work to solve challenges SHOW SLIDE 48: RSO DIVISION ASSISTANCE l. The HRSC has a Reception Staging and Onward Movement (RSO) Division (formerly the R5 Division) that is responsible for providing MACOM and APOD Managers assistance and overseeing the following activities while in Theater: (1) Determine need for APOD Module locations (2) In coordination with ARCENT G1, publish policies and standards for APOD Operations (3) In coordination with ARCENT G1, train PAT teams on correct APOD Module procedures (4) Train PAT Teams on TPS execution (5) Assist with updating outdated user list for APODs (6) In coordination with ARCENT G1, perform oversight of APOD TRN uploads and identify and work to solve challenges

Check on Learning Q. What type of file is created when the APOD Manager scans in units? A. A TRN file Q. What are the two types of APOD errors that can occur in DTAS? A. Failed to Load TRN and APOD Theater Processing Errors SHOW SLIDE 49: CHECK ON LEARNING What type of file is created when the APOD Manager scans in units? A. A TRN File What are the two types of APOD errors that can occur in DTAS? A. Failed to Load TRN File and APOD Theater Processing Errors

DTAS DASHBOARD Show Slide 50: DTAS DASHBOARD
a. The DTAS Dashboard application was deployed to the production Major Command Level server in March Its main purpose is to assist users in the field, giving them a quick and effective way to retrieve personnel information captured in DTAS, whether they are deployed or non-deployed. The reports include Duty Status exception reports, accountability reports, JPERSTAT reports, and APERSTAT reports. The DTAS Dashboard application is available upon request to everyone who has access to Datastore (Battalion S1 thru Corps G1). b. The application also provides users the capability to search for information in the DTAS database. Since deployment, the Dashboard has been expanding its scope and is continually updated with new functionalities based on the customer’s needs. NOTE: All information retrieved from the DTAS Dashboard application is considered classified information and must be handled accordingly. NOTE: Have students log-in to the Dashboard using the following URL with their assigned username and password:

Security Statement Show Slide 51: SECURITY STATEMENT
c. The DTAS Dashboard is a web application running on the SIPRNET. Its main purpose is to provide users access to various types of reports such as exception reports, accountability reports, JPERSTAT reports, and APERSTAT reports. The reports allow users to drill down to find detailed information, such as points of contact, so that exception reports can be corrected. In addition, the Dashboard application provides a “Search” functionality including Personnel search, Mobile POC search, Hierarchy search, and Unit search. NOTE: Have the students click ”OK” to proceed.

Deployed or Non-Deployed Personnel
Show Slide 52: DEPLOYED OR NON-DEPLOYED PERSONNEL d. Users will have a choice to select viewing the reports for deployed or non-deployed personnel. Sections below will describe in detail reports available for deployed personnel. NOTE: Have the students select view Deployed Personnel Information and click "Submit”.

CLICK OK Show Slide 53: LOG-IN/MAIN PAGE e. The Dashboard application provides four major groups of reports. Exception reports, JPERSTAT reports, APERSTAT reports, and Search reports. The table below contains links to functionality currently on the Dashboard. From this page, users can view the Dashboard User’s Guide or select one of the options presented in the table: NOTE: At the Log-in, have the students enter the specified User Name and Password and click “OK”.

Exception Reports Shows all exception reports based on all personnel within a UIC Shows all exception reports based only on military service members within a UIC Duty status exception report within the ARCENT hierarchy Show Slide 54: EXCEPTION REPORTS f. Exception Reports - For deployed personnel, the Exception Reports options – All Personnel or Military Only, provide a quick glance, dashboard view, with a configurable color coded scheme, to show the exceptions of major duty statuses and APOD, i.e. counts shown in green are normal and below allowable range, yellow is within range, and red is above the range. Duty status exception report similar to the ARCENT report but for the top UIC of IRAQ Duty status exception report similar to the ARCENT report but for the top UIC of Afghanistan

MAINTAIN won’t be hearing from us!
Color Coded Counts Yellow numbers on an exception report suggests that units don’t have many discrepancies Within Range Show Slide 55: COLOR CODED COUNTS g. This page provides counts of personnel/mobiles that fall into the various exception and miscellaneous report categories. The counts are color coded based on the configurable thresholds shown on the right-hand side of the screen. The counts shown on this page are refreshed every 15 minutes. The Duty Status Exception reports are a set of individual reports that display the following exception categories: (1) In-Transit (TRA) over 30 days Rest and Recuperate (RnR) over 30 days. Wound in Action (WIA) over 1 day (4) Unverified (mini record indicator = U) h. Counts are color coded – based on configurable thresholds. (1) Red: Exceed threshold (2) Yellow: Within range of threshold (3) Green: Normal and below threshold i. For each exception, reports start with a list of UICs showing POC name, , phone – sorted in descending order by personnel counts. j. When the page is first opened, the default view of the report is: “All Personnel” (military and civilians) and by Deployed UIC or “DUIC.” k. The reports also allow drill down by UIC to view actual personnel for that unit. l. Once drilled down, there are options allowing the user to view exception reports by Mobile UIC or Deployed UIC. The deployed UIC counts will not include APOD UICs. m. The Personnel Filter drop down list allows users to view the reports by branch of service or civilian. n. Select a UIC from the drilled down report to see a list of personnel names in that unit who met the criteria. The title of the report will show the UIC and option selected. o. The Miscellaneous report is another type of report from the Exception and consists of the following reports: (1) Counts of Mobiles that have not Synchronized/Initialized in the Past 7 Days (2) Count of Personnel with Unknown Physical Location MAINTAIN won’t be hearing from us! Below Range FIX DISCREPANCY ASAP!!! Above Range

ARCENT Reports Show Slide 56: ARCENT REPORTS Transition slide

Review discrepancy reports within Theater of Operations
ARCENT Reports (1 of 5) Provides a duty status exception report for ARCENT hierarchy starting from the top UIC of ARCENT and all of its children UICs. Show Slide 57: ARCENT REPORTS (1 of 5) a. The ARCENT Report is another report that users can select from the Exceptions page. It provides a duty status exception report for ARCENT hierarchy starting with the top UIC of the ARCENT administrative hierarchy and all of its subordinate UICs. Review discrepancy reports within Theater of Operations

ARCENT Reports (2 of 5) Show Slide 58: ARCENT REPORT (2 of 5)
b. The ARCENT Report contains the following data: (1) TRA (Transit) over 30 days (2) RnR (Rest and Recuperate) over 30 days (3) Pending Gains over 30 days (4) WIA (Wounded in Action) over 1 day (5) Unverified (mini record indicator = ‘U’)

When the UIC W46E61 is selected The following report will be displayed
ARCENT Reports (3 of 5) When the UIC W46E61 is selected The following report will be displayed Show Slide 59: ARCENT REPORT (3 of 5) c. When the UIC is shown in blue, it allows drill down to subordinate UICs when the UIC is selected. d. When the count is shown in blue, select the count under the category to see the list of personnel who met the criteria. The personnel may belong to that particular UIC or a UIC within the hierarchy chain. e. When the count is shown in black, it means the current count is applied to the UIC shown on the left.

ARCENT Reports (4 of 5) Blue hyperlink lets you verify the personnel under that category When Pending Gain over 30 days is selected, the following report is displayed Show Slide 60: ARCENT REPORT (4 of 5) When the UIC is shown in blue, users can continue to drill down to see immediate subordinate UIC(s) and its associated exceptions. Users can also click the count shown in blue to see the personnel for that category. g. When selecting pending gains over 30 days, the following report is displayed which will allow the user to make updates. Make the necessary updates

Export to Excel to save then entire report on a spreadsheet
ARCENT Reports (5 of 5) Show Slide 61: ARCENT REPORT (5 of 5) h. Clicking on the “Export to Excel” button on the left, users can save the entire report to an Excel file. Export to Excel to save then entire report on a spreadsheet

Iraq and Afghanistan Reports (1of 2)
Show Slide 62: IRAQ AND AFGHANISTAN REPORT (1 of 2) i. The Iraq and Afghanistan Reports are other reports that users can select from the Exceptions page. They provide a duty status exception report similar to the ARCENT report; but, for the top UIC of the Iraq or Afghanistan administrative hierarchy (i.e. W1IRAQ). The report has the following properties: (1) TRA over 30 days (2) RnR over 30 days (3) Pending Gains over 30 days (4) WIA over 1 day (5) Unverified (mini record indicator = ‘U’) All functions and buttons that are available in the ARCENT report are also available in the Afghanistan and Iraq report

Iraq and Afghanistan Reports
(2 of 2) Show Slide 63: IRAQ AND AFGHANISTAN REPORT (2 of 2) j. When the UIC is shown in blue, it allows drill down to subordinate UICs when the UIC is selected. k. When the count is shown in blue, select the count under the category to see the list of personnel who met the criteria. The personnel may belong to that particular UIC or a UIC within the hierarchy chain. l. When the count is shown in black, it means the current count is applied to the UIC shown on the left.

JPERSTAT Reports Show Slide 64: JPERSTAT REPORTS
NOTE: Transition Slide

JPERSTAT Reports Shows JPERSTAT numbers by Country and Command
Shows JPERSTAT numbers for ARCENT Show Slide 65: JPERSTAT REPORTS a. The JPERSTAT report is a complex report and has the following characteristics: (1) To maintain the same business rules with the JPERSTAT cubes in Datastore, the contents of the report are refreshed twice a day at 0500 GMT and 1700 GMT. That means the data on the report is static for 12 hours. The last refreshed date is shown on the title of the report. (2) The report is grouped by countries and base camps within each country. There are total rows for each base camp, country, and all countries for the report. There is also the Previous Grand Total row at the bottom of the report so that the Delta Grand Total row can be calculated for the day. (3) The report shows the operational strength – duty status of PDY or TDY. (4) The report uses the Administrative UIC hierarchy. (5) Locations used on the report are physical locations. (6) The report counts personnel in the following categories: Military active personnel Reserve personnel National Guard personnel Civilians including military civilians and contractors Females (7) For each of the person type groups listed above, the report also shows yesterday’s counts and calculates the deltas based on today’s counts. Yesterday’s count is based on the first refresh from the previous day. (8) The counts on the JPERSTAT report can be drilled down to see a personnel detail report which includes: last name, first name, GUID, rank, PMOS, DUIC, country, base camp, person type description, and unit name. (9) The output of the JPERSTAT report can be exported to excel by clicking the Export to Excel button on the left. (10) JPERSTAT Help hyperlink at the top of the page, provides business rules used to create JPERSTAT report. Shows JPERSTAT numbers for units in Iraq Shows JPERSTAT numbers for units in Afghanistan Generates the JPERSTAT report based on user’s entered DUIC. Users also have option to select whether to include or exclude sub-units.

JPERSTAT Reports By Area of Responsibility (1 of 2)
Show Slide 66: JPERSTAT REPORTS BY AREA OF RESPONSIBILITY (1 of 2) b. To generate the JPERSTAT for all countries, from the country drop down box, click “ALL” within the country pick-list and then click the “Generate” button on the left. The JPERSTAT will be generated for CENTCOM listing all countries and all Base Camps existed in those countries that have deployed personnel in DTAS. c. To generate the JPERSTAT for a particular country, open the pick-list for each option respectively and select the desired items for the report. NOTE: The pick-lists for countries are sorted alphabetically. Search a Country or Command by numbers

JPERSTAT Reports By Area of Responsibility (2 of 2)
Show Slide 67: JPERSTAT REPORTS BY AREA OF RESPONSIBILITY (2 of 2) d. Using the windows scroll bars, users can scroll to the right to see the rest of the columns and scroll down to see the rest of the report. The title of the JPERSTAT has the last refreshed date and time. This is an important indicator of the JPERSTAT. It signifies that the data used to build the report was last captured on this date/time. The information is static until the next scheduled refresh run. f. The JPERSTAT report can be exported to Excel by selecting the “Export to Excel” button on the left. To reset the previous option back to the default, select the “Reset” button on the left.

JPERSTAT Reports By Duty Status
Show Slide 68: JPERSTAT REPORT BY DUTY STATUS g. For the JPERSTAT Report, counts are based on personnel in 'TDY' or 'PDY' duty status. h. The user must enter an Assigned Unit Identification Code (ASUIC) and the ASUIC must exist in the DTAS Hierarchy. The report is generated based on the ASUIC point in the Administrative Hierarchy. In addition, the results will be based on the inclusion or exclusion of sub-units. i. If the user is unsure of the ASUIC code, they go to the Unit Name Search page. After the name search, click on the UIC Code link to generate a report for that UIC and its descendant units. NOTE: Results can be exported to an Excel spreadsheet.

Search Reports Show Slide 69: SEARCH REPORTS NOTE: Transition Slide

Search Reports (1 of 3) Provides a quick way to search for one or more personnel based on several search criteria Retrieves information from the UIC provided Retrieves information from the unit name provided Show Slide 70: SEARCH REPORTS (1 of 3) a. Similar to the Search Reports for Deployed personnel, this section provides users different ways to retrieve deployed personnel and unit information. Available options are: (1) Personnel Search (2) Operational Personnel (3) Physical Location Search (4) Mobile POC Search (5) Unit Name Search (6) Hierarchy Search Retrieves information from the provided UIC code and displays the unit’s hierarchy

to search one or more personnel based on several search criteria
Search Reports (2 of 3) Provides a quick way to search one or more personnel based on several search criteria Show Slide 71: SEARCH REPORT (2 of 3) b. The Personnel Search Report provides a quick way to search for one or more personnel based on several search criteria such as SSN or file of SSNs, last name, first name, person type, duty status, ASUIC, primary MOS, physical location, country and/or assigned location. Among those listed, SSN, last name, and Primary MOS allow the wildcard search. That means only the first few characters are needed. The following conditions apply to the Personnel Search page: (1) At least one search criterion (i.e. first name, last name, SSN, etc.) must be specified by the user. (2) If specifying a file of SSNs or EDI PN IDs, the file must be a text file. The user cannot specify a single SSN and a file of SSN's. A file of SSNs cannot be specified with a single SSN value. A file of EDI PN IDs cannot be specified with a single EDI PN ID value. (3) Users may perform a wild card search on SSN, EDI PN ID, last name and primary MOS. (4) The pay grade search capability is only available after selecting a person type of US Army Soldier, Other US Service Member, or DoD Federal Civilian. These are the only person types associated with a pay grade. (5) If entered, the primary MOS must contain at least 2 characters which can occur at any position. (6) Exact match searches are performed for first name, person type, duty status, and ASUIC. (7) The subordinate ASUIC Checkbox requires that the user specify a ASUIC. (8) The query will execute for the entered ASUIC, subordinate ASUICs, and additional search criteria. (9) The ASUIC returned from a query appears as a hyperlink when the person exists on a mobile. NOTE: If specifying a file of SSNs or EDI PN IDs, specify any other search criteria first. Click the hyperlink to identify the mobile and contact information.

individual or multiple field inputs
Search Reports (3 of 3) Search criteria can be individual or multiple field inputs If search criteria is only UIC. The following report is generated. Show Slide 72: SEARCH REPORT (3 of 3) c. The rows count is displayed at the top of the report showing the total search result that matches the search criteria. The report is sorted by last name. The typed character is not case sensitive. Clicking on the unit under ASUIC column will trigger the Mobile POC Search page to be displayed for that UIC. d. A sorting function for the Personnel Search page is also available. By moving the mouse to any column header (column heading), a link will appear that, when selected, allows the report to be sorted by that column. The sorting will toggle from ascending to descending and vice versa. NOTE: ATUIC – attached UIC, and APOD UICs are also available in the report. If the ASUIC is not Highlighted in blue, then the UIC is the APOD UIC. NOTE: To reset the page or clear out the current search, select the “Reset” button. To go back to the main page, click the “Main Page” button.

Hierarchy Search (1 of 2) Show Slide 73: HIERARCHY SEARCH (1 of 2)
e. The Hierarchy Search Report helps users to retrieve, from the provided UIC code, the unit’s hierarchy including its parents, grandparent, and children UICs along with the available mobile’s point of contact information. When the Hierarchy Search function is selected from the main page, this page is displayed. f. The user must enter a full UIC code and select the hierarchy type button - ADCON or OPCON. The default is ADCON. Then select the Search button on the left.

Enter full UIC code and select hierarchy type
Hierarchy Search (2 of 2) Enter full UIC code and select hierarchy type The following report is generated Show Slide 74: HIERARCHY SEARCH (2 of 2) g. The entered UIC is not case sensitive. To reset or clear the page, click the “Reset” button. To go back to the main page, click the “Main Page” button. NOTE: Clicking on the “Export to Excel” button on the left to export the report output to an Excel file.

Check on Learning Q. What are the four major groups of reports available in Dashboard? A. Exception Reports JPERSTAT Reports APERSTAT Reports Search Reports Q. What report provides a quick way to search one or more personnel based on several search criteria? A. Search Report Q. What report provides a joint personnel status report for a group of deployed units in the administrative hierarchy, of all locations, and across all person types and branches of services? A. JPERSTAT Report SHOW SLIDE 75: CHECK ON LEARNING Q: What are the four major groups of reports available in Dashboard? A: Exception Reports JPERSTAT Reports APERSTAT Reports Search Reports Q: What report provides a quick way to search one or more personnel based on several search criteria? A: Search Reports. Q: What report provides a joint personnel status report for a group of deployed units in the administrative hierarchy, of all locations, and across all person types and branches of services? A: JPERSTAT REPORT

DTAS Mobile System Initialization
SHOW SLIDE 76: MOBILE SYSTEM INITIALIZATION NOTE: TRANSITION SLIDE

Mobile System Initialization (1 of 2)
Enter the required data in the pop-up System Activation window. SHOW SLIDE 78: DTAS MOBILE SYSTEM INITIALIZATION (1 of 2) d. After coordination has taken place and the unit S-1s have prepared for set-up, the mobile system must be initialized. The Mobile User must call the Major Command Level Manager to receive the IP Address and System DUIC and Activation Key. After entering the information provided by the Major Command Level Manager, plug in the necessary information and select “Activate”. NOTE: Have students log-in to the Mobile System: Click on DTAS Icon on desktop. Pop-up System Activation window will appear. Enter Student Name as POC. Phone and s can be generic. Location is Fort Jackson. Enter UIC assigned to Student. Enter Activation Key. (Instructor must Assign each Mobile in MACOM Manager and record and distribute Activation Keys to students prior to class. Activation Keys are only good for 24 hours.) URL is ps2.training.dtas.mil

DTAS Mobile System Setup
Personnel Pre-deployment Processing (PPP) CONUS Replacement Center (CRC) 1 MANIFEST SITE S-1 obtains TRN File from manifest site at CRC or at APOD/SPOD, or S-1 can download eMILPO file prior to deploying Manifest a Service member, Joint Service Member, DoD Civilian, Contractor, Foreign Nationals 3 2 Aerial Port of Debarkation (APOD) Sea Port of Debarkation (SPOD) Mobile System Users Synchronize with DTAS MACOM Database SHOW SLIDE 78: DTAS MOBILE SYSTEM SET-UP a. Manifest Site (1) S1 obtains TRN Files from the manifest site at CRC or at the APOD/SPODS, or the S-1 can down load eMILPO files prior to deploying (2) Manifest a Soldier, Joint Service Member, DoD Civilian, Contractor, or Foreign Nationals b. APOD/SPOD - Mobile System users must coordinate the following with the Major Command Level Manager: (1) UIC placed in hierarchy on the Major Command Level System (2) Wartime requirements documentation loaded to Major Command Level (3) Obtain Major Command Level System IP Address and Mobile System Activation Key c. Mobile System Users must ensure that the following occurs: (1) S-1 Personnel have access to and connect with SIPRNET (2) Initialize DTAS system (3) Add personnel to DTAS via Add Personnel Function, or Mass Add using TPS(TRN) eMILPO (XML), or Excel (CSV) load file BN BDE CJTF Mobile System users must coordinate the following with the Major Command Level Manager: UIC placed in hierarchy on Major Command Level System Wartime requirements documentation loaded to Major Command Level Obtain Major Command Level System IP Address and Mobile System Activation Key Division S-1 Personnel plug into SIPRNET Initialize DTAS system Add personnel to DTAS via Add Personnel Function, or Mass Add using a TPS (TRN), eMILPO (XML), or Excel (CSV) Load file.

UIC Hierarchy UIC Hierarchy must be established prior to deploying.
Ensure completed hierarchy is turned into Major Command Level Manager. Higher Element to the Left SHOW SLIDE 79: UIC HIERARCHY f. As a reiteration, the UIC hierarchy must be established prior to deploying and provided to the Major Command Level Manager. This prepares your unit to properly utilize the DTAS database upon arrival. When you open DTAS and begin downloading unit and personnel files, the hierarchy should be depicted as illustrated here.

The Main Screen and Tabs
SHOW SLIDE 80: THE MAIN SCREEN AND TABS NOTE: TRANSITION SLIDE

DTAS – The Display Grid SHOW SLIDE 81: DTAS - THE DISPLAY GRID
a. The Display Grid is viewed when you open DTAS. This grid is the main screen; but, the technical term is "Display Grid". Briefly discuss the configuration of this screen. We will go into most of the areas in more detail through the lesson plan. Draw the students’ attention to the top left hand of the screen. The four tabs allow the user to do the following: (1) People Tab – Allow the viewing of personnel and selecting personnel for updating (2) Location Tab - Identifies locations within the deployed area. Locations are managed by the Major Command Level Manager (3) Reports Tab - Displays the available reports: (a) Gains/Losses (b) In Transit Reports (c) PERSTAT Reports (d) Unit Roster (4) Management Tab - Allows for the management of equipment NOTE: Remind personnel that the DTAS Functional Guidance provides more in-depth instruction on the functionalities and business rules of DTAS. b. Note the buttons at the bottom of the display grid. These buttons allow the user to select a personnel function. Alternately, they can Right Click from within the display grid to access a pop-up menu.

DTAS – The Display Grid UIC Hierarchy Extended
SHOW SLIDE 82: DTAS - THE DISPLAY GRID UIC HIERARCHY EXTENDED c. This slide depicts where the user’s UIC hierarchy would appear and the view that they would expect to see.

Adding Personnel There are four ways to add personnel into the DTAS Mobile System: Add individual person Mass add via TRN file (TPS) Mass add via XML file (eMILPO) Mass add via CSV file (Text) SHOW SLIDE 83: ADDING PERSONNEL d. This slide depicts the four ways to add personnel to the DTAS database. NOTE: Ask the students to explain what they think may be the difference between an individual vs. mass add.

Data Extract - eMILPO (1 of 10)
Using your web browser navigate to and click on eMILPO SHOW SLIDE 84: DATA EXTRACT - eMILPO (1 of 10) k. Let's quickly look at a series of screen shots that will depict how easily a DTAS file can be created from e-MILPO. e-MILPO is the most widely used system for downloading data to DTAS. The file when downloaded from e-MILPO will carry the extension of "XML". 84

Click “Accept”. SHOW SLIDE 85: DATA EXTRACT - eMILPO (2 of 10) NOTE TO INSTRUCTOR: Have the students read instructions on the slide.

Select “DTAS Soldier Record” SHOW SLIDE 86: DATA EXTRACT - eMILPO (3 of 10) NOTE TO INSTRUCTOR: Have the students select DTAS Soldier Record. 86

Select UIC for Search Criteria SHOW SLIDE 87: DATA EXTRACT - eMILPO (4 of 10) NOTE TO INSTRUCTOR: Tell the students that this page allows the user to build a Soldier list for the working session. Have the students select “UIC” for the search criteria. 87

Type UIC and click “ADD” W05611 SHOW SLIDE 33: DATA EXTRACT - eMILPO (5 of 10) NOTE TO INSTRUCTOR: Have the students type in the UIC, W0xxxx and then click “ADD.” The first two xx are the class number, the second two xx are the student number. 88

After UIC is added to Selected Criteria, click “Search” UIC: W05611 SHOW SLIDE 89: DATA EXTRACT - eMILPO (6 of 10) NOTE TO INSTRUCTOR: Have the students click on “Search” once the UIC has been added to the Selected Criteria. 89

Highlight “Select” to choose all Soldiers SHOW SLIDE 90: DATA EXTRACT - eMILPO (7 of 10) NOTE TO INSTRUCTOR: Have the students select Soldiers by clicking on the corresponding checkboxes in the Select/Deselect column. 90

Scroll to the bottom and click “OK” SHOW SLIDE 91: DATA EXTRACT - eMILPO (8 of 10) NOTE TO INSTRUCTOR: Have the students scroll to the bottom of the page and select “OK.” 91

Click on the blue hyperlink SHOW SLIDE 92: DATA EXTRACT - eMILPO (9 of 10) NOTE TO INSTRUCTOR: Have the students click on the hyperlink to extract Soldier data and download the file. 92

Click on “Save” and save file to Desktop SHOW SLIDE 93: DATA EXTRACT - eMILPO (10 of 10) NOTE TO INSTRUCTOR: Have the students select “Save” and choose a location to save the file to their desktop. 93

TPS to a TRN File SHOW SLIDE 94: TPS to a TRN File l. This is what a data file extracted from TPS would resemble when downloaded. This is what a TRN data file created in TPS resembles when displayed.

DTAS - Locations Tab SHOW SLIDE 95: DTAS - LOCATIONS TAB
m. When selecting the Display Grid Locations Tab your screen will open up to a view similar to what you are viewing on this screen shot. The locations tab displays data related to locations within the theater. Locations are managed, including adding and editing locations, by the theater manager. n. One can sort in alphabetical order by location name or sequence by country name by clicking on the top of the "Location Name" and "Country" columns respectively. 95

DTAS – Reports Tab The “View” function allows you to view the “Army” or “Marine” view. Select this box if you wish to include sub-unit data to your report. SHOW SLIDE 96: DTAS - REPORTS TAB o. When preparing to generate a report, select reports from the Display Gird. Once opened your computer screen view should resemble this screen shot. To generate a report perform the following steps: (1) Select a UIC from the Select UIC pick list (also sub units if desired) (2) Click the "radio button" to the left of the report you wish to generate. (3) Click "view report" to generate the report. (4) DTAS displays the report in Microsoft Excel. At this point you can print or save the file as a new name by selecting the appropriate functions at the top of the screen "print" or "save as" respectively. 96

DTAS – Management Tab SHOW SLIDE 97: DTAS - MANAGEMENT TAB
p. Allows the S-1 to maintain and update an inventory of equipment assigned to unit personnel. 97

Check On Learning Q: Name the four tabs on the Display Grid and their related functions. A: (1) People Tab - Allows for viewing of personnel and selecting personnel for updating. (2) Location Tab - Identifies locations within the deployed area. Locations are managed by the Theater DTAS Manager. (3) Reports Tab - Displays the available reports accessible for generation and they are: a. Gains/Losses b. In Transit Reports c. PERSTAT Reports d. Unit Roster (4) Management Tab - Allows for the management of equipment. SHOW SLIDE 98: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q: Name the four tabs on the Display Grid and their related functions. A: (1) People Tab - Allows for viewing of personnel and selecting personnel for updating. (2) Location Tab - Identifies locations within the deployed area. Locations are managed by the Theater DTAS Manager. (3) Reports Tab - Displays the available reports accessible for generation and they are: a. Gains/Losses b. In Transit Reports c. PERSTAT Reports d. Unit Roster (4) Management Tab - Allows for the management of equipment. SUMMARY: We have just completed Learning Activity 3, Input Unit Personnel Files to the DTAS Database. Next, we will Add, Attach, and Assign Personnel using DTAS.

Mass Add Wizard SHOW SLIDE 99: MASS ASSIGN WIZARD
NOTE: Transition Slide The Mass Assign Wizard function allows users to load data to the DTAS database using an eMILPO XML file, a TPS TRN file, or a Comma Separated Value (CSV) file. The XML and TRN files are created in eMILPO and TPS, respectively, and are saved to a disk or other removable/transportable media. The CSV file is created as a text file and converted to Excel. Normally the CSV file is not used for uploading. To load data from a file, perform the following steps: NOTE: Students will use the TRN and XLM files previously saved on their desktops for all future transactions.

DTAS Mass Add Wizard (1 of 9)
From the Tools menu select “Mass Add Wizard”. SHOW SLIDE 100: DTAS MASS ADD WIZARD (1 of 9) Learning Step/Activity 4. Add, attach, and assign personnel in DTAS Method of Instruction: Hands-on Instructor to Student Ratio: 1:16 Time of Instruction: 15 mins a. The Mass Assign Wizard function allows you to load data to your DTAS database using an eMILPO XML load file, a TPS TRN file, or a Comma Separated Value (CSV) file. The XML and TRN files are created in eMILPO to TPS, respectively, and are saved to a disk or other removable/transportable media. To load data from a file, perform the following steps: b. From the tools menu select "Mass Assign Wizard".

Click the “Select File” tab. SHOW SLIDE 101: DTAS MASS ADD WIZARD (2 of 9) c. A dialogue box appears that prompts you to select a file. Click the "Select File" tab.

Browse for the file. SHOW SLIDE 102: DTAS MASS ADD WIZARD (3 of 9) d. After you click the "Select File" tab, another dialogue box opens which will allow you to browse to the location of the file that contains the information to allow you to "Mass Add" personnel to DTAS.

After file selection is confirmed select “Select Next”. SHOW SLIDE 103: DTAS MASS ADD WIZARD (4 of 9) e. After you have "found" and "selected" the file containing the information that you wish to download to DTAS using the "Mass Add" function. You will see the file name appear in the dialogue box as seen on this screen shot. Select "Next".

Select “Select All” and then select “Next”. SHOW SLIDE 104: DTAS MASS ADD WIZARD (5 of 9) f. After selecting next, you will see a list of names appear in the dialogue box. At this time you can select only those names you desire to download, or you can either choose the option "Select All" or "Deselect All". After you have identified personnel to "Mass Add" to DTAS then click select "Next".

Select the Operation from the drop-down box and then select “Next”. SHOW SLIDE 105: MASS ADD WIZARD (6 of 9) g. A dialogue box appears prompting the user for the "Operation". Select the desired "Operation" then select "Next". NOTE: Tell the students that the data and time group defaults to the current date and time.

Select the Locations from the drop-down box and then select “Next”. SHOW SLIDE 106: DTAS MASS ADD WIZARD (7 of 9) h. A dialogue box appears prompting you for "Location" information. Type in the location information on the left hand side. This entry automatically updates the right hand side. Select "Next".

Select the Tour Status and Tour Status Sub-Type from the drop-down box and then select “Finish”. SHOW SLIDE 107: DTAS MASS ADD WIZARD (8 of 9) i. A dialogue box appears prompting the user to enter "Tour Status" , "Tour Status Subtype" and "Number of Days". Provide the requested information and select "Finish".

This is an example of your downloaded personnel file SHOW SLIDE 108: DTAS MASS ADD WIZARD (9 of 9) j. The downloaded personnel files should appear. At this time you may manipulate the personnel data.

Mass Assign Wizard SHOW SLIDE 109: MASS ASSIGN WIZARD
NOTE: Transition Slide The Mass Assign Wizard function allows users to load data to the DTAS database using an eMILPO XML file, a TPS TRN file, or a Comma Separated Value (CSV) file. The XML and TRN files are created in eMILPO and TPS, respectively, and are saved to a disk or other removable/transportable media. The CSV file is created as a text file and converted to Excel. Normally the CSV file is not used for uploading. To load data from a file, perform the following steps: NOTE: Students will use the TRN and XLM files previously saved on their desktops for all future transactions.

DTAS Mass Assign Wizard (1 of 9)
From the Tools menu select “Mass Assign Wizard” SHOW SLIDE 110: DTAS MASS ASSIGN WIZARD (1 of 9) b. From the tools menu select "Mass Assign Wizard"

Click the “Select File” tab SHOW SLIDE 111: DTAS MASS ASSIGN WIZARD (2 of 9) c. A dialogue box appears that prompts the user to select a file. Click the "Select File" tab. NOTE: Do NOT use any files previously created in eMILPO. Use ONLY the files provided by your instructor.

Browse for the file SHOW SLIDE 112: DTAS MASS ASSIGN WIZARD (3 of 9) d. After clicking the "Select File" tab, a new dialogue box opens which allows users to browse to the location of the file that contains the needed information. NOTE: Do NOT use any files previously created in eMILPO. Use ONLY the files provided by your instructor.

After file selection is confirmed select “Select Next” SHOW SLIDE 113: DTAS MASS ASSIGN WIZARD (4 of 9) e. After users have "found" and "selected" the file containing the information for download to DTAS, the file name appears in the dialogue box. Select "Next".

DTAS Mass Assign Wizard
(5 of 9) SHOW SLIDE 114: DTAS MASS ASSIGN WIZARD (5 of 9) f. After selecting “Next”, a list of names appears in the dialogue box. At this time, select only those names desired for download, or choose either "Select All" or "Deselect All". Make a selection and click "Next". Select “Select All” and then select “Next”

Select the Operation from the drop-down box and then select “Next” SHOW SLIDE 115: MASS ASSIGN WIZARD (6 of 9) g. A dialogue box appears prompting the user for the "Operation". Select the desired "Operation" then select "Next". NOTE: The date and time group defaults to the current date and time.

Select the Locations from the drop-down box and then select “Next” SHOW SLIDE 116: DTAS MASS ASSIGN WIZARD (7 of 9) h. A dialogue box appears prompting users for "Location" information. Type in the location information on the left hand side. This entry automatically updates the right hand side. Select "Next". NOTE: The instructor will provide required information.

SHOW SLIDE 117: DTAS MASS ASSIGN WIZARD (8 of 9) A dialogue box appears prompting the user to enter "Tour Status,” "Tour Status Subtype," and "Number of Days". Provide the requested information and select "Finish". NOTE: The instructor will provide required information. Select the Tour Status and Tour Status Sub-Type from the drop-down box and then select “Finish”

SHOW SLIDE 118: DTAS MASS ASSIGN WIZARD (9 of 9) The downloaded personnel files will appear. At this time users may manipulate the personnel data using the tabs at the bottom of the screens. NOTE: This screen will not match the file previously provided by the instructor.

Mass Attach Wizard SHOW SLIDE 119: MASS ATTACH WIZARD
NOTE: TRANSITION SLIDE k. The Mass Attach Wizard function allows users to load data to the DTAS database using an eMILPO XML file, a TPS TRN file, or a Comma Separated Value (CSV) file. The XML and TRN files are created in eMILPO and TPS, respectively and are saved to a disk or other removable/transportable media. This option is used when attaching large number of personnel or units.

DTAS Mass Attach Wizard
From the Tools menu select “Mass Attach Wizard” and then follow the prompts as with the “Mass Add Wizard” SHOW SLIDE 120: DTAS - MASS ATTACH WIZARD l. Loading data to DTAS through the "Mass Attach" wizard closely resembles the steps just completed for "Mass Add". From the tools menu select "Mass Attach Wizard" and continue with the steps that were previously followed for "Mass Add Wizard". NOTE: If users receive an error message indicating that the files are problematic, users troubleshoot using the Functional Guidance. Remember, knowing the business rules supports a more proficient use of the system. NOTE: Conduct a check on learning and summarize the learning activity. Q: What type of files can you use to upload personnel data with into the Mass Assign Wizard? A: eMILPO XML, TPS TRN, or a Comma Separated Value (CSV) file

Assign Personnel SHOW SLIDE 121: ASSIGN PERSONNEL
NOTE: TRANSITION SLIDE a. The "Assign Personnel" function allows users to add personnel as they are assigned to a UIC. This function is set up using a wizard process that will guides users through the steps needed to assign personnel. To add an individual, perform the following steps.

DTAS - Assign Personnel (1 of 4)
Select “Assign Personnel” from the Buttons menu SHOW SLIDE 122: DTAS - ASSIGN PERSONNEL (1 of 4) b. Select the "Assign Personnel" button from the Display Grid.

SHOW SLIDE 123: DTAS - ASSIGN PERSONNEL (2 of 4) c. A dialogue box appears requesting fields of information. The information required will vary depending on fields selected. As a minimum some of the required fields are: (1) Type of person being added (2) Date of Birth (3) Sex (4) Last Name (5) First Name (6) Middle Name (7) DOD Component (8) Rank (9) Operation NOTE: Required fields are annotated by an asterisk until they gain familiarity all users of DTAS should refer to the business rules for each function. The business rules are found in the DTAS functional guidance. Complete the required data fields and then select “Next”

SHOW SLIDE 124: DTAS - ASSIGN PERSONNEL (3 of 4) d. A dialogue box appears requesting additional information relative to the Soldier. Mandatory element fields are preceded by an asterisk. Some of the required elements are: (1) Duty Status (2) Location (3) Tour Status (4) Number of Days on Tour e. After all required fields are completed select "Finish". NOTE: The Instructor will provide information for required data fields. Complete the required data fields and then select “Finish” 124

The Soldier’s name and other data elements should be visible in the DTAS database SHOW SLIDE 125: DTAS - ASSIGN PERSONNEL (4 of 4) f. The Soldier's name as well as all other required data elements should appear. At this point, users can begin making additional updates as required. g. The Add Personnel function is performed at the lowest level of SIPRNET connectivity. (1) If an incorrect mini-record is pulled down due to incorrect SSN entry, the record can not be deleted. Instead, submit a duty status update, changing the Soldier’s duty status to ‘Redeployed - Erroneously Added’. The record will ‘age off’ the mobile system 24 hours later. Users can immediately add the correct SSN (do not need to wait until the incorrect SSN is gone). There is no departure transaction in DTAS. If a person is reassigned from one unit to another in Theater, the gaining unit will submit an ‘Add Personnel’ transaction which will remove the associated mini-record from the losing unit’s mobile system. NOTE: After there is an entry in the DTAS database all "Buttons" at the bottom of the screen are now illuminated. NOTE: The Mobile System must synchronize before changes are seen. 125

DTAS - Assign then Search
When assigning a new Soldier ensure that the Soldier has been added by “Searching” for their name SHOW SLIDE 126: ASSIGN THEN SEARCH h. After assigning new personnel, it is always good to search for the personnel to make sure they were assigned properly. If assigning a new person fails, the appropriate resolution is for the DTAS user at the APOD to research the MACOM database to determine the reason for failure. The DTAS (APOD) user will resubmit the update if necessary. If the DTAS (APOD) user is unable to resolve the error, the Mobile User will contact the MACOM Manager Help Desk for resolution.

Check On Learning Q: What are some of the required fields when adding personnel using the “Assign Personnel” function of DTAS? A: (1) Type of person being added (2) Date of Birth (3) Sex (4) Last Name (5) First Name (6) Middle Name (7) DOD Component (8) Rank (9) Operation SHOW SLIDE 127: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q: What are some of the required fields when adding personnel using the “Assign Personnel” function of DTAS? A: (1) Type of person being added (2) Date of Birth (3) Sex (4) Last Name (5) First Name (6) Middle Name (7) DOD Component (8) Rank (9) Operation SUMMARY: We have just completed Learning Activity 4, Add, Attach and Assign Personnel Using DTAS. Next, we will discuss View Mini-Record in DTAS.

View Mini-Record SHOW SLIDE 128: VIEW MINI-RECORD
NOTE: TRANSITION SLIDE

DTAS - View Mini-Record (1 of 9)
The View Mini-Record provides an abbreviated personnel record for the selected individual. For ease of use, the record is divided into five tabs: Deployment Service Basic Personal Patient Tracking SHOW SLIDE 129: DTAS - VIEW MINI-RECORD (1 of 9) a. View Mini-Record provides an abbreviated and simplified personnel record for the selected individual assigned and attached to the Mobile System. The Mini-Record is divided into five tabs: (1) Deployment (2) Service (3) Basic (4) Personal (5) Patient Tracking 129

The data displayed in the mini-record downloads to the mobile database from the Enterprise System, which receives the data from eMILPO and the Operational Data Store Enterprise (ODSE) -- for Army and Marine Corps personnel If a person is not on eMILPO or the ODSE, the data is obtained from the Defense Manpower Data Center (DMDC) Contact the Major Command Level Manager if the records do not download properly SHOW SLIDE 130: DTAS - VIEW MINI-RECORD (2 of 9) b. The data displayed in the mini-record is downloaded to the mobile database from the Enterprise System, which receives the data from eMILPO and the Operational Data Store Enterprise (ODSE) for Army and Marine Corps personnel. If a person is not on eMILPO or ODSE, the data is obtained from the Defense Manpower Data Center (DMDC). The Major Command Level Manager should be contacted if the records do not download properly. 130

Three different values could be displayed here. Differences in these values should be discernable to S-1 personnel. Select the “View Mini-Record” button. SHOW SLIDE 131: DTAS - VIEW MINI-RECORD (3 of 9) c. To view the mini-record perform the following steps from the "People Tab": (1) Highlight the name of the Soldier whose record you wish to review. (2) Click the "View Mini-Record" button. (3) DTAS will open to the default tab or the "deployment" tab if you choose to review another tab you can do so from this point or within the dialogue box. (4) Click "Close" to return to the People Tab. NOTE: Bring the students attention to the "Limited External Data Block". The next slide will discuss this more in detail.

Further Defining The Limited External Data Block Field X—Indicates that the mini-record has not been received from the Enterprise system. The Limited External Data Block displays this value, after you use the Assign Personnel or Mass Assign Personnel function to add a non-existing person to your Mobile System. N—Indicates that the mini-record has been received from the Enterprise system and that users will continue to accept values from the Enterprise external data source (when the mini-record is refreshed or updated) for the following fields: DoD Service Component and Service Component. Y—Indicates that the mini-record has been received from the Enterprise system and that users will not continue to accept values from the Enterprise external data source (when the mini-record is refreshed or updated) for the following fields: DoD Service Component and Service Component. SHOW SLIDE 132: DTAS - VIEW MINI-RECORD (4 of 9) d. This slide further defines the "Limited External Data Block Field" from the previous slide and as seen under the deployment tab. NOTE: If you use the Update Personnel function to update one of the following fields, the Limited External Data Block value will change to Y: Person Type DoD Service Component (3) Service Component NOTE: Further mini-record updates from the external data source at Enterprise will not override changes to the DoD Service Component and Service Component fields. 132

A view of the “Deployment” tab SHOW SLIDE 133: DTAS - VIEW MINI-RECORD (5 of 9) e. Deployment Tab - This tab displays information about a Soldier's deployment; such as Deployed Operation Name and Tour Status location. Briefly show elements available under this tab.

A view of the “Service” tab. SHOW SLIDE 134 : DTAS - VIEW MINI-RECORD (6 of 9) f. Service Tab - This tab displays military service-related information, including the service component, home UIC, and BASD. Briefly show elements available under this tab.

A view of the “Basic” tab. SHOW SLIDE 135: DTAS - VIEW MINI-RECORD (7 of 9) g. Basic Tab - This tab displays information such as the Soldier's name, SSN, rank, etc. Briefly show elements available under this tab. 135

A view of the “Personnel” tab. SHOW SLIDE 136: DTAS - VIEW MINI-RECORD (8 of 9) h. Personal Tab - This tab displays information such as DOB, race and blood type. Briefly show elements available under this tab. 136

A view of the “Patient Tracking” tab SHOW SLIDE 137: DTAS - VIEW MINI-RECORD (9 of 9) i. Patient Tracking Tab - This tab allows users to view hospitalization and condition information for a selected Soldier. Briefly show elements available under this tab. 137

Check On Learning Q: What is the View Mini-Record function?
A: To provide an abbreviated personnel record for the selected individual. Q: The View Mini-Record contains 5 tabs. What are they? A: Deployment, Service, Basic, Personnel, and Patient Tracking. SHOW SLIDE 138: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q: What is the View Mini-Record function? A: To provide an abbreviated personnel record for the selected individual. Q: The View Mini-Record contains 5 tabs. What are they? A: Deployment, Service, Basic, Personnel, and Patient Tracking. SUMMARY: We have just completed Learning Activity 5, View Mini-Record in DTAS. Next, we will Update Personnel and Unit Status in the DTAS Database.

Update Duty Status SHOW SLIDE 139: DTAS - UPDATE DUTY STATUS
NOTE: TRANSITION SLIDE a. The "Update Duty Status" function allows the user to update the duty status for a Soldier and to provide the reason and effective date for the change.

DTAS - Update Duty Status (1 of 6)
The Update Duty Status function allows users to update the duty status for the individual and to provide the reason and effective date for the change Users may update the duty status on one individual or a group of individuals Users have multiple methods to search for the name of the Soldier whose duty status requires an update SHOW SLIDE 140: DTAS - UPDATE DUTY STATUS (1 of 6) b. The Update Duty Status function allows the user to update the duty status for a Soldier and to provide the reason and effective date for the change. Users may update the duty status of one Soldier or a group of Soldiers. There are multiple methods to search for the name of the Soldier whose record requires updating. NOTE: DTAS does not update the duty status in eMILPO.

Present for Duty Temporary Duty In-transit Confined by Military Authorities Missing Missing Killed in Action Wounded in Action Death (other) Duty status whereabouts unknown Hospitalized (battle incurred) Hospitalized (non-battle incurred) Re-Deployed Rest and Recuperation (R&R) Convalescent Leave SHOW SLIDE 141: DTAS - UPDATE DUTY STATUS (2 of 6) c. This slide depicts types of "Duty Statuses". Refer to the Functional Guidance for a clearer understanding on all transactions within DTAS.

Select the “Update Duty Status” button. SHOW SLIDE 142: DTAS - UPDATE DUTY STATUS (3 of 6) d. Please draw your attention to those areas highlighted in yellow on this screen. To update a "Duty Status" you must: (1) Select the button at the bottom of the screen labeled "Update Duty Status. (2) Select a Soldier or group of Soldiers to whose duty status will be updated. Choose AKDINS, RYAN (3) Select the appropriate box at the top left-hand corner of the dialogue box. (4) Select "OK". 142

Complete the required fields and then select “Next”. SHOW SLIDE 143: DTAS - UPDATE DUTY STATUS (4 of 6) (5) Select the type of "Duty Status" update. Choose “HOSPITALIZED (NONBATTLE INCURRED) (6) Select the type for "Reason" of update if applicable. (7) Select "Next". 143

Complete the required fields and then select “OK”. SHOW SLIDE 144: DTAS - UPDATE DUTY STATUS (5 of 6) (8) Select the "Location". Choose “KUWAIT, KU TEST” (9) Select the "Type" if known. (10) Select "OK". 144

The Duty Status has been changed to reflect “HOS” (Hospitalized) SHOW SLIDE 145: DTAS - UPDATE DUTY STATUS (6 of 6) e. Please note that the duty status has been changed to “HOS" for HOSPITALIZED for ATKINS, RYAN. 145

Update Location SHOW SLIDE 146: DTAS - UPDATE LOCATION
NOTE: TRANSITION SLIDE

DTAS Update Location (1 of 4)
The Update Location function allows the user to update the assigned and physical locations for a selected person You may update the location on one individual or a group SHOW SLIDE 147: DTAS - UPDATE LOCATION (1 of 4) a. The "Update Location" function allows the user to update the assigned and physical location of one individual or a group of individuals.

Select the “Update Location” button, then select an individual or “Select All” to move the entire unit SHOW SLIDE 148: DTAS - UPDATE LOCATION (2 of 4) g. To update the location assignment of an individual or group one must accomplish the following: (1) Select the button entitled "Update Location". (2) Select an individual(s) or click on the "Select All" button to select all. NOTE: COL James shows presently assigned to Camp Buehring, KU 148

Complete the required fields and then select “OK”. SHOW SLIDE 149: DTAS - UPDATE LOCATION (3 of 4) (3) Under "Assigned" select the updated location. (4) Under "Physical" select the updated location. (5) Select "OK". 149

This screen shot reflects the updated has successfully processed SHOW SLIDE 78: DTAS - UPDATE LOCATION (4 of 4) h. This screen shot depicts that the update has indeed occurred. COL JAMES according to DTAS is now assigned and located physically in CAMP CHAMPION, KU. 150

Check On Learning Q: What is the “Update Location” function used for?
A: To update the assigned and physical location of one individual or a group of individuals. SHOW SLIDE 151: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q: What is the “Update Location” function used for? A: To update the assigned and physical location of one individual or a group of individuals. SUMMARY: We have just completed Learning Activity 6, Update Personnel and Unit Status in the DTAS Database. Next, we will Generate Reports from DTAS.

Generating Reports SHOW SLIDE 152: GENERATING REPORTS

DTAS - Reports Tab The “View” function allows you to view the “Army” or “Marine” view. Select this box if you wish to include sub-unit data to your report. SHOW SLIDE 153: DTAS - REPORTS TAB Learning Step/Activity 6. Generate reports from DTAS Method of Instruction: Hands-on Instructor to Student Ratio: 1:16 Time of Instruction: 10 mins a. This is the main view for the DTAS reports that may be generated by the USER. Select any report you wish to generate by selecting the "Radio Button" to the left of the report names. Let's take a moment and review a few special features. 153

DTAS Reports - Gains/Losses
You can “print” or “save” a report by selecting the appropriate icon from the menu bar. SHOW SLIDE 154: DTAS REPORTS - GAINS/LOSSES b. The Gains/Losses Report is divided into two worksheets (1) The Gains portion of the report lists personnel who have arrived in the current 24-hour reporting period as a gain to the unit. This is determined by the person's arrival date and arrival time to the unit. (2) The Losses portion of the report lists those personnel who are no longer an asset to the organization. These personnel became a non-asset during the current reporting period. NOTE: Tell the students that data elements and business rules are further defined in the functional guidance. 154

DTAS Reports – In Transit
SHOW SLIDE 155: DTAS REPORTS - IN TRANSIT c. This report provides information on personnel in transit. Additionally, you may "print" or "save" the report by selecting the appropriate icon from the menu bar. 155

DTAS Reports Personnel Status Report - PERSTAT
Embedded worksheets provide additional information SHOW SLIDE 156: DTAS REPORTS - PERSONNEL STATUS REPORT - PERSTAT d. The PERSTAT report provides a daily summary of the unit’s personnel strength by personnel status. This report is compared with the manual PERSTAT. NOTE: There are several business rules that govern the data that are reported on the PERSTAT Report. The business rules should always be referenced. Refer to Section Business Rules PERSTAT Report in the DTAS Mobile Application User Manual. 156

DTAS Reports - Unit Roster
Data elements continue to be reported beyond this screen view. Embedded worksheets provide additional information. SHOW SLIDE 157: DTAS REPORTS - UNIT ROSTER e. The Unit Roster Report comprises the overall Unit Roster. The data displayed varies depending on whether the Army or Marines view is selected. NOTE: Tell the students that with the Unit Roster Report you have an additional function available to you prior to generating the report. This function allows you to sore the data by selected category. Business rules should be referenced for more information on the data elements contained within the Unit Roster Report. 157

Check On Learning Q: The Gains portion of the report lists personnel who have arrived in the current 24-hour reporting period as a gain to the unit. How is this determined? A: This determined by the person’s arrival date and arrival time to the unit. Q: What is the additional function that is available with the Unit Roster Report prior to generating the report? A: You can sort the data by selected category. SHOW SLIDE 158: CHECK ON LEARNING NOTE: Conduct a check on learning and summarize the Learning Activity with the students before proceeding to the next Learning Activity. Q: The Gains portion of the report lists personnel who have arrived in the current 24-hour reporting period as a gain to the unit. How is this determined? A: This determined by the person’s arrival date and arrival time to the unit. Q: What is the additional function that is available with the Unit Roster Report prior to generating the report? A: You can sort the data by selected category. SUMMARY: We have just completed Learning Activity 7, Generate Reports from DTAS. Next we will View Synchronization and Identify System Deactivation for DTAS.

View Synchronization SHOW SLIDE 159: VIEW SYNCHRONIZATION

View Synchronization (1 of 4)
The View Synchronization function allows users to view system-generated messages awaiting upload to the Major Command Level Database The Synchronization Log allows the user to view the date and time of each of the user’s synchronizations SHOW SLIDE 160: DTAS - VIEW SYNCHRONIZATION (1 of 4) a. The View Synchronization feature allows users to view system generated messages awaiting upload to the Major Command Level System and a synchronization log with two tabs of Message Queue and Synchronization Log. The S-1 would view this to see what has been input into the system, to know what was received by the MACOM database, and what is still on hold. This feature works well, especially when the SIPRNET is down or the system is disconnected. NOTE: This feature is important because it is the only means for the Mobile System to receive updates from the MACOM Server. 160

Select “View Synchronization” from the Tools menu. SHOW SLIDE 161: DTAS - VIEW SYNCHRONIZATION (2 of 4) b. Select "View Synchronization" from the tools menu. 161

A view of the “Message Queue” tab. SHOW SLIDE 162: DTAS - VIEW SYNCHRONIZATION (3 of 4) c. Click on message queue tab to view message queue information. 162

DTAS - View Synchronization (4 of 4)
SHOW SLIDE 163: DTAS - VIEW SYNCHRONIZATION (4 of 4) d. Click on the “Synchronization Log” tab to view the data and time of each synchronization. 163

Email Major Command Manager
SHOW SLIDE 164: MAJOR COMMAND MANAGER NOTE: Transition Slide

(1 of 3) The “Help Menu” provides the user with the capability to contact the Major Command Manager (by ) for assistance with items such as: Synchronization issues and concerns Add location(s) to the DTAS “Locations” table Requisition of updated 6 digit grid coordinates from G-3 Improper functioning of DTAS SHOW SLIDE 165: MAJOR COMMAND MANAGER (1 of 3) a. For any problems or questions, users can utilize the help menu to contact the Major Command Level manager. Some common examples of when users may need help are when DTAS is not synchronizing properly, to add a 6-digit grid coordination location to DTAS tables, and when DTAS is not working properly. 165

(2 of 3) Select “ MACOM Manager” from the Help menu SHOW SLIDE 166: MAJOR COMMAND MANAGER (2 of 3) b. Click on the help tab and scroll down to " MACOM Manager" for assistance. 166

(3 of 3) The issue is expressed in this area and sent directly to the Major Command Manager. Or if the user prefers to contact the Major Command Manager through another option, the address is: SHOW SLIDE 167: MAJOR COMMAND MANAGER (3 of 3) c. Users are prompted by an already prepared to send their issues forward to the Major Command Manger. 167

Deactivating DTAS SHOW SLIDE 168: DEACTIVATING DTAS

DTAS – Deactivating the System
Deactivating DTAS: Executed only when directed by the Major Command Manager Resets the DTAS system Removes all existing personnel and unit files in the DTAS database SHOW SLIDE 169: DEACTIVATING THE SYSTEM NOTE: (No Hands-on) Explain to students that the Deactivate System function will remove their existing DTAS database. a. Deactivation resets DTAS and removes the existing database. Mobile System Users must coordinate deactivation with the Major Command Manager. Users must NOT deactivate until approval and permission are received from the Major Command Manager. 169

Deactivation Function (1 of 2)
Select “Deactivate System” from the Tools menu. SHOW SLIDE 170: DEACTIVATION FUNCTION (1 of 2) i. To deactivate the system select "Deactivate System" from the tools menu. 170

Deactivation Function (2 of 2)
Select “OK” to Deactivate DTAS. SHOW SLIDE 171: DEACTIVATION FUNCTION (2 of 2) j. DTAS displays the deactivate system confirmation message, and users should click "OK" to proceed with the process. This action will remove the existing database, deleting all DTAS data. Users should click "cancel" to cancel the deactivation without making any changes. 171

Check on Learning Q. What does the synchronization function allow users to view? A. This function allows users to view system generated messages awaiting upload to the Major Command Level System and a synchronization log with two tabs of message queue and synchronization log. Q. What does the Management tab allow users to do? A. The Management tab allows users to manage personal equipment issued to an individual, such as night vision goggles (NVGs) and weapons. There are additional blank columns that allow the user to store additional, unit-specific, user defined data. SHOW SLIDE 172: CHECK ON LEARNING Q: What does the synchronization function allow users to view? A: This function allows users to view system generated messages awaiting upload to the Major Command Level System and a synchronization log with two tabs of message queue and synchronization log. Q: What does the Management tab do? A: The Management tab allows a user to manage personal equipment issued to an individual, such as night vision goggles (NVGs) and weapons. There are additional blank columns that allow the user to store additional, unit-specific, user-defined data.

PRACTICAL EXERCISE SHOW SLIDE 173: PRACTICAL EXERCISE
NOTE TO INSTRUCTOR: Administer the Practical Exercise for this lesson plan. Upon completion, critique the Practical Exercise and answer any questions related to the Practical exercise.

Terminal Learning Objective
Action: Manage the Deployed Theater Accountability System (DTAS) Conditions: In a classroom environment, with internet connectivity and the DTAS training application loaded, DTAS Functional Guidance (current version), AHRS DTAS Dashboard User’s Guide (current version), DTAS Mobile Application User Manual (current version), and Applicable HR Field Manuals and References. Standard: Students will meet the standard of 70% accuracy when they: 1. Identify the objectives of DTAS 2. Identify the three sub-systems of DTAS 3. Identify S-1 DTAS responsibilities and planning considerations 4. Employ the DTAS Mobile system 5. Manage the DTAS APOD module 6. Manage the DTAS Dashboard function 7. Manage the DTAS Major Command Level module SHOW SLIDE 174: TERMINAL LEARNING OBJECTIVE NOTE: Read and discuss the TLO with the students. NOTE: Checks on Learning are distributed throughout the Lesson Plan.

Manage the Deployed Theater Accountability System (DTAS) October 2015

Similar presentations

Presentation on theme: "Manage the Deployed Theater Accountability System (DTAS) October 2015"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Manage the Deployed Theater Accountability System (DTAS) October 2015

Similar presentations

Presentation on theme: "Manage the Deployed Theater Accountability System (DTAS) October 2015"— Presentation transcript:

Similar presentations

About project

Feedback