1. Manage Personnel Strength Data
Adjutant General School
Captain Career Course
Manage Personnel Strength Data
December 2014 1

2. Terminal Learning Objective
Action: Manage Personnel Strength Data
Condition: Given access to Human Resource enabling systems, FM 1-0, and an awareness of Operational Environment (OE) variables and actors.
Standards: Students will meet the standard by scoring 80% or higher on a knowledge-based performance test including the following learning activities:
Define Strength Reporting principles
Correlate Strength Reporting doctrinal responsibilities at each echelon of command
Identify Strength Reporting formats
Identify Strength Reporting HR Enabling Systems
Show Slide 2 : Terminal Learning Objective
NOTE: Inform the students of the Terminal Learning Objective requirements. 2

3. Army Universal Task List (AUTL)
Provide Human Resources Support
Slide 3: Army Universal Task List (AUTL)
Personnel Accountability and Strength Reporting and the other three Man The Force Key Functions are aligned under Man the Force Core Competency in the Army Universal Task List (AUTL). Accurate strength reporting process is critical in order to reflect the combat power of a unit and is also used to monitor unit strength, prioritize replacements, execute strength distribution, and make tactical and HR support decisions.
NOTE: Discuss with students how SR impacts the personnel replacement/unit reset process. 3

4. Human Resources (HR) Support
SHOW SLIDE 4: HUMAN RESOURCES (HR) SUPPORT
HR units and staffs perform the core competencies and key functions at theater-level and below. Not all HR key functions are executed at each level of command. For example, personnel accountability is conducted at the S-1 level and monitored at division and above levels. However, Strength Reporting is conducted at every level. Commanders and HR leaders should use FM 1-0 and the Army Universal Task List (AUTL) as a reference tool for developing general mission essential task lists, core capabilities mission essential tasks, operational orders, and SOPs. 4

5. Strength Reporting
FM 1-0: Strength Reporting is the numerical end product of the accountability process by comparing by-name data (faces) against authorizations (spaces) to determine a percentage of fill.
Strength Reporting includes reporting all personnel who deploy with the force including:
Numerical Strength Reports reflect the combat power of a unit and are used to:
Soldiers
Military service members from other Services
Department of Defense (DoD) Civilians
Contractors
Monitor unit strength
Prioritize replacements
Make and support tactical decisions
Show Slide 5: STRENGTH REPORTING
Personnel strength reporting is a numerical end product of the accountability process. It is achieved by comparing the by-name data obtained during the personnel accountability process (faces) against specified authorizations (spaces or in some cases requirements) to determine a percentage of fill. Strength data reflects a unit’s authorization and required base-line strength. It starts with strength-related data submitted at unit level and ends with an updated database visible at all echelons, to include HRC. Personnel strength reporting is a command function conducted by G-1/AGs and S-1s to enable them to analyze manning levels and readiness, which provide a method of measuring the effectiveness of combat power. As strength reports may impact tactical decisions, the timely and correct duty status of individuals are critical to the strength reporting process.
Personnel strength reporting includes reporting all personnel who deploy with the force. This includes Soldiers, military Servicemembers from other Services, DoD civilians, and contractors.
Personnel accountability is the key factor used for conducting strength reporting.
NOTE: Ask the students how SR can affect the commander’s decisions and the unit’s mission. Encourage students to share real-world experiences that will help clarify these definitions.
Personnel Accountability is the key factor used for conducting Strength Reporting
FM 1-0, Chapter 3 5

6. Strength Reporting Process
Show Slide 6: STRENGTH REPORTING Process
The strength reporting process begins by unit S-1s processing strength related transactions into various HR automated systems that update the HR common operational picture at all levels and ends with the production of a PERSTAT report (JPERSTAT in a Joint environment). This report can be either manual or automated. Greater accuracy in the strength reporting process can be gained by generating reports from automated systems that perform personnel accountability functions. These automated reports reduce error by treating each entry as a record versus a data element that requires separate update. Additionally, automated processing is capable of simultaneous versus sequential reporting, which provides greater responsiveness to HR providers and their commanders.
The strength reporting process provides commanders with a snapshot of the personnel component of their combat power and capabilities. Every level of command develops their requirements for data elements reflected on the strength report. At a minimum, commands should report strengths by unit, location, component, category (military, DoD civilian, contractor, etc.), and duty status. Internally, commanders may use additional data elements that provide a better snapshot of actual capabilities by weapon system, cohort (officer/warrant/enlisted), MOS additional specialties, language ratings, etc. Unit G-1/AGs and S-1s should develop strength reports that best represent the personnel component of combat power for their organizations. Within a deployed theater, the ASCC G-1/AG will establish PERSTAT reporting requirements for unit strengths to include required “as of” times. If operating in a Joint environment, the PERSTAT should require the same data elements as the JPERSTAT. 6

