Tracking how a part’s cost and its usage have changed over time is handled by a screen that records time-stamped cost values and usage quantities for each part. This history view lets you see trends, compare different periods, and link changes in cost or consumption to procurement or production events. In IMDS, the screen named Parts/Inventory Cost History or Usage History is built specifically for this purpose. It captures historical data so you can analyze cost trends, monitor usage patterns, and make informed decisions about stocking, pricing, and supplier negotiations. For example, you can check if a part’s price has been rising over the last year or if its usage spikes during certain production runs. Other screens focus on current state rather than historical per-part data: an Asset Tracking dashboard shows where assets are and their status, Maintenance Scheduling handles upcoming service tasks, and Labor Allocation tracks work hours and resource assignment. None of these provide the per-part historical cost or usage history in the same targeted way.

To view every scheduled event for an aircraft within a chosen time window, you need a screen that pulls together all upcoming items for that aircraft and filters them by the selected period. Screen 361 is the one designed for that task, presenting a consolidated list of scheduled events for the aircraft and allowing you to specify the time window. This makes it easy to see everything planned in that interval at a glance, which helps with planning, sequencing, and avoiding clashes between maintenance, inspections, and flights. Other IMDS screens are meant for different views or data types, so they won’t provide the same complete, time-bounded schedule for a single aircraft.

In IMDS, screen numbers map to specific data views you can pull or print. The request to get a printout of all shop data for a TCTO is fulfilled by the screen that is specifically set up to assemble and format all relevant shop information for that TCTO. That screen is the one labeled with 663. It gathers the full set of shop data—labor actions, parts usage, status, and related details—into a single printout, which is why it’s the correct choice. The other screens point to different inquiries or reports and don’t produce the complete TCTO shop data printout. They may show partial or different information, but not the full, print-ready data set for a TCTO.

Cancellation and delay reason codes are managed through a dedicated catalog screen in maintenance planning. This screen serves as the authoritative reference for all reasons used when a maintenance task is canceled or delayed, storing both the code and its description so planners can consistently tag events. Having a centralized place for these codes ensures data entry is standardized, which in turn supports accurate reporting and trend analysis. When a plan is canceled or a delay occurs, selecting a code from this catalog links the event to a clear, predefined reason, making it much easier to track patterns and drive improvements. Other planning screens handle different functions—such as viewing or editing orders, scheduling, or managing parts—and they’re not the repository for cancellation and delay reason codes.