System Options

Key Concepts

The System Options tab is used to set various system-wide settings. It can be accessed by going to Settings | System Options.

Plant Spans Tab

This tab contains various options dealing with windows of time that have special meaning.

  • Frozen Span: The Frozen Span represents a time window in which jobs and operations are locked and anchored. The length of the Frozen Span can be defined here and will begin at the beginning of the schedule. Once set, the Frozen Span will appear as an orange zone in the Gantt. Note: The Frozen Span is applied to all plants when defined in the System Options. This may be undesirable, depending on how similar or different your plants are. 
  • Lock Activities scheduled to start within the Frozen Zone: If enabled, the system will automatically lock any activity scheduled to start before the end of the Frozen Span. Note: Activities are not un-locked automatically if they leave the Frozen Span, but they can be un-locked manually.
  • Anchor Activities scheduled to start within the Frozen Zone: If enabled, the system will automatically anchor any activity scheduled to start before the end of the Frozen Span. Note: Activities are not un-anchored automatically if they leave the Frozen Span, but they can be un-anchored manually.
  • Set Operation Commit Dates When Anchoring and Re-Anchoring: If enabled, the operation's CommitStartDate and CommitEndDate will be set to when the operation is anchored.
  • Short-term Span: This is where the Short-term Span is set. The Short-term Span starts calculating from the scheduling clock, so it will change when the clock is advanced.
  • Planning Horizon: This is where the Planning Horizon is set. The Planning Horizon starts calculating from the scheduling clock and represents the window of time where jobs can be scheduled. 

 

MPS/MRP Tab

This tab contains various options related to resetting the values of sub-jobs based on changes to successor job schedules. A sub-job is a job that is creating a material that another job will use.

  • Set sub-Job Need Dates: This drop-down menu allows users to choose how they with the sub-job need dates to be calculated. 
    • Disabled: To use the sub-job need date settings defined in the MPS/MRP Optimize tab, this field must be set to Disabled. Otherwise, the option defined in the System Options will override the changes made in the MPS/MRP Optimize tab.
    • To earlier of JIT and scheduled start date: The need date of the sub-job is set to the earlier of its JIT start date or its parent job's scheduled start date.
    • To JIT date: The need date of the sub-job is set to the JIT start date of its parent job.
    • To start date: The need date of the sub-job is set to the scheduled start date of its parent job. 
    • To bottlenecked Operation start date: The need date of the sub-job is set to whichever operation is causing a bottleneck.
  • Set sub-job Priorities: If checked, sub-job priorities will be the lowest value (highest priority) of all successor job Priorities. 
  • Set sub-job Hot Flags: If checked, sub-job Hot flags will be set to Hot if any successor jobs are set to Hot.

Note: These features apply to jobs that are connected by material. They do not apply to jobs that are connected by the Successor MO feature. 

 

Scheduling

  • Adjust MO Quantity: If enabled, the quantity of activity will be changed by dragging and dropping one side of an activity block.
  • Max DelayIf enabled, this feature will force an operation's successors to be scheduled within a certain amount of time as defined by the MaxDelayHrs column of the Alternate Path settings. 
  • Auto Select Alternate Paths: If enabled, Alternate Paths will automatically be selected. This option is useful when there are multiple methods of producing an item to let the system automatically select an alternate path when the needed date of the manufacturing order is approaching. 
  • MO Batching: If enabled, an MO Batching tab will appear at the top of the Optimize Option dialog. This will allow users to group manufacturing orders with the same Batch Group Name. 
  • Move Compresses Predecessors: Controls whether dragging an operation before its predecessor results in the predecessors being moved earlier to accommodate the drop time of the activity. 
  • Calculate Optimize Scores: If enabled, the optimize score will be calculated. Note: Score calculation can consume hundreds of millions of score records and add significant time to optimization. Leaving this option disabled will increase system performance. 
  • Job Lateness Threshold:
  • Jobs with unsatisfiable paths will not be scheduled:
  • Recalculate JIT on Schedule Change: If disabled, the JIT dates will not be recalculated each time the schedule changes, and each will generate the same schedule.

 