7. Key Terminology FMS WEB (1 of 2)
Required Strength - Unit wartime requirements, which can normally be found on a unit’s MTOE or an RC unit’s mobilization/deployment order; normally the same as authorized strength given recent Army leadership guidance.
Authorized Strength - Unit peacetime requirements; the number against which personnel assignments are made and can normally be found on a unit’s MTOE or an RC unit’s mobilization/deployment order, may be directed by PMAD.
Operating Strength - Soldiers who are available to deploy as compared to authorizations. This relates to available strength on the USR and does not include Soldiers who are non-deployable or not available.
Force Management System
FMS WEB
Show Slide 7: key Terminology (1 of 2)
Required Strength - Unit wartime requirements, which can normally be found on a unit’s MTOE or an RC unit’s mobilization/deployment order; normally the same as authorized strength given recent Army leadership guidance.
Authorized Strength - Unit peacetime requirements; the number against which personnel assignments are made and can normally be found on a unit’s MTOE or an RC unit’s mobilization/deployment order, may be directed by PMAD.
Operating Strength - Soldiers who are available to deploy as compared to authorizations. This relates to available strength on the USR and does not include Soldiers who are non-deployable or not available.
FMSWeb. Authorization Documents for all Army organizations are available on the Force Management System ( S-1s can request access and run various reports detailing their unit’s authorization information. The mission of the United States Army Force Management Support Agency (USAFMSA) is to:
Document all Army force structure to include manpower and equipment requirements and authorizations using an integrated process.
Provide support, analysis, and discipline for Army's (personnel, materiel, resource and force managers) plans and decisions.
Support leadership decisions to transform and shape the Army.
FMSWeb documents include TDA/TOE/MTOE/CTA/JTA. 7

8. Key Terminology
(2 of 2)
Assigned: To place units or personnel in an organization where such an organization controls and administers the units or personnel for the primary function in a permanent nature. Unless specifically stated, this includes administrative control (ADCON) (Parent Unit is responsible for PA and SR)
Attached: The placement of units or personnel in an organization where such placement is relatively temporary (Gaining Unit is responsible for PA and SR)
Operational Control (OPCON): Transferable command authority for a specific mission; temporary; not normally logistically or administratively supported (Parent Unit is responsible for PA and SR)
Tactical Control (TACON): Unit falls under a commander’s command authority for a specific mission; temporary; not logistically or administratively supported. (Parent Unit is responsible for PA and SR)
Administrative Control (ADCON): includes personnel management, control of resources and equipment, discipline, and other matters not included in operational missions. For OPCON and TACON, parent units retain ADCON.
Show Slide 8: key Terminology (2 of 2)
NOTE: Inform students that the next four terms are command relationships as defined by FM It is important that S-1s understand the these terms and the relationships of their units in order to understand their PASR responsibilities. Discuss with the students the impact of each of these relationships as it relates to Task Organization. The S-1 needs to insure that, as the S-3 considers command relationships during the planning and orders process, they understands the impact on support relationships.
Assigned: To place units or personnel on orders in an organization where such placement is relatively permanent, and/or where such organization controls and administers the units or personnel for the primary function of the unit or personnel. Unless specifically stated, this includes administrative control (ADCON). This means the unit or personnel are fully “owned” by the gaining organization to include strength reporting, awards, postal, casualty support, supply, transportation, etc. Also, includes less obvious areas like evaluations, contact with rear detachments, R&R planning, etc.
Attached: The placement of units or personnel in an organization where such placement is relatively temporary. A unit that is temporarily placed into an organization is attached.
Operational Control (OPCON): Transferable command authority for a specific operational mission, Operational control may be delegated and is the authority to perform those functions of command over subordinate forces involving organizing and employing commands and forces, assigning tasks, designating objectives, and giving authoritative direction necessary to accomplish the mission. Operational control does not, in and of itself, include authoritative direction for logistics or matters of administration, discipline, internal organization, or unit training (JP 1-02). This command relationship has the least impact on HR operations. Generally, this control is related to a specific mission with a short duration timeline. HR personnel will normally be expected to monitor the units’ personnel status; but, not take direct action to influence it.
Tactical Control (TACON): command authority over military capability or forces made available for tasking, that is limited to the detailed and, usually, local direction and control of movements or maneuvers necessary to accomplish missions or tasks assigned. Tactical control is inherent in operational control. Tactical control allows commanders below combatant command level to apply force and direct tactical use of logistic assets but does not provide authority to change organizational structure or direct administrative and logistic support.
Administrative control (ADCON): When commanders establish command relationships they determine if the command relationship includes ADCON. Administrative control is direction or exercise of authority over subordinate or other organizations in respect to administration and support, including 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 the operational missions of the subordinate or other organizations (JP 1-02). ADCON of an Army unit must remain in Army channels. It cannot be transferred to a unit of another service. ADCON is inherent in Assigned status and can be part of Attached status depending on how the orders are worded. It is possible to have units or personnel in an Attached status “minus ADCON” that would have their ADCON retained by their parent or losing unit. NOTE: ADCON is not a command relationship.
NOTE: Ask students where they would find their units command relationships (Task Org in OPORD). Discuss with students that assigned and attached Soldiers should be annotated on the unit’s accountability systems (eMILPO AAA-162 report and DTAS) 8

9. Command Relationships
Show Slide 9: Command Relationships
Command relationships will determine who is responsible for a unit’s personnel accounting and strength reporting. Normally, this will align with the unit they receive sustainment support (CSS) from. These relationships can change frequently with in an operation and HR personnel must stay current with changes to the unit’s task force organization. To ensure SR remains timely and accurate, units must clearly understand their role, the effective date/time groups for task organization changes and “as of” data reflected in SR reports. Close coordination must be made during changes in task organization to ensure personnel are not double counted by gaining and losing command or are not accounted for at all. Double counting of units the day of a change in task organization is the most common discrepancy with SR numerical reporting.
NOTE: Discuss example scenarios of changes in command relationships and ask students if they would account for and report individuals and units. Task Organization can get ‘creative’ with unit’s being ‘attached minus ADCON’. Discuss what this means for SR and responsibility of updating databases to reflect these relationships.
Command relationships establish the degree of control and responsibility commanders have for forces operating under their control.
FM 5-0, Appendix F1 9

10. Battalion S-1 Doctrinal Responsibilities
Collect, summarize, analyze, update, and report personnel strength information.
Perform error reconciliation between the manual PERSTAT and DTAS.
Process information on replacements, RTD Soldiers, Army civilians, and multinational personnel, as required.
Submit personnel status reports (i.e., PERSTAT/JPERSTAT).
Submit PERSUMs and PRRs by unit SOPs or established procedures from higher HQs.
Coordinate with appropriate agencies for information on casualties, patient tracking, and stragglers and update the database as appropriate.
Coordinate for connectivity for secure and non-secure voice and data systems with the battalion S-6 and brigade S-1, where appropriate.
Ensure deploying members of the PR TM have been granted clearances and accesses to the appropriate HR systems.
Provide copies of flight or sea manifests to the appropriate PAT at the port of debarkation and maintain copy at unit-level.
SHOW SLIDE 10: BATTALION S-1 RESPONSIBILITIES
Collect, summarize, analyze, update, and report personnel strength information, using secure or non-secure data systems in the directed format with the proper enabling HR system.
Perform error reconciliation between the manual PERSTAT and DTAS when required.
Process information on replacements, RTD Soldiers, Army civilians, and multinational personnel, as required.
Submit personnel status reports (i.e., PERSTAT/JPERSTAT) to the brigade S-1.
Submit PERSUMs and PRRs by unit SOPs or established procedures from higher HQs.
Coordinate with appropriate agencies for information on casualties, patient tracking, and stragglers and update the database as appropriate.
Coordinate for connectivity for secure and non-secure voice and data systems with the battalion S-6 and brigade S-1, where appropriate.
Ensure deploying members of the PR TM have been granted clearances and accesses to the appropriate HR systems.
FM 1-0, para 3-73 10

11. Brigade/STB S-1 Doctrinal Responsibilities
Collect, summarize, analyze, update, and report personnel strength information to G-1/AG or higher HQs.
Monitor duty status change information and update the personnel database and HR management systems.
Process information on replacements, RTD Soldiers, Army civilians, multinational personnel, as required .
Perform error reconciliation and correct deviations in strength between eMILPO/RLAS/SIDPERS and TAPDB and between DTAS and the manual PERSTAT.
Update DTAS daily.
Submit PERSUMs and PRRs when required by higher headquarters.
Coordinate with the Rear Detachment, appropriate staff sections, and external agencies for information on casualties, patient tracking, and stragglers and ensure battalion S-1s update the database.
Plan and coordinate for connectivity for secure and non-secure data systems.
On order or in support of, operate a manifesting cell at ports of embarkation, collect manifest data at ports of debarkation and enter those personnel into the theater database.
SHOW SLIDE 11: BRIGADE/STB S-1 RESPONSIBILITIES
Collect, summarize, analyze, update, and report personnel strength information to G-1/AG or higher HQs.
Monitor duty status change information (i.e., Present for Duty, WIA, KIA, MIA) and update the personnel database and HR management systems.
Process information on replacements, RTD Soldiers, Army civilians, multinational personnel, as required.
Perform error reconciliation and correct deviations in strength between eMILPO/RLAS/SIDPERS and TAPDB and between DTAS and the manual PERSTAT.
Update DTAS daily.
Submit personnel status reports (i.e., PERSTAT/JPERSTAT) to higher HQs.
Submit PERSUMs and PRRs when required by higher headquarters.
Coordinate with the Rear Detachment, appropriate staff sections, and external agencies for information on casualties, patient tracking, and stragglers and ensure battalion S-1s update the database.
Plan and coordinate for connectivity for secure and non-secure data systems, as well as access to secure voice communications systems.
On order or in support of, operate a manifesting cell at ports of embarkation, collect manifest data at ports of debarkation and enter those personnel into the theater database.
FM 1-0, para 3-72 11

12. Corps/Division G-1/AG Doctrinal Responsibilities
Perform ASCC personnel strength reporting responsibilities when serving as the Army Force.
Establish and enforce strength reporting requirements for subordinate units.
Notify subordinate G-1/AGs and S-1s of all pending and potential task organization changes.
Ensure reports reflect the latest task organization.
Consolidate/submit PERSTATs, PERSUMs, and PRRs, as required.
Coordinate with the HRSC, if necessary, to establish an automated personnel accountability system that aligns assigned and attached element UICs with supporting S-1s.
Ensure arriving battalions and separate units provide copies of their flight/sea manifests to the appropriate PAT at the port of debarkation.
Conduct personnel strength reporting quality control checks.
Coordinate with the G-3 for replacement priorities.
SHOW SLIDE 12: CORPS/DIVISION RESPONSIBILITIES
Perform ASCC personnel strength reporting responsibilities when serving as the Army Force.
Establish and enforce strength reporting requirements for subordinate units.
Notify subordinate G-1/AGs and S-1s of all pending and potential task organization changes.
Ensure reports reflect the latest task organization.
Consolidate/submit PERSTATs, PERSUMs, and PRRs, as required.
Coordinate with the HRSC, if necessary, to establish an automated personnel accountability system that aligns assigned and attached element UICs with supporting S-1s.
Ensure arriving battalions and separate units provide copies of their flight/sea manifests to the appropriate PAT at the port of debarkation.
Conduct personnel strength reporting quality control checks.
Coordinate with the G-3 for replacement priorities.
FM 1-0, para 3-71 12

13. ASCC G-1/AG Doctrinal Responsibilities
Establish personnel strength reporting plans and policies in coordination with the JTF/JFLCC/CFLCC J-1
Manage and maintain ASCC personnel strength reporting information; monitor DTAS
Prepare and maintain PERSTAT / JPERSTAT / PERSUM / PRR reports
Direct a PAI for any subordinate unit when the unit’s strength imbalance between DTAS and the daily PERSTAT exceeds theater policy
Establish connectivity with HRC, RC Personnel Offices, Rear Detachments (as required), appropriate Joint HQ/other Services/federal agencies, and CRC
Monitor, analyze, and validate unit strengths to determine personnel requirements/priorities
Predict and validate personnel requirements based on current strength levels, projected gains, estimated losses, and the projected number of Soldiers and Army civilians RTD
Recommend replacement priorities to the G-3 (if replacement shelves are created)
Develop theater personnel distribution plans and manage the theater replacement system (if replacement and casualty shelves are used).
Conduct reassignments to meet operational requirements (coordinate with subordinate G-1/AG, S-1, and HRC).
SHOW SLIDE 13: ASCC G-1 RESPONSIBILITIES
Establish personnel strength reporting plans and policies reflecting detailed reporting procedures, timelines, formats and responsibilities (who reports to whom), in coordination with the JTF/JFLCC/CFLCC J-1.
Manage and maintain ASCC personnel strength reporting information.
Prepare and maintain PERSTAT / JPERSTAT reports.
Monitor DTAS to obtain strength reporting information.
Direct a PAI for any subordinate unit when the unit’s strength imbalance between DTAS and the daily PERSTAT exceeds theater policy.
Establish connectivity with HRC, RC Personnel Offices, Rear Detachments (as required), appropriate Joint HQ/other Services/federal agencies, and CRC.
Monitor, analyze, and validate unit strengths to determine personnel requirements and priorities.
Prepare and maintain PERSUMs and PRRs.
Predict and validate personnel requirements based on current strength levels, projected gains, estimated losses, and the projected number of Soldiers and Army civilians RTD.
Recommend replacement priorities to the G-3 (if replacement shelves are created).
Develop theater personnel distribution plans and manage the theater replacement system (if replacement and casualty shelves are used).
Conduct reassignments to meet operational requirements (coordinate with subordinate G-1/AG, S-1, and HRC).
FM 1-0, para 3-70 13

14. Manual Reporting
Manual reports are used in the event automated systems are not available or periodically to support commander’s requirements
Manual reports required for OPCON/TACON units
Reports flow from subordinate units, are rolled up, and then reported higher
S-1s must reconcile manual reports with automated systems
Examples of standard manual reports are:
Personnel Summary (PERSUM)
Personnel Requirements Report (PRR)
Joint Personnel Status Report (JPERSTAT)
Personnel Status Report (PERSTAT)
Rear Detachment and Personnel Availability Report
Show Slide 14: Manual Reporting
Battalion and Brigade S-1 sections submit by-name strength-related transactions via eMILPO which are visible at all levels up to HQDA. The Army also has an automated personnel accountability software package for use in a deployed theater. In the event the automated system is not available, especially during the initial phase of an operation, manual reports become the primary reporting method. Manual reports are the primary method for reporting situational awareness for OPCON/TACON units; official accounting and reporting via JPERSTAT and DTAS are conducted by parent unit. Examples of standard manual reports include: Personnel Summary (PERSUM), Personnel Requirements Report (PRR), Joint Personnel Status (PERSTAT), Personnel Status (PERSTAT).
NOTE: Explain to the students that reporting is required both manually via the JPERSTAT, and in automated system, DTAS, daily in theater. Unit must reconcile numbers reported in DTAS with the numbers they report on the JPERSTAT. 14

15. Personnel Summary (PERSUM)
Displays a unit’s personnel strength in aggregate numbers, as of
a given time; used to assess combat power and set priorities.
Show Slide 15: Personnel Summary (PERSUM)
This report displays a unit’s personnel strength in aggregate numbers, as of a given time. It reports strength by personnel category (officer, warrant, enlisted, and civilian), gains, losses, and duty status changes since the last report. Unit SOPs will determine report format and reporting times. Reports from subordinate units are rolled up and reported higher. Commanders and personnel readiness managers use the report to assess organizational combat power and set priorities.
NOTE: This format is provided as an Example only.
FM 1-0, para 3-67 15

16. Personnel Requirements Report (PRR)
Displays a unit’s personnel replacement requirements by grade/MOS; based on comparison of authorized vs. strength
Show Slide 16: Personnel Requirements Report (PRR)
Human resource managers report personnel requirements through a personnel requirements report. This report lists a unit’s personnel replacement requirements by grade/MOS based on a comparison of authorized versus assigned strength. The PRR is primarily used to manage replacement operations. Unit SOPs will determine report format and reporting times.
FM 1-0, para 3-67 16

17. JPERSTAT
(1 of 2)
Provides an assigned and available strength count, and captures gains and losses since the last reporting period
Used in Joint Environment
Reports Military, Civilian and Coalition personnel physically present in the theater by unit and location
Numbers must reconcile with DTAS
Show Slide 17: JPERSTAT (1 of 2)
The Joint Personnel Status Report or JPERSTAT gives the unit and the commander a strength summary. It provides an assigned and available strength count, and captures gains and losses since the last reporting period. Data is broken down by unit and deployed installation and includes Army Soldiers of all components, DOD civilians and contractors, allied, multi-national and joint personnel in theater. Soldiers on leave, TDY, emergency leave, etc. in CONUS are not included on the JPERSTAT.
(1) The J-1 must develop and publish the JPERSTAT format and enforce its use. The unit’s PERSTAT should be in exactly the same format as the final theater JPERSTAT product.
(2) The unit’s numbers on the JPERSTAT must match the unit’s numbers in the Deployed Theater Data Base (DTAS). Army planners rely on theater database to make operational decisions, budgeting requirements, AAFES, MWR and intra-theater pass program planning and executions.
NOTE: Explain that the JPERSTAT in theater may look a little different, but that they have the same basic elements. Discuss with students each element of the JPERSTAT (civilian and coalition example on next slide).
JP 1-02, III-3 17

18. Civilians and Coalition
JPERSTAT
(2 of 2)
Civilians and Coalition
Show Slide 18: (J) PERSTAT (2 of 2)
S-1s are also required to report civilian and coalition partners that are assigned or attached to their unit. This is usually done on a separate spreadsheet of the JPERSTAT than the U.S. military personnel. These personnel can be challenging to account for and coordination must be made to insure they are not being double counted or not accounted for at all. 18

19. PERSTAT Example 1 Show Slide 19: PERSTAT Example 1
The Personnel Status Report or PERSTAT gives the unit and the Army commander a strength summary. FM 1-0 recommends that the Army unit’s PERSTAT be in exactly the same format as the final theater JPERSTAT product. Unit SOPs may have different formats in order to provide the commander the information they need to make decisions. This may be an example of a BDE’s PERSTAT after arriving in theater and preparing to send personnel on Environmental leave (EML). 19

20. PERSTAT Example 2 Show Slide 20: PERSTAT Example 2
This PERSTAT example is for a unit preparing to redeploy. The commander wanted a status report on the accountability of personnel as they flowed from theater (CLN) to CONUS. 20

21. PERSTAT Example 3 OPCON / TACON Units Operating Strength
Show Slide 21: PERSTAT Example 3
To prevent double counting, units do not report personnel strength on their OPCON and TACON units to higher HQs. Those reports are made by the parent unit. However commanders may require a status report of those units’ operation strength in order for the commander to make tactical decisions. This is an example of a unit’s strength report for those OPCON/TACON units. 21

22. Rear Detachment Report
Show Slide 22: Rear Detachment Report
NOTE: A Soldier is carried as non-deployable on the Rear Detachment Report if for any reason they will not deploy with the unit.
The Rear Detachment provides HQDA with a comprehensive view of the major combat units. Major combat unit is defined as a BCT, Division headquarters, and combat Aviation BDE from the active component, the U.S. Army Reserves and Army National Guard. The report is submitted monthly once BCTs reach their LAD-180 and then weekly at LAD-90 until deployment Other units may be required to also submit this report as designated by the senior leaders of the Army. The report provides an update of the following categories:
Total number of Soldiers deployed
Number of Soldiers assigned as rear detachment cadre
Number of Soldiers that are Non-Deployable. There are 24 categories in the RD Report with the majority aligning to specific categories in the Unit Status Report. There are 8 (eight) additional categories that are included in the Rear Detachment Report that are not included in the USR: Emergency LV, School, Dwell (Dependent Limiting Tours), Deployment Dwell, TSIRT/IRT, Available Not Deploying (Commander’s Discretion), Rear Detachment Cadre and Not Scheduled for Deployment or Redeployed at End of Unit Mission
Number of Soldiers ready to fly with a flight scheduled
(5) Number of Soldiers ready to fly without a flight scheduled
The number of Soldiers in these categories should equal the total number of Soldiers assigned to the unit. Units will annotate the next scheduled flights and total number of pax at the bottom of the spreadsheet.
19 Jun 2010 22

23. Battlefield Flow 23 Slide 23: Battlefield Flow
Prior to arriving in theater, the ASCC G-1/AG or Army Force G-1/AG establishes theater policy for personnel strength reporting to include reporting standards and timelines. Coordination with the G-6 is necessary to ensure access to NIPRNET and SIPRNET is established for required HR databases and automated systems. During initial entry, strength managers must be prepared to operate with limited or no connectivity.
The early entry element of the HRSC establishes the DTAS and initiates database hierarchy management.
The TG PAT, supported by an HR Company, establishes theater personnel accountability operations at theater reception points (APOD/SPOD).
The TG PAT ensures all personnel and units arriving in theater are accurately entered into DTAS. For units, the S-1 normally provides a copy of their unit’s database which the TG PAT then uploads into DTAS.
The HR Company establishes PATs at designated locations to maintain accountability and tracking of personnel as they transit the theater of operations.
CLTs are established at the APOD and at other designated locations.
All arriving personnel (Soldiers, civilians and contractors) and units must be accurately entered in the system to ensure accurate personnel strength reporting throughout the duration of the theater-level operation. As units and individuals arrive in theater, the PAT, which directly impacts the effectiveness of deployed personnel strength reporting operations, records their arrival in theater.
HR PAT elements capture and record data into DTAS information on Soldiers and units who can be tracked as they enter, transit, and depart the theater. PATs are only located at locations where the personnel flow equals 600 or more per day. S-1 sections complement this system by performing personnel accountability tasks within their elements for small-scale movements conducted within the brigade AO and in movement to the intra-theater APOD where no HR organization assets are assigned.
NOTE: Figure depicts the information flow for both automated and manual personnel accountability reporting. 23

24. Strength Reporting HR Enabling Systems
Tactical Personnel System (TPS)
Deployed Theater Accountability System (DTAS)
Electronic Military Personnel Office (eMILPO)
Show Slide 24: Personnel Accountability HR Enabling Systems
NOTE: Explain to the students that this portion of the lesson will be a general overview of the systems that support PA and in subsequent lessons that will receive more in-depth, hands-on training on each of the enabling systems.
There are several HR enabling systems that assist Brigade S-1s in the performing accurate and timely personnel accountability, if the systems are used properly. The critical enabling systems for personnel accountability include:
Tactical Personnel System (TPS)
(2) Deployed Theater Accountability System (DTAS)
(3) Electronic Military Personnel Office (eMILPO) 24

25. Tactical Personnel System (TPS)
(1 of 3)
Serves as a deployment manifesting platform for all military personnel (Joint capable), DOD civilians, and contractors
Supports a commander's tactical decision-making process by creating a mobile, stand alone deployed personnel strength automated file.
Can performing functions of Manifest, Jump Manifest, System Administration, Personnel, Task Force Operations, Crew Status, Ad hoc Query, and UIC Authorizations
Show Slide 25: Tactical Personnel System (1 of 3)
The Tactical Personnel System’s (TPS) primary use today is manifest and account for personnel during deployment. It allows for immediate human resource monitoring during deployment and reception by the receiving theater. Standardized reports created by TPS facilitate the creation of a deployed force database for the theater commander.
(1) TPS supports a commander's tactical decision-making process by creating a mobile "go to war" personnel strength automated file. TPS is a hasty field system, which does not replace eMILPO/DTAS, but enhances the commander’s ability to account for personnel in theater. This tool can assist an S-1 in conducting daily status reports, while keeping track of those moving in and out of country. This largest selling point of this S-1 Tool is that it is a stand alone that does not require Internet connectivity.
(2) TPS performs functions of Manifest, Jump Manifest, System Administration, Personnel, Task Force Operations, Crew Status, Adhoc Query, and Unit Identification Code (UIC) Authorizations.
(3) TPS creates and monitors personnel by task force organizations, provides duty status monitoring of deployed personnel, and is mobile, which maximizes personnel accountability for the tactical commander during "split-base" or other operations. 25

26. Tactical Personnel System (TPS)
(2 of 3)
Show Slide 26: TACTICAL PERSONNEL SYSTEM (2 of 3)
TPS uses a barcode scanner that reads each deploying Soldier’s CAC card and uploads them into the manifest. Each manifest (chalk) that has been captured of arriving and departing Soldiers can be viewed on the screen. The manifest detail screen shows the individual Soldiers listed on each manifest. 26

27. Tactical Personnel System (TPS)
(3 of 3)
(1 of 3)
(1 of 3)
Show Slide 27: TACTICAL PERSONNE SYSTEM (TPS) (3 OF 3)
TPS captures all the manifesting of Soldiers, civilians and contractors at their departing station (during deployment and redeployment) and is digitally uploaded into DTAS (Deployed Theater Accountability Software). When the TPS manifest is finalized at the departure site, the disk is taken forward and given to the S-1 upon arrival. This file can be ed or carried by disk to higher echelons to build on the deployed database to have total accountability down to the individual Soldier. The information will be displayed both on DTAS and the individual TPS system at the unit S-1.
NOTE: Direct students to their desktop icons on their laptops and to open the TPS icon to take a look at it. 27

28. Check on Learning Q: What functions does TPS perform?
A: TPS performs functions of Manifest, Jump Manifest, System Administration, Personnel, Task Force Operations, Crew Status, Adhoc Query, and Unit Identification Code (UIC) Authorizations
Q. Who does TPS capture during manifesting at their departing station (during deployment and redeployment)?
A. TPS captures all the manifesting of Soldiers, civilians and contractors
Q. What is used to read each deploying Soldier’s CAC card and uploads them into the manifest?
A. TPS uses a barcode scanner.
SHOW SLIDE 28: CHECK ON LEARNING
NOTE: Provide the following correct answers:
Q: What Functions does TPS perform?
A: TPS performs functions of Manifest, Jump Manifest, System Administration, Personnel, Task Force Operations, Crew Status, Adhoc Query, and Unit Identification Code (UIC) Authorizations
Q. Who does the TPS manifest capture?
A. TPS captures all the manifesting of Soldiers, civilians and contractors at their departing station (during deployment and redeployment).
Q. What does TPS use that reads each deploying Soldier’s CAC card and uploads them into the manifest?
A. TPS uses a barcode scanner.
NOTE: Summary: During this learning activity we discussed the TPS which is also apart of the
Strength Reporting HR Enabling Systems.
NOTE: Inform the students that they will be given a PE on DTAS and upon completion and
review of the PE they will be given a final test on Prepare Unit Personnel Strength Data that
encompass all activities discussed during this lesson. 28

29. Deployed Theater System (DTAS)
Database of record for accountability (boots on ground) in the deployed theater of operations (DEPLOYED STRENGTH)
Provides near real-time visibility and accountability for military and civilian personnel
Tracks and reports of the duty status of all deployed personnel by name (SSN), unit, location, and date
Web enabled application via SIPRNET
Show Slide 29: DEPLOYED THEATER ACCOUNTING SYSTEM
Deployed Theater Accountability Software (DTAS) is the database of record for accountability in the deployed theater of operations. It is the ‘boots on ground’ or ‘BOG’ strength, or deployed strength, for all military and civilian personnel, to include: Army personnel, joint service members, DOD civilians, and contractors. It provides commanders with a standardized database for near real-time visibility of the duty status of all deployed personnel by name (SSN), unit, location, and date. It is a web enabled software application accessible worldwide via physical connection to the Secret Internet Protocol Router Network (SIPRNET) or by mobile computers.
NOTE: Direct students to their desktop icons on their laptop and open the DTAS icon to take a look.
NOTE: Inform students that if they use the DTAS training database on a computer with Windows VISTA, they will not be able to pull up this report. 29

30. GENERATING DTAS REPORTS
SHOW SLIDE 30: GENERATING DTAS REPORTS
NOTE: Transition Slide 30

31. Utilizing DTAS – Mobile System Level
Show Slide 31: Utilizing Dtas – Mobile System level
The DTAS System operates on a secure network (SIPRNET), but is capable of operating disconnected from the network. The DTAS is comprised of three distinct sub-systems:
(1) Mobile System level (User level)
 (2) Major Command level (formerly called the “Theater” level)
 (3) Enterprise System level
NOTE: Inform the students that during this block of instruction they will be utilize the Mobile System level (User Level)
DTAS shows the UIC hierarchy for all UICs within the unit and displays all names in the unit. By highlighting one of the subordinate unit UICs, DTAS will display only the names for that subordinate unit. S-1s should insure the number of names displayed matches the numbers reported on the PERSTAT/JPERSTAT. 31

32. 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 in your report.
SHOW SLIDE 32: DTAS - REPORTS TAB
NOTE: Direct the students to click on the Reports Tab on the DTAS Menu and select UIC WATGA0.
This is the main view for the DTAS reports that are generated by the USER. The following reports are generated by selecting the "Radio Button" to the left of the report names.
Gains/Losses
In-Transit
PERSTAT
Unit Roster
NOTE: Inform the students that they will now have a brief overview of these reports. They should have received a more detailed class, with hands-on instruction, during the Employ/Manage DTAS lesson. 32

33. DTAS Reports - Gains/Losses
SHOW SLIDE 33: DTAS REPORTS - GAINS/LOSSES
The Gains/Losses report displays those personnel who have either arrived or departed the UIC/DUIC or were an operational loss to the organization during the 72-hour reporting period.
(1) The report consist of two parts – Gains and Losses. Each are presented as separate worksheets in Microsoft Excel.
(a) The Gains portion of the report lists personnel who have arrived in the current reporting period as a gain to the unit. This is determined by the person's arrival date and time to the unit.
(b) 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.
(2) The report presents data from the 72-hour period preceding the time the user generates the report.
NOTE: Data elements and business rules are further defined in the functional guidance.
You can “print” or “save” a report by selecting the appropriate icon from the menu bar. 33

34. DTAS Reports – In Transit
SHOW SLIDE 34: DTAS REPORTS - IN TRANSIT
The In Transit report displays data on those personnel who are in transit from the UIC/DUIC for any reason. This report allows the unit to track an individual throughout a movement out of theater or to another unit.
Personnel will remain on the In Transit report until a duty status change is submitted.
(2) A person may be in transit for any of the following reasons.
Convalescent Leave
Emergency Leave
Local Reassignment
Mission Complete
Rest and Recuperation (R&R Leave)
Temporary Duty (TDY)
Relieved from Attached (RATH)
NOTE: Inform the students that this report not only shows who has moved, but also should prompt a location change transaction. Major Command managers are tracking individuals who are in a TRA status, and if not timely updated, will raise a flag.
NOTE: Inform the students that they can "print" or "save" the report by selecting the appropriate icon from the menu bar. 34

35. DTAS Reports Personnel Status Report – PERSTAT (1 of 2)
Embedded worksheets provide additional information.
SHOW SLIDE 35: DTAS REPORTS - PERSONNEL STATUS REPORT – PERSTAT (1 of 2)
The PERSTAT report gives the user and the commander a strength summary. It provides an assigned and available strength count and captures gains and losses for the last 24 hour period.
(1) The PERSTAT is populated by the Assign Personnel, Attach Personnel, and Update Duty Status functions in the Mobile System. If the user does not assign personnel, attach personnel, or enter duty status changes in a timely manner, the PERSTAT will not reflect an accurate picture of the unit strength to the Mobile System User or the higher command.
(2) The PERSTAT is broken down into subsections or tabs that provide various views or summaries of the main report.
(a) Personnel Daily Summary – A break-down of all the different person types and a count of assigned and operating strength for each UIC. The Assigned, Operating Strength, and Females columns are not subject to the 24 hour rolling window, but are cumulative snapshots of unit strength. The Females column is a subset of the Assigned Column, rather than the Operating Strength Column. 35

36. DTAS Reports Personnel Status Report – PERSTAT (2 of 2)
SHOW SLIDE 36: DTAS REPORTS – PERSONNEL STATUS REPORT –PERSTAT (2 OF 2)
(b) Loss Summary – shows strength information such as the total number of personnel by MOS and skill level that have been lost in the last rolling 24 hour block. It also includes a by-name report of personnel losses.
(c) Gains Summary – shows strength information such as the total number of personnel by MOS and skill level that have been gained in the last rolling 24 hour block. It also includes a by-name report of personnel gains. The Remarks Section is editable by the user.
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 students to the business rules. 36

37. DTAS Reports - Unit Roster
Data elements continue to be reported beyond this screen view.
Embedded worksheets provide additional information.
SHOW SLIDE 37: DTAS REPORTS - UNIT ROSTER
The Unit Roster Report comprises the overall Unit Roster. The data displayed varies depending on whether the Army or Marines view is selected.
The Unit Roster lists all deployed personnel assigned to the unit for which a user
generates the report.
(2) It includes all data elements in the Mini-Record and is intended as a generic report that the user can modify as needed.
(3) The user can sort the report by any data column and delete those columns that the user does not require.
NOTE: The Unit Roster Report has an additional function available for the user to use prior to generating the report. This function allows the user to sort the data by categories. Business rules should be referenced for more information on the data elements contained within the Unit Roster Report. 37

38. VARIANCE REPORT OVERVIEW
SHOW SLIDE 38: VARIANCE REPORT OVERVIEW
NOTE: Transition Slide 38

39. APOD Module SHOW SLIDE 39: APOD MODULE - VARIANCE REPORT
The Variance Report is designed to show the difference between personnel with a duty status of Permanent Duty (PDY) or Temporary Duty (TDY) in DTAS and what the units are reporting on their JPERSTAT for boots on ground (BOG) strength.
NOTE: Inform the students that this report is “View Only” for users and is maintained by their Major Command Manager. To reconcile this report, the user must update both DTAS and their JPERSTAT Reports. To view the Variance Report, the user accesses the ARCENT APOD Module as previously discussed in the Employ/Manage DTAS class. 39

40. Variance Report 40 SHOW SLIDE 40: VARIANCE REPORT
Variance Report Procedures
The ARCENT Personnel Action Branch (PAB) clerk prepares the Variance Report daily and posts it on the website not later than hrs for authorized users to review. The goal is to have no more than a 2% variance.
(2) The PAB clerk contact units with a variance higher than 2%.
(3) The PAB clerk can also assist the unit in finding the cause of the variance:
(a) incorrect report on JPERSTAT
(b) incorrect duty statues in DTAS, or
(c) incoming personnel not loaded into DTAS in a timely manner.
NOTE: Variance Report Color Code: Green = variance is less than 2%; Yellow = variance is at or over 2% with minor discrepancies noted between DTAS and JPERSTAT; and Red = variance is significantly above 2% with major discrepancies noted between DTAS and JPERSTAT.
Common Reasons for Discrepancies on the Variance Report
Personnel not uploaded into the DTAS mobile system by the unit clerks
Personnel not RED/MIC (Redeployed/Mission Complete) in a timely manner
Duty status updates not completed within 24 hours of change
Unit not updating JPERSTAT
Unit is going through RIP/TOA
NOTE: Conduct a check on learning and summarize the learning activity. 40

41. Check on Learning Q: What is the purpose of the DTAS Variance Report?
A: Reconcile the DTAS and PERSTAT/JPERSTAT.
Q. What does the Gains Loss Report display?
A. The Gains Loss Report displays those personnel who have either arrived or departed the UIC/DUIC or were an operational loss to the organization during the 72-hour reporting period.
Q. What report provides an assigned and available strength count and captures gains and losses for the last 24 hour period?
A. The PERSTAT Report.
Q. How many reports can be found in the DTAS Reports Tab?
A. Four.
SHOW SLIDE 41: CHECK ON LEARNING
NOTE: Provide the following correct answers:
Q: What is the purpose of the DTAS Variance Report?
A: Reconcile the DTAS and PERSTAT/JPERSTAT.
Q. What does the Gains Loss Report display?
A. The Gains Loss Report displays those personnel who have either arrived or departed the DUIC or were an operational loss to the organization during the 72-hour reporting period.
Q. What report provides an assigned and available strength count and captures gains and losses for the last 24 hour period ?
A. The PERSTAT Report.
Q. How many reports can be found in the Reports Tab?
A. Four.
Summary: During this learning activity we discussed the DTAS Reports and Variance Report. 41

42. eMILPO
The Army’s personnel accountability system of record…including mobilized USAR and ARNG
Provides reliable, timely and efficient mechanism for managing strength accountability, strength reporting and personnel actions
Provides visibility of location, status and skills of Soldiers down to company level…vital in determining unit’s warfighting capability
Active and mobilized RC units must maintain in garrison and while deployed
Web based application via NIPRNET
Show Slide 42: eMILPO
The Army’s personnel accountability system of record is the Electronic Military Personnel Office or eMILPO. It is an unclassified web-based application that provides the Army with a reliable, timely, and efficient mechanism for managing strength accountability and performing personnel actions. This system provides visibility of location, status, and skills of Soldiers both from a high level (top of the system) and a unit level (bottom of the system). This visibility is vital in determining the war fighting capability of the Army and subordinate commands. The active component is responsible for maintaining the eMILPO data in peacetime and while deployed. During mobilization, Army Reserve and National Guard personnel are also entered into eMILPO for accountability purposes. Reserve component units are responsible for maintaining eMILPO data throughout their mobilization.
NOTE: Discuss challenges for RC units in maintaining system (training, access, etc.) 42

43. AHRS Web Portal SHOW SLIDE 49: PERSONNEL REGISTRY (DA FORM 647-1)
The DA Form 647 will be used to the greatest extent possible, and the DA Form will be used when the use of the DA Form 647 is impractical. For example, when the Soldier’s duty station is located away from the Unit maintaining the Personnel Register, mail the DA Form to the parent unit when the Soldier signs in or out.
Unit Commanders will establish procedures for maintaining the personnel register and designate a place where it will be located, during and after duty hours.
The completed DA Forms 647 and should be filed in accordance with (IAW) AR , the Army Records Information Management System (ARIMS).
NOTE: Inform the students that they can refer to AR , Table 2-7 to read the four steps on how to reconcile the personnel register. 43

44. eMILPO Reports Menu SHOW SLIDE 49: PERSONNEL REGISTRY (DA FORM 647-1)
The DA Form 647 will be used to the greatest extent possible, and the DA Form will be used when the use of the DA Form 647 is impractical. For example, when the Soldier’s duty station is located away from the Unit maintaining the Personnel Register, mail the DA Form to the parent unit when the Soldier signs in or out.
Unit Commanders will establish procedures for maintaining the personnel register and designate a place where it will be located, during and after duty hours.
The completed DA Forms 647 and should be filed in accordance with (IAW) AR , the Army Records Information Management System (ARIMS).
NOTE: Inform the students that they can refer to AR , Table 2-7 to read the four steps on how to reconcile the personnel register. 44

45. Utilizing eMILPO for Strength Accounting (1 of 3)
03/23/2010
Show Slide 45: Utilizing eMILPO for Strength Accounting (1 of 3)
The eMILPO system provides the tools necessary for maintaining accurate accountability of Soldiers. The Unit Personnel Accountability Report (AAA-162) is the primary document provided by eMILPO for strength accounting. It is a UIC level report that, in addition to its use for PAIs, S-1s and company commanders should scrub monthly to support USR. Commanders should compare the AAA-162 to their UCFR. The Personnel Readiness Team should have a desk copy to annotate gains and losses. Annotated changes should be compared to the next report printed to ensure the changes have been captured in the database.
NOTE: Discuss the purpose and elements of the AAA-162 in detail. 45

46. Utilizing eMILPO for Strength Accounting (2 of 3)
Show Slide 46: Utilizing eMILPO for Strength Accounting (2 of 3)
The bottom portion of the AAA-162 report provides a rollup of Soldiers in the unit identification code (UIC). This information should be kept up to date and provides a quick snapshot of assigned and attached strengths. Reconciling the AAA-162 must occur monthly in order to maintain accurate strengths of the unit. The Battalion S-1 should print the AAA-162 the last working day of each month and annotate all changes that have occurred but are not reflected in the system. This annotated AAA-162 is then submitted to each unit commander for verification and authentication. Company commanders should sign the copy turned in with USR to validate the data accuracy for the Soldiers in his unit. The report is then maintained on file. The Brigade S-1 PAS section performs daily error reconciliation to maintain accurate strengths.
NOTE: Discuss the purpose and elements of the AAA-162 in detail. 46

47. Utilizing eMILPO for Strength Accounting (3 of 3)
Strength Reporting Steps
Obtain supporting documentation
Have Soldier sign in/out of unit on the personnel register
Submit Transaction via eMILPO
Annotate on or print AAA-162 and Unit Commander’s Finance Report (UCFR)
Slot Soldier via eMILPO; Annotate or print the AAA-161 (HRAR)
File documents
Maintain a suspense file for PCS orders
BNs notify the PAS (Brigade S-1) of any error messages or discrepancies (AAA-351)
Reconcile within Brigade monthly
Show Slide 47: Utilizing eMILPO for Strength Accounting (3 of 3)
Strength related transactions are processed daily in eMILPO to maintain accurate strength accountability and maintain the integrity of the database. Controls must be in place to ensure that a tracking method is established to maintain accountability of Soldiers arriving and departing from a unit. Units should establish SOPs to ensure personnel understand the requirements and prevent inaccurate databases. These SOPs could include these strength reporting steps.
(1) Supporting documentation should be obtained for all strength related transactions. Supporting documents that are required are the Soldier's set of orders or other documentation, such as casualty reports.
(2) When a Soldier signs in or out of the unit, it should be accomplished using DA Form 647/647-1 (Personnel Register). The personnel register documents provide a method to maintain accuracy of strength related transactions classified as gains and losses. The DA Form 647 and DA Form are the source documents that show when a Soldier arrives and departs a unit and should be reconciled with eMILPO. Personnel registers should be closed out each day at 2400.
(3) The eMILPO transactions should be processed daily based on the personnel register. Transactions are submitted via eMILPO and the AAA-162 is annotated or reprinted to obtain the current strength.
(4) When Soldiers arrive, the Soldier must be slotted into the correct MTOE position via eMILPO. Annotate or print the AAA-161 (HRAR). The Human Resource Authorization Report (HRAR) should be annotated with changes as they occur and a new HRAR printed as needed.
(5) All supporting documentation, to include the personnel register, must be filed and maintained at the S-1 section.
(6) A suspense file must be maintained for all PCS orders so that the S-1 section can monitor outprocessing Soldiers and perform the appropriate transactions in a timely manner.
(7) When errors or discrepancies are noted, it is important for Battalion personnel to notify the Brigade personnel automation section (PAS) so that they can assist in resolving them. Battalion S-1 sections should reconcile with the Brigade PAS on a monthly basis. AR 47

48. Personnel Registry (DA Form 647)
SHOW SLIDE 48: PERSONNEL REGISTRY (DA FORM 647)
An out of balance strength condition is the result of the occurrence of a strength related personnel action and the appropriate eMILPO transaction not being prepared. Although the eMILPO transaction can be overlooked, a source document cannot. The source document is the driving force behind the personnel action. It is the source documents that will assist you in determining accurate strength figures.
The Personnel Register (DA Form 647/647-1) is a source document used when performing strength reconciliation. It is used to record military personnel arrivals to or departures from units on Permanent Change of Station (PCS) or Temporary Duty (TDY) Orders. It is also used for recording passes, leaves, and visitors. The items on the form are:
(1) Organization – This is the organization / unit that the information pertains to. As you can see on the slide and in the handout this DA Form 647 is for the SSI Training Battalion (WP01AA).
(2) Date – This is the period covered by the form (20 November 2014).
(3) Date and Time – This is date and time the action pertaining to the individual occurred.
(4) Action – This item indicates whether the Soldier is signing "IN" or signing "OUT". An "X" is placed in the applicable block.
(5) Reason – This item indicates whether the Soldier is going on leave, TDY, PCS or other. An "X" is placed in the applicable block.
(6) Name/Signature – This is the name of the Soldier that the line applies. The Soldier's printed/typed name is on the top line and the Soldier's signature is on the bottom line.
(7) Social Security Number – This is the SSN of the Soldier that the line applies.
(8) Grade – This is the grade of the Soldier that the line applies.
(9) Remarks – This line serves a variety of purposes. It is primarily used to clarify the entry or provide additional information. Since this personnel register pertains to Soldiers within a battalion, the remarks indicate the unit of assignment. 48

49. Personnel Registry (DA Form 647-1)
SHOW SLIDE 49: PERSONNEL REGISTRY (DA FORM 647-1)
The DA Form 647 will be used to the greatest extent possible, and the DA Form will be used when the use of the DA Form 647 is impractical. For example, when the Soldier’s duty station is located away from the Unit maintaining the Personnel Register, mail the DA Form to the parent unit when the Soldier signs in or out.
Unit Commanders will establish procedures for maintaining the personnel register and designate a place where it will be located, during and after duty hours.
The completed DA Forms 647 and should be filed in accordance with (IAW) AR , the Army Records Information Management System (ARIMS).
NOTE: Inform the students that they can refer to AR , Table 2-7 to read the four steps on how to reconcile the personnel register. 49

50. Personnel Accounting 50 SHOW SLIDE 50: PERSONNEL ACCOUNTING
The functional category of Personnel Accounting offers the following areas within eMILPO:
(1) Arrival (Soldier Arrival, OCONUS Arrival, Arrival Date Correction, Mass Arrival, and Revoke Arrival)
(2) Attachment (Attach Soldier (including Release from Attachment) and Mass Attachment)
(3) Slotting (Slotting – Authorized Documents and Slotting – No Authorized Documents)
(4) Duty Status
(5) Soldier Patient History
(6) Assignment History (Assignment/Duty History and Tour Credits
(7) Reserve Component Accounting (Soldier Mobilization, Soldier Demobilization, Unit Mobilization, Unit Demobilization and Attach RC Soldiers/Operational Support (ADOS))
(8) DFR/DFS (Drop from Rolls or Strength, Return from DFR/DFS, and Revoke DFR/DFS)
(9) Transition/Loss (Soldier Transition/Loss to the Army and Mass Transition)
(10) PCS Departure (Departure, PCS Departures, and Revoke Departure)
(11) RA Strength (Recall Retiree, Sanctuary/UCMJ, and Enlistment Into RA)
(12) Casualty Affairs 50

51. Personnel Accounting Transactions
SHOW SLIDE 51: PERSONNEL ACCOUNTING TRANSACTIONS
NOTE: Inform the students that the arrows point to the functions within Personnel Accounting that are used most frequently and are covered in-depth in other lesson throughout this course.
Arrival – An arrival transaction is used to report the arrival of an individual or group of individuals. The transaction is also used to report individuals who were previously attached. This transaction also adds one to the Present For Duty (PDY) status in the applicable MPC. This includes the Mass Arrival Transaction. Arrival transactions are gain transactions which will add to the total assigned strength in the applicable Military Personnel Code (MPC).
Attachments – The Attach Soldier action allows you to attach one or more Soldiers to a unit. You have the option to further attach the Soldiers without terminating the previous attachments. Attachment transactions are gain transactions which add to the total attached strength in the applicable Military Personnel Code (MPC).
Departure – A departure transaction is used to report the physical departure of a Soldier from their unit of assignment (based on orders). This transaction subtracts one Soldier from the PDY status in the applicable MPC. Departure transactions are loss transactions which will take away from the total assigned strength in the applicable Military Personnel Code (MPC).
Duty Status – The duty status transaction has a dual effect. Each transaction is counted as a gain or a loss within the applicable duty status. Remember, these transactions do NOT always affect the assigned or attached strength. Sometimes they only affect the applicable duty statuses. For example, Leave, Hospital, Temporary Duty, etc. The Duty Status allows you to add or remove a military duty status for the selected Soldier. You have the option to add new statuses and to remove the most current status 51

52. Check on Learning
Q: What is the Unit Personnel Accountability Report AAA-162?
A: It is the source and historical document for strength reconciliations. It lists all Soldiers assigned and attached to a specific organization and identifies their Deployability and Duty Status.
Q: What effect does a Departure transaction have on unit strength?
A: It is a loss to the unit's assigned strength.
Q: What is the purpose of the Personnel Register DA Form 647?
A: The Personnel Register (DA Form 647 and DA Form 647-1) is a source document used when performing strength reconciliation. It is used to record military personnel arrivals to or departures from units on Permanent Change of Station (PCS) or Temporary Duty (TDY) Orders. It is also used for recording passes, leaves, and visitors.
Q: What effect does a Duty Status Change transaction have on unit strength?
A: The Duty Status Change transaction has a dual effect. Each transaction is counted as a gain and a loss within the applicable duty status and it also provides the current duty status of the Soldier (i.e. PDY, TRA, hospital, leave, confined, AWOL. etc.).
SHOW SLIDE 52: CHECK ON LEARNING
NOTE: Provide the following correct answers:
Q: What is the Unit Personnel Accountability Report (AAA-162)?
A: It is the source and historical document for strength reconciliations. It lists all Soldiers assigned and attached to a specific organization and identifies their Deployability and Duty Status.
Q: What effect does a Departure transaction have on unit strength?
A: It is a loss to the unit's assigned strength.
Q: What is the purpose of the Personnel Register DA Form 647?
A: The Personnel Register (DA Form 647 and DA Form 647-1) is a source document used when performing strength reconciliation. It is used to record military personnel arrivals to or departures from units on Permanent Change of Station (PCS) or Temporary Duty (TDY) Orders. It is also used for recording passes, leaves, and visitors.
Q: What effect does a Duty Status Change transaction have on unit strength?
A: The Duty Status Change transaction has a dual effect. Each transaction is counted as a gain and a loss within the applicable duty status and it also provides the current duty status of the Soldier (i.e. PDY, TRA, hospital, leave, confined, AWOL. etc.).
NOTE: Summary: During this learning activity we discussed the HR Enabling Systems – TPS, DTAS, and eMILPO.
NOTE: Inform the students that they will be given a PE on Personnel Strength Data and HR Enabling Systems
upon completion, you will conduct a review of the PE and summarize the learning activities that have been
Covered during this lesson . 52

53. Unit Personnel Strength Reporting Data Practical Exercise
Strength Reporting HR Enabling Systems
&
eMILPO Transactions/Reconciliation
SHOW SLIDE 53: PERSONNEL STRENGTH DATA PRACTICAL EXERCISE
NOTE: Inform students that this is a GO/NO GO Practical Exercise, they must accurately answer 7 of 10 knowledge based questions and submit all transactions and reconcile each AAA-162 to receive a GO on the PE.
NOTE: Inform the students that portions of this Practical Exercise will be completed using eMILPO. Students must complete all required transactions in eMILPO and print a new AAA-162 for each UIC.
NOTE: Inform the students that they will have 50 minutes to complete the PE, upon completion and review of the PE we will summarize the training activities covered during the last several hours. 53

54. Strength Reporting Principles Doctrinal Responsibilities
Summary
Strength Reporting Principles
Doctrinal Responsibilities
Strength Reporting Formats
HR Enabling Systems
Show Slide 54: SUMMARY 54

55. Terminal Learning Objective
Action: Manage Personnel Strength Data
Condition: Given access to Human Resource enabling systems, FM 1-0, and an awareness of Operational Environment (OE) variables and actors.
Standards: Students will meet the standard by scoring 80% or higher on a knowledge-based performance test including the following learning activities:
Define Strength Reporting principles
Correlate Strength Reporting doctrinal responsibilities at each echelon of command
Identify Strength Reporting formats
Identify Strength Reporting HR Enabling Systems
Show Slide 55 : Terminal Learning Objective
NOTE: Inform the students of the Terminal Learning Objective requirements. 55