Shop Views Options

The Shop Views Options are used to customize the information displayed in the Shop Views application. To access the following options, go to Settings | Scenario Data | Operation Status Options. 

Resources Tab

This grid allows each Resource to have specific Users and a particular Resource Option Set assigned.

If no Users are specified, then all Users who have access to Shop Views (based on Can View Shop Views in the User's dialog) are permitted access to the Resource and their Access Rights are set as described below.  If one or more Users are specified for a Resource then only those Users are granted access to the Resource in Shop Views.

  • Can Resequence:  Whether Activities can be dragged-and-dropped in the Shop Views grid to reschedule them to different times on the same Resource. (If Resource Users are not specified, then this is set based on whether each User's Scenario Access is Master Scheduler.)
  • Can Reassign (For Future Use):  Whether Activities can be rescheduled to other Resources from the Shop Views dialog. (If Resource Users are not specified, then this is set based on whether each User's Scenario Access is Master Scheduler.)
  • Can Update Status:  Whether Activity statuses such as completion quantities and run status can be updated from the Shop Views dialog. (If Resource Users are not specified, then this is set based on whether each User's Can Change Job Status option is checked.)

Each Resource has an Option Set specified.  The Resource Option Set is used to customize the Shop Views dialog for the Resource.

Note: These settings are only applied to the current Scenario.

Resource Option Sets

These sets of options are used to customize the Shop Views Dialog for individual Resources.  This allows, for example:

  • Defining alternative languages for text.
  • Using different company-specific terms such as "Work Order" instead of "Job".
  • Hiding fields that are not relevant for a particular Resource to simplify the display.
  • Limit which Activities are shown to avoid confusion or execution out of scheduled sequence.

Any number of Option Sets can be created.  They can be shared by Resources, copied, and deleted.  Each Resource must refer to one Option Set and so the last Option Set cannot be deleted (There must always be at least one.).

Resource Option Set

Options

  • Option Set Name:  User-defined identifier for the Option Set.
  • Non-Ready Activity Treatment:  If set to Read-Only, then Activities that have a Production Status of "Waiting" are shown in gray text and cannot have their status updated.  If set to Hidden then the Activities don't appear in Shop Views at all.
  • Non-Leading Activity Treatment:  If set to Read-Only, then Activities that are not the first Activity on the Resource's schedule are shown in gray text and cannot have their status updated.  If set to Hidden then the Activities don't appear in Shop Views at all.
  • Treatment of Activities scheduled to start after the Resource's Head Start Span:  If set to Read-Only, then Activities that are scheduled to start more than the Resource's Head Start Span from the current time are shown in gray text and cannot have their status updated.  If set to Hidden then the Activities don't appear in Shop Views at all.
  • Show Activities that start in the next:  Activities scheduled to start beyond this time span from the current time are not shown in the Shop Views.
  • Maximum Number of Activities to Show:  Only up to this number of Activities are listed.  The others are not.
  • Enforce the Resource Capacity Type:  If checked, then the number of Activities that can be put into production simultaneously in Shop Views is limited based on the Resource's Capacity Type.  If the Capacity Type is Single Tasking then if an Activity is in production (Setup, Run, or Post Processing) on the Resource, other Activities are shown as read-only in Shop Views thus preventing another Activity from being started.  Finishing the Activity or marking the Activity as Paused or On-Hold allows another Activity to be started.  If the Capacity Type is Multi-Tasking then once 100% of the Resource Attention is used up by the sum of the in-production Activities' Attention Percents, the other Activities are made read-only.  If the Capacity Type is Infinite then any number of Activities can be started simultaneously.
  • Prevent Finish of Activities without full quantity reporting:  If checked, then when the "Finish" button is clicked the Reported quantities are validated to prevent finishing without entering sufficient quantity information.  The Reported Good Qty + Reported Scrap Qty must be greater than or equal to the Expected Good Qty + Expected Scrap Qty or else a warning message is displayed and the Finish button is unchecked.

Fields

These are the values shown in the Activities grid and Activity dialog.

  • Name: (read-only) The identifier for the field.
  • Display Text: The text to display as the column header in the Activities grid and in the label in the Activity dialog.
  • Show InGrid: Whether to show the field as a column in the Activities grid.
  • Show In Dialog: Whether to show the field in the Activity dialog.
  • Sort Index: The sequence in which to show the columns in the Activities grid. Smaller numbers are shown further to the left.
  • Read Only: Whether the field should be editable in the Activity dialog. Note that this only applies to fields that are sometimes allowed to be edited. Many fields are always read-only and so this settings is ignored.

Material Fields

These are the fields in the Materials grid.

  • Name: (read-only) The identifier for the field.
  • Display Text: The text to display as the column header in the Activities grid and in the label in the Activity dialog.
  • Show In Grid: Whether to show the field as a column in the Activities grid.
  • Show In Dialog: Whether to show the field in the Activity dialog.
  • Sort Index: The sequence in which to show the columns in the Activities grid. Smaller numbers are shown further to the left.
  • Read Only: Whether the field should be editable in the Activity dialog. Note that this only applies for fields that are sometimes allowed to be edited. Many fields are always read-only and so this settings is ignored.

Buttons

  • Name: (read-only) The identifier for the button.
  • Display Text: The text to display in the button.
  • Visible: Whether to show or hide the button.

Groups

  • Name: (read-only) The identifier for the group box.
  • Display Text: The text to display in the group box caption.
  • Visible: Whether to show or hide the group box.

Tabs

  • Name: (read-only) The identifier for the tab.
  • Display Text: The text to display in the tab.

Labels

  • Name: (read-only) The identifier for the label.
  • Display Text: The text to display in the label.
  • Visible: Whether to show or hide the label.

Other

  • Activities Grid Caption: The text to display above the Activities grid.

System Options

These settings are applied to all Scenarios to control how Shop Views function.

  • Log users out automatically after long periods of inactivity: If checked, then if a Shop View is logged in and there is no mouse or keyboard activity for a period of time then the Shop View logs out.  This is to help increase security in cases where a user failed to logout.
  • Logout after __ of inactivity: Specifies the amount of idle time (no mouse or keyboard activity) after which the Shop View should logout.
  • Use Passwords for login to Shop Views: If unchecked then the password entry box is hidden during Shop Views login and passwords are not used. If checked then the password entry box is shown and passwords are validated against the User's password as specified in the User's dialog.
  • Use the Published Scenario instead of the Live Scenario for Shop Views: If checked then the data from the Published Scenario is used instead of the Live Scenario. (If there is no Published Scenario then the Live Scenario is used regardless of this setting.)