Splitting Tab

  • Split Operation: If enabled, operations can be split.
  • Split Job: If enabled, the job as a whole can be split. 
  • Split MO: If enabled, the manufacturing order as a whole can be split.
  • Join: If enabled, jobs and manufacturing orders can be joined together to create a merged job or manufacturing order.
  • Expedite After Split: Expedites the split jobs after they are split. 

 

Undo & Checksum Tab

This tab contains various options that control the Undo/Redo functions. Note that changes to these settings will not take effect until the APS System Service is restarted.

  • Maximum Seconds to Perform Undo: This represents the cumulative processing time of actions that trigger scenario data to accumulate for potential Undos. Smaller values cause more frequent disk access but result in less time for an undo action. Larger values require less disk access but require more time for Undos. 
  • Limit memory used for undoing sets (in MB): The maximum number of MB used to store undo sets in memory. 

 

User Security Tab

  • Require Passwords To Be Changed Periodically: If enabled, password changes will occur at the specified time interval.
  • Password Complexity Configuration: This option allows you to enable the password complexity rules and configure the preferred level of complexity for user passwords. The configuration options allow you to set a password length and specify whether users require uppercase letters, lowercase letters, digits, and/or special characters.
  • Maximum Number of Failed Login Attempts: This specified the number of times a user can enter an incorrect password before they get locked out. There is no time factor to the failed attempts, and an administrator can unlock a user if they accidentally get locked out.
  • Auto Logoff Users: If enabled, users who have been inactive for the amount of time specified in the 'Auto Logoff Timeout' field will be logged off.
    • Auto Logoff Timeout: Admins can specify the number of minutes users must be inactive before logging off. Inactive users will receive a message that they are being signed out due to inactivity and can decide to remain logged in.
    • The Timeout Period is reset when the user changes tabs, acts (Clock Advance, Import, Publish, Optimize, MRP, etc.), or another action that causes a popup window to open.

 

Incoming Data Tab

  • Prevent ERP Job changes within the Stable Span: If enabled, the system will prevent imports from changing jobs in any way if they have one or more activities scheduled to start before the end of the stable span.
  • Prevent ERP Job cancel or delete within the Stable Span: If enabled, the system will prevent imports from auto-deleting or canceling jobs if they have one or more activities scheduled to start before the end of the stable span. 
  • Prevent ERP changes on Started Jobs: If enabled, the system will prevent imports from changing jobs in any way if they have any activities that are started. 
  • Prevent ERP Cancel or Delete of Started Jobs: If checked, the system prevents imports from auto-deleting or canceling jobs if they have any started activities. 
  • Allow ERP Production Status to override current status: If enabled, the activity will have its Production Status set to the value specified by the ERP system, overriding its current status.
    • Update Values from ERP: This determines when the activity's Reported Quantity and Hours should be updated. This includes: Reported Setup Span, Reported Run Span, Reported Post Processing Span, Reported Good Qty, and Reported Scrap Qty. 
      • Never: The activity's current values are never updated.
      • If ERP Values are Greater: The activity's values are only updated if the new value from the ERP system is larger than the activity's current values. Each new value is compared to the corresponding existing value individually and updated only if larger.
      • Always: The activity`s current values are always updated by the new ERP values.

Note: Certain activity values are never updated by an ERP transmission once the activity is "Finished Internally." These include Paused, People Usage, Number of People, and Comments. Instead, these values are always preserved. 

 

Tracking Data Tab

  • Track Actuals Maximum Age: The amount of time that Track Actual blocks will appear on the Gantt after an activity is marked as finished. 
  • Quantity Rounding: Rounds all values in the system using the selected precision (length of decimal to store). Enabling this feature can help with splitting issues and is necessary when using MRP Optimizations.
  • Time Span Rounding: Will round all timespan values using the number of decimal places specified.

 

Publishing

  • A maximum number of Scenario Histories to store for each Scenario specifies the maximum number of scenario histories to store in the system between sessions for each scenario. Regardless of this setting, all scenario histories are shown as they are created in the PlanetTogether APS Client if it is running. Each scenario history that is stored will take up memory (~500 bytes), thus increasing memory requirements and the time to load and save the system. Changing this value will cause the system to purge excessive histories beyond the amount specified at the next historical event. The next time the PlanetTogether APS Client is started, it will have no more than this number of histories stored.