Use this window to view information about the data used in the schedule. The data is organized in a graphical structure, with more detailed information at lower levels of the structure. Each item in the structure is a scheduling object that you can drag elsewhere in the Data Tree or into the Gantt chart. You can expand or collapse entire levels of the structure by clicking the plus and minus signs next to the objects, just as you can open or close folders in the main Navigator in IFS Applications.
This window contains three top-level objects: Activities, Master Data, and Scenarios. The Activities object is the root of all objects that represent work in the schedule. It expands to display some of the following types of individual objects: DOP demand orders, promise demand orders, promise shop orders, resource breaks, shop orders and work orders. The Master Data object is the root of all objects that do not represent work in the schedule, including objects representing characteristics of orders, resources, and capacity. The Master Data object expands to display individual characteristics, materials, labor classes, tool sets, work centers, and work time calendars; or crafts, employees, material, tool sets and work time calendars. The Scenarios object is the root of all objects that represent a specific scheduling scenario. It expands to display lists of pre-defined scenarios and custom scenarios, if any.
The Data Tree window consists of four tabs: All Items, Activities, Master Data, and Scenarios. Click the All Items tab to view all objects in the structure; the Activities tab to view only the Activities objects; the Master Data tab to view only the Master Data objects; and the Scenarios tab to view only the Scenarios objects.
Select any object and right-click to choose from the options that are appropriate for that object. Optionally, select multiple objects and then right-click to select options that are appropriate for all these objects.
Click the selector bar and drag the Data Tree window to dock it on any side of the main window or to enable it to float above the Gantt chart. Alternatively, select Data Tree View from the Windows menu to move the Data Tree through each of the docking positions.
N/A
Evaluate Result
Reschedule
Manually using Drag and Drop
Start Simulation Client
Load Saved Simulation File
Save Simulation Result to
File
Start Scheduling
Client
This window contains
Activities objects:
Demand Orders: The root object for all dynamic order processing (DOP) orders. This object expands to display the individual demand order objects. Each of these objects is a collection of shop orders, and possibly purchase orders, that must be completed to fulfill a specific customer demand.
Promise Demand Orders: The root object for all promise demand orders. This object expands to display the individual promise demand order objects. Each of these objects is a collection of shop orders, and possibly purchase orders, that must be completed to fulfill a specific customer demand.
Promise Shop Orders: The root object for all promise shop orders. This object expands to display the individual promise shop order objects. Each of these objects represents an individual shop order that must be completed to fulfill a specific promise demand order.
Resource Breaks: The root for all objects representing individual and collections of basic non operation event elements in the schedule. This object expands to display the individual collection of resource breaks and resource break objects. Each collection of resource breaks object represents a collection of basic non operation event element operations in the schedule. It expands to display the individual resource break objects and/or additional collection of resource breaks objects. Each resource break object represents a basic non operation event element in the schedule. It is used to prevent operations from scheduling one or more resources during a specified time period.
Shop Orders: The root for all objects representing shop orders and shop order operations in the schedule. This object expands to display the individual shop order objects. Each of these objects represents a collection of operations in the schedule. An individual shop order object expands to display the individual operation objects that are part of the shop order. Each operation object represents a basic element of work in the schedule.
Work Orders: The root object for all objects representing work orders and work order operations in the schedule. This object expands to display the individual work orders. The first level can either be a separate, standalone work order or a top work order in a work order structure or a project node collecting all work orders that belong to a specific project. The next level can either expand to a new work order in a structure or a work order operation.
Master Data objects:
Crafts: The root for all objects representing crafts.
Employees: The root for all objects representing employees. Employees are grouped per maintenance organization.
Characteristics: The root for all objects representing part characteristics. This object expands to display the individual characteristic objects. Each characteristic object represents a particular part characteristic that may be related to shop orders, such as diameter, color, or weight. It expands to display the individual characteristic value objects that are possible for this characteristic. Each characteristic value object represents a possible value for the characteristic. For example, red, blue, and green might be characteristic values for the Color characteristic.
Materials: The root for all types of materials. This object expands to display the individual material objects. Each material object identifies parameters which influence scheduling. These parameters include the material's availability definition, its lead time and current available supply.
Labor Classes: The root for all types of labor classes. This object expands to display the individual labor class objects. Each labor class object represents a collection of labor resources that fit into a labor category, e.g., laborers, employees, and workers. For example, you might create a labor class called Welders, which would include all workers who are skilled at welding. Each labor class object expands to display the individual labor resource objects. Each labor resource object represents a worker who provides labor.
Tool Sets: The root for all objects representing single tools or collections of them. This object expands to display the individual tool set objects. Each tool set object represents a collection of tools or a category of tool types. For example, you might create a tool set called Drills that includes all available drills. Each tool set object expands to display the individual tool instance objects. Each of these objects represents a single basic tool. For example, one tool instance might be a 1/2 HP drill, and another one might be a 3/4 HP drill. Tools are grouped by their type and then by the maintenance organization they belong to.
Work Centers: The root for all objects representing resources in the schedule. This object expands to display the individual work center objects. Each work center object represents a collection of resources. It expands to display the individual resource objects in the work center. Each resource object represents the basic element of capacity in the schedule.
Work Time Calendars: The root for all objects representing available time to perform work in the schedule. This object expands to display the individual calendars, day types, schedule exceptions, and schedules objects.
Calendars: The root for all objects representing calendars in the schedule. This object expands to display the individual calendar objects. Each calendar object defines a set of available working times that can be associated with a work center.
Day Types: The root for all objects representing available time in a day. This object expands to display the individual day type objects. Each day type object represents the basic component used to build a schedule or schedule exception. It defines time periods within a 24-hour period. For example, if a typical work day is 8:00 A.M.– 5:00 P.M., with a one-hour lunch break, then a day type could be created with two working periods: 8:00 A.M.– 12:00 P.M., and 1:00 P.M.– 5:00 P.M.
Schedule Exceptions: The root for all objects representing exceptions to schedules in a calendar. This object expands to display the individual exception objects. Each exception object represents a collection of days that are exceptions to a regular schedule in a calendar. For example, a holiday might be entered as an exception to the normal five-day work schedule.
Schedules: The root for all objects representing collections of schedule objects. This object expands to display the individual schedule objects. Each schedule object represents a collection of day types that are used to define working time in a calendar. A typical schedule defines a week containing seven days. For the typical five-day work week, the schedule might include the weekend day type for the first day (Sunday), five weekday day types for Monday through Friday, and the weekend day type for the last day of the week (Saturday).
Scenarios objects:
Pre-Defined Scenarios: The root object which comprises of the pre-configured scheduling scenarios, namely All Shop Orders and Tardy Shop Orders. The All Shop Orders scheduling scenario object represents all the shop orders that exist in the current schedule. The Tardy Shop Orders scheduling scenario object represents all the shop orders that do not meet the required need date as per the current schedule.
User-Defined Scenarios: The root object which comprises of the scheduling scenarios that you have created and configured.