EAD indicates the earliest arrival date—the earliest date something can arrive given current constraints like transit time and routing. It’s a planning reference, not a forecast: it represents the soonest possible arrival if everything goes as quickly as possible. This differs from an estimated arrival date, which is a forecast that incorporates typical delays and variability. It also isn’t the generic arrival date or a destination-specific term. Use the earliest arrival date to plan resource readiness and downstream activities, for example, when a shipment leaves with a minimum transit time of two days, the earliest arrival is two days after departure, assuming no delays.

Movement planning gets activated whenever there is a directive that requires forces or assets to move. That means any order that compels movement—whether it’s a fully developed operation plan (OPLAN) or a concept plan (CONPLAN) that lays out how forces would be moved, or an order to conduct an exercise that requires staging and transport—triggers the Deployment Movement Plan. Real-world relocations driven by personnel changes, such as permanent change of station orders, also necessitate coordinating movement of people and equipment. Similarly, any order that involves movement-related tasking within a theater, like TCS orders, will prompt the same planning to ensure proper transport, staging, and sustainment. In short, whenever movement of forces or assets is authorized or needed, the Deployment Movement Plan is activated to organize and synchronize that movement.

Movement planning and execution rely on a dedicated system that compiles deployment data and generates the documents that guide shipments. TC AIMS II, short for Transportation Coordinators Automated Information for Movement II, is the primary tool used by transportation officers to input unit data and produce key deployment artifacts. It creates the Overseas Equipment List (OEL), the Unit Deployment List (UDL), and load plans, and it generates transportation control movement documents (TCMD) that track and authorize movement of personnel and cargo. This system is designed specifically for movement data and documentation, handling both air and sea shipments and ensuring that loads are properly planned, equipment is accounted for, and movement is traceable. In contrast, JOPES is focused on joint operation planning and sequencing at a broader level, not the detailed logistics documents. SDDC is a command responsible for distribution operations rather than the data-entry and document-generation tool itself, and Global Freight Management centers on freight management workflows rather than producing these deployment artifacts. Therefore, the system that creates the OEL, UDL, load plans, and certain transportation control movement documents is TC AIMS II.

This question tests how items are organized for deployment packing, specifically what belongs in the A bag. The A bag is meant for personal clothing items you need right away on arrival or during the initial phase of operations, so you can dress and manage basic needs without waiting for the rest of your issued gear. Personal clothing items are therefore the radius of items you want readily available, separate from your standard-issue kit. TA 50 items are standard-issue gear that accompanies your main kit, not typically kept in the A bag; baggage and some equipment refer to larger items that go in other containers; and items that accompany troops and should be accessible en-route are meant to be carried or kept in an easily reachable place during travel, not in the personal A bag. So, personal clothing items fit best in the A bag.