Resource Options

Key Concepts

The resource properties dialog allows users to view detailed information about the particular resource, such as the optimization rules defined, the capacity type, whether the resource can support multiple jobs simultaneously, and much more. The resource properties dialog can be accessed by double-clicking a resource from the Gantt view.

Resource Properties Options

The different tabs of this window contain different settings and configurations for the various resource properties. Each tab and configuration is explained below:

Work Assignment

  • Capabilities: This section displays which capabilities are assigned to the resource. The number to the right of "Capabilities" displays the number of capabilities assigned to that particular resource. New capabilities can be added to the resource by checking the corresponding checkbox from the list.
  • Quantity Constraints:
    • Max Qty: This number specifies the maximum quantity of goods that the resource can produce. For a resource to be considered eligible for an activity, the activity's required finish quantity must be less than or equal to this value.

    • Max Qty Per Cycle: This value specifies the maximum quantity of goods produced by cycle on the resource. For a resource to be considered eligible for an operation, the operation's quantity per cycle value must be less than or equal to this amount. 
    • Min Qty: This number specifies the minimum quantity of goods that that specific resource must produce. For the resource to be considered eligible for an activity, the activity's required finish quantity must be equal to or greater than this value.
    • Min Qty Per Cycle: This number specifies the minimum quantity of goods produced per cycle. For the resource to be considered eligible for an operation, the operation's quantity per cycle must be equal to or greater than this value.
  • Attribute Code Table Name: The Attribute Code Table is used to calculate the resource's setup cost and time-based on sequential operation attribute code changes. This value is blank if no Attribute Code Table has been assigned.
  • Active: Checking this box determines that the selected resource is active and available to have work scheduled.
  • Manual Scheduling Only: This removes the resource from optimization calculations and makes the resource only eligible for drag-and-drop schedule changes.
  • Disallow Drag-and-Drop: This sets the resource only to be eligible for changes in the schedule set by optimization calculations.

Optimization:

  • Optimize Rules
    • Normal Rule: This is the set of optimization rules that are used for normal operation.
    • Experimental Rule: This is the set of optimization rules that are generally used in What-If scenarios.
  • Setup / Changeover Optimization
    • Max Cumulative Qty: This is the maximum number of simultaneous activities allowed on the resource. This field is often used to model the capacity of Tank resources or Subcontractor resources. A violation of the max cumulative quantity is flagged if the total unfinished quantity of the resource exceeds this number.
      Note: this is only a flag and not a constraint.
    • Max Same-Setup Span: When using "Same Setup Code" optimization rules, a setup code change is forced after this specified number of hours or cycle-time passes. This option can be used to force periodic rotation between groups of products.
    • Same-Setup Headstart Multiplier: This value is used to calculate how far an operation can be scheduled before the current JIT start date. Larger values will result in activities with longer setups being allowed to start earlier to save a setup. This can be used to prevent excessive inventory buildup and help in grouping together activities with the same setup code. 
  • Headstart Span: This controls how early a job can schedule before its Just-In-Time Start Date. Lower values will schedule the job closer to its JIT start date. 

Display

  • Resource Type: This is a flag that is generally used for reporting purposes. It defines whether a resource is a machine, an operator, a supervisor, etc.
  • Gantt Row Height Factor: This option controls how tall the resource row is relative to the other rows on the Gantt chart by entering a number from 1 (shortest) to 10 (tallest). The primary function of this option is to emphasize resources that are a greater priority, such as drum resources.
  • Image: This allows you to change the image seen next to the resource's name in the Gantt view.
  • Sort Index: This is used to order the resources on the Gantt in your preferred order. Resources are arranged alphabetically by default. Setting a sort index will allow you to decide how the resources are grouped and arranged. Note: Departments can also be ordered at the top of the Gantt using the sort index. This is done from Settings | Scenario Data | Resources.
  • Exclusions: Users can choose to exclude the resource from the capacity plan, the Gantt / activity grid, the reports, or only show the resource in the department section. This is used when a resource is no longer in use, but there is no desire to remove the resource from the shop floor. 

Capacity

  • Capacity Type: This field is used to specify if a resource has an infinite or finite capacity and whether the resource is single-tasking or multi-tasking. 
    • Infinite Capacity: The resource can perform any amount of work simultaneously.
    • Single Tasking: The resource can only perform one activity at a time.
    • Multi-Tasking: The resource can perform multiple activities at a time based on the resource's Attention Percent. The attention percent is a numerical value for how much of the resource's attention is devoted to that activity.
  • Tank: This is used to specify that a resource will be used as a tank to store materials. Tanks are considered in use until downstream operations empty them. 
  • Batch Scheduling: Batch scheduling allows multiple activities to be scheduled simultaneously on a resource as a single activity block (i.e., starting and ending simultaneously). Only operations with the same batch code will schedule together in the same batch.
    • Batch Type: Batch Scheduling can be done by percent or by volume. 
      • Percent: Activities are batched until 100% of the batch is filled. The percent occupied by each activity is calculated by dividing the activity's Required Finish Qty by its Qty Per Cycle.
      • Volume: Activities are batched until the activities' Required Finish Quantities equals the resource's batch volume.
    • Batch Volume: This is the maximum number of units included in a batch when using batch by volume.
  • Efficiency Multipliers: These are resource-wide modifiers of the setup and cycle times that can be changed to reflect whether resources run faster or slower than usual.
    • Setup Time: This value can be changed to reflect whether the setup time of the resource is faster or slower than usual. Values greater than one represent a resource setup that is slower than usual, while values less than one represent a resource setup that is faster than usual. 
    • Cycle Time: This value can be changed to reflect whether the run time of the resource is faster or slower than usual. Values greater than one represent a resource running slower than usual, while values less than one represent a resource running faster than usual. 

