This dialog is used to set various system-wide options.
Planning Windows Tab
This tab contains various options that deal with windows of time that have special meaning.
- Frozen Zone:
- Frozen Span: This is where the Frozen Span is set.
- Lock Activities scheduled to start within the Frozen Zone: If checked then the system automatically Locks any Activity scheduled to start before the end of the Frozen Span. The Activity is not un-Locked automatically if it leaves the Frozen Span but can be un-Locked manually.
- Anchor Activities scheduled to start within the Frozen Zone: If checked then the system automatically Anchors any Activity scheduled to start before the end of the Frozen Span. The Activity is not un-Anchored automatically if it leaves the Frozen Span but can be un-Anchored manually.
- Set Operation Commit Dates When Anchoring and Re-anchoring:
- Short-term Span: This is where the Short-term Span is set.
- Planning Horizon: This is where the Planning Horizon is set.
- Stability / Change Control
- Prevent ERP Job Changes within the Stable Span: If checked then the system prevents 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 checked then the system prevents imports from auto-deleting or cancelling 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 checked then the system prevents 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 then the system prevents imports from auto-deleting or cancelling jobs if they have any Activities that are Started.
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 material that will be used by another Job (the successor Job).
Important Note: These features are only active if this option is enabled: System Options | Enabled Features | Recalculate JIT on Schedule Change Enabled.
- Set sub-job Need Dates:
- If checked, sub-job Need Dates will be set to:
- The earlier of the successor operation’s scheduled start or JIT start (for scheduled successors)
- The JIT start (for non-scheduled successors)
- If a sub-Job feeds multiple successor Jobs then the earliest of the above dates for the successor Jobs is used.
- If the successor operation is locked to or has a Default Resource that is a Drum Resource then the sub-Job NeedDate is set back by the Drum Buffer. If the successor operation is unlocked and has no Default Resource but has one or more eligible Drums then the sub-Job NeedDate is set back by the largest of the eligible Drum Buffers.
- If checked, sub-job Need Dates will be set to:
- Set sub-job Priorities: If checked, sub-job Priorities will be set to the lowest value (highest Priority) of all successor Jobs Priorities.
- Set sub-job Hot Flages: If checked, sub-job Hot flags will be set to Hot if any of the successor Jobs is set as Hot.
This feature applies to Jobs that are connected by Material. It does not apply to Jobs that are connected by the Successor MOs feature.
Incoming Data Problems Tab
Capability does not exist: This specifies the action taken by the system if an Operation is imported and it specifies a Capability that does not yet exist.
- Reject the Manufacturing Order: The Manufacturing Order and its Job are rejected and must be reloaded in order to be scheduled.
- Omit the Operation: The Operation is marked as “Omitted Automatically” and the Job is scheduled without it.
- Create the Capability: The Capability is automatically created and added to the Capability list. It will still need to be assigned to one or more Resources in order to scheduled the Job. The Capability’s description is set to indicate that the Capability was automatically created.
Warn if Operation length is larger than:
This will notify the user if an operation imported has a length longer than the time frame specified in the drop down menu. These warnings can be disabled by setting the drop down menu to “0 minutes”
ERP Update of Activities Manually Updated
These controls specify how updates from an ERP system via JobT transmissions should be handled when updating Activities that were previously updated internally or through a bar code system using an InternalActivityFinishT transmission. The overall purpose of these options is to provide a way to preserve changes made to the Activity status by a user or bar code system so that the ERP updates do not override the internal changes.
Allow ERP Production Status to override current status: If checked, then 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 coming 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 that certain Activity values are never updated by an ERP transmission once the Activity is “Finished Internally”. These include: Paused, People Usage, Nbr. of People, and Comments. These values are always preserved.
Undo & Checksum Tab
This tab contains various options that control how the Undo & Checksum feature functions. Note that changes to these settings will not take effect until the APS.net Service is restarted.
- Undo Settings
- Maximum Seconds to Perform Undo: The cumulative amount of processing time of actions that triggers scenario data to accumulate for the purpose of potential Undos. Smaller values cause more frequent disk access but result in less time for an undo action. Larger values require less disk accesses but require more time for Undos. The value is specified in seconds.
- Maximum Number of Undo Sets to Store: The number of undo sets to store to disk. Example: If the Max Seconds is set to 10 and Max Undo Sets is set to 10 then you will be able to undo at least 100 seconds worth of actions.
- Maximum Transmissions Per Undo Set: The maximum number of transmissions that an undo set can contain. Once this number is exceeded a new Undo Set is created.
- Checksum Frequency Settings
- Whenever an Undo Set is saved: Less frequent
- After every schedule change: More frequent
Max Histories Count: This specifies the maximum number of Scenario Histories to store in the system for each Scenario. Regardless of this setting, all Scenario Histories are shown as they are created in the APS.net Client if it is running. This controls how many Histories are stored between sessions. Each Scenario History that is stored will take up memory (approximately 500 bytes) thus increasing memory requirements and the time to load and save the system. Changing this value will cause the system to, at the next History event, purge any excessive Histories beyond this amount that are already stored. The next time the APS.net Client is started, it will have no more than this number of Histories in the Scenario Histories pane.
Export to SQL Server Database: This specifies whether the system should update or overwrite the data in the SQL Server database. If you will be entering any data in the database manually then this setting should be set to Update only or else your data will be lost the next time the Export to SQL Server Database command is executed.
Job Lateness Threshold:
Fiscal Year End:
Schedule Custom Report Field Script:
- Exclude Unsatisfiable jobs:
- Optimize Satisfiable Paths:
Enable Features Tab
This tab is used to enable or disable features that may or may not be being used. Disabling features that aren’t being used can often improve system performance.
- Miscellaneous Features:
- Adjust MO Quantity Enabled: Controls whether or not the Quantity of an Activity can be changed by dragging and dropping one side of an Activity Block.
- Enforce Max Delay: If checked, this feature will force an Operation’s Successors to be scheduled within a certain amount of time as defined by the Max Delay.
- Auto Select Alternate Paths: Controls whether or not Alternate Paths are automatically selected.
- Show MO Batching Tab: MO Batching will appear on the Optimize Options if this is checked.
- Optimization Score Analysis: Controls whether or not the Optimization Score Analysis will be done. Leaving this unchecked will increase system performance.
- Move Compresses Predecessor Enabled: Controls whether dragging an Operation before its Predecessors results in the Predecessors being moved earlier to accommodate the drop-time of the Activity.
- Recalculate JIT on Schedule Change Enabled: If unchecked, JIT dates won’t be recalculated each time the schedule changes and each Optimize will generate the same schedule.
- Split Operation Enabled: Controls whether or not Operations can be split.
- Split Job Enabled: Control whether or not the Job as a whole can be split.
- Split MO Enabled: Controls whether or not an entire Manufacturing Order can be split.
- Join Enabled: Controls whether or not Jobs and MO’s can be joined together to create a merged Job or MO.
- Expedite After Split: Expedites the split jobs after they’re split
- Track Actuals
- Maximum Age:
- Performance Thresholds:
- Quantity Rounding: Rounds all values in the system, using 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:
This tab contains various options that deal with System Security.
- Require Passwords to be changed periodically: If checked passwords changes will occur at specified interval.
- Require Strong Passwords: Strong passwords must be at least 8 characters long, contain at least one upper and one lower case letter, and one number or special character