Setup / Changeover:

  • Setup Included: Indicates when to add setup time to an operation scheduled on this resource:
    • When Product Changes: This option schedules a setup if the manufacturing order's product is different from the previous product.
    • When Setup Code Changes: This option schedules a setup if the operation's setup code differs from the previous one.
    • When Either Changes: This option schedules a setup if the manufacturing order's product or the operation's setup code is different.
    • Always: This option always schedules a setup time, with no exception.
    • Never: This option never schedules a setup time. Note: This is related to operation changeovers. If a "Setup Span" is defined below, setup will still be incurred as that feature is set at the resource level.
    • When Setup Number Changes: This option schedules a setup time if the operation's setup number is different.
    • When Setup Number Increases: This option schedules a setup time if the operation's setup number is greater than the previous setup number.
    • When Setup Number Decreases: This option schedules a setup time if the operation's setup number is lower than the previous one.
    • Use Setup Code Tables: This is calculated based on the operation's setup code values and a setup code table lookup.
    • Use Operation Attributes: This option uses the setup time as defined in the operation header.
  • Consecutive Setup Times: Sets setup time as the sum of all setup time incurred by the different attributes on the operation header.
  • Omit Setup on First Activity: If selected, the setup time on the first activity scheduled on the resource is always zero.
  • Omit Setup on First Activity in Shift: If selected, then the setup time on the first activity scheduled on a capacity interval is always zero.
  • Setup Span: This allows users to define a setup time span to be applied to activities scheduled on the resource. Note: This is not related to the "Setup Included" options. If a value is chosen here, it will be applied to all activities scheduled on the resource (even if the "Setup Included" is set to 'Never'). The "Setup Included" options above are related to operation changeovers. 
  • Attribute Code Table Name: The Attribute Code Table is used to calculate the resource's setup cost and time-based on sequential operation attribute code changes. This value is blank if no Attribute Code Table has been assigned. 
  • The Setup Code Table Name: The Setup Code Table calculates the resource's setup cost and time based on sequential operation setup code changes. This value is blank if no Setup Code Table has been assigned. 
  • Current Setup: This allows the user to define the current Product, Setup Code, and Setup Number for the first run. 

Advanced Rules

  • Transfer Span is used to specifying the amount of time that must pass before successor operations can start after finishing the previous operation. The resource is not consumed during this time.
  • Compatibility Group: Resources part of the same compatibility group can only run operations concurrently if they have the same compatibility code specified in their job operation's header. 
  • Stage: This is used to set the stage number for resources with the same capabilities so that groups of resources can be scheduled stage by stage when using multi-stage scheduling. 
  • Min Nbr Of People: This is the minimum number of people required to perform operations on the resource. 
  • Sequential: This property only applies to infinite resources and was added to help model conveyors. When this box is checked, the system makes sure that every activity scheduled is finished on or after the last scheduled block time. If an activity is scheduled to complete before the last scheduled block, the finish time is adjusted so that the activity and the last block finish simultaneously. 
  • Cellular Scheduling: This associates the resource with a particular cell. A cell is defined as a part of the shop floor where either a family of parts is produced in a single line or a group of machines controlled by operators who work specifically within that line or cell. When selected, the user can specify which cell the resource should be associated with. Successor operations will attempt to schedule resources in the same cell.
  • Drum-Buffer-Rope (DBR): This allows the user to set the resource as the Drum, setting the pace for the rest of the shop floor. The drum buffer can also be set from this window.
    Note: Drum-Buffer-Rope release rules must be in effect for these values to impact the optimization engine. 
  • Auto-Join Span: The Auto-Join span is calculated from the PlanetTogether clock and represents the time span in which resources are processed to be Auto-Joined. 
    • Limit AutoJoin to same shift: This limits the Auto-Join processing of the resources to single shifts so that rescheduling between shifts is allowed. 

Analysis

  • Bottleneck: The resource is flagged as a bottleneck if more than the plant's bottleneck threshold of activities on the resource are capacity bottlenecked.
    • Activities Bottlenecked: Can be represented as a percent of the resource's scheduled activities that are capacity bottlenecked or as a number of the scheduled activities that are capacity bottlenecked on that resource. 
  • Hourly Costs
    • Standard: This displays the cost of running the resource under normal conditions.
    • Overtime: This displays the cost of running the resource during overtime capacity intervals. 
  • Shop View Users Count: This displays the number of users that have access to view the resource. This is based on the number of users who have Can View Shop Views in their user's dialog and access that particular resource. 
  • Processing Status: Specified the resource's status as of the last update. 
  • Overlapping Online Intervals Count: This displays the number of normal online intervals that are overlapping. This is a warning since overlapping intervals are not usually set up intentionally, and the overlapping intervals will be summed during their overlaps. 

 

Related Articles:

Resources