- Description: This setting is used to describe the dispatch type. It's best to be very specific.
- example: Code Red - Machine down not producing
- example: Code Yellow - Machine running at reduced capacity
- Color: This setting is used to set the background color of Dispatch Type field on the main dispatch screen.
- Code: This setting is used to set the 'Dispatch Type' code. Note: cannot be edited once saved.
- Active: Green means the Dispatch Type is Active. Clicking on the green button will turn it grey inactivating it.
- Impact to Production: This setting is used to select the Dispatch Types impact to production (Down, Impacting, Planned and No Impact). Note: Down Impact effects OA, OEE and Downtime totals on production dashboards and reports.
- Set Display Priority for Dispatch Types on Main Screen: This setting is used to set the sort order when sorting the dispatch type column from the main dispatch screen.
Create Dispatch Settings
- Start Down Time When Resource is Dispatched: This setting is used for special situations where machine downtime may not start until the time a resource(s) have actively started working on the issue. Check this box when response time does not impact machine availability.
- In each of these cases, the line or machine continues to run until the time that it is taken out of production to correct the problem
- For scheduled dispatch events that launch hours or days prior to the actual time of action and response time has no impact on machine availability.
- Allow Only One Dispatch per Machine Open Simultaneously: This setting is used to only allow one dispatch per machine for each Dispatch Type. If this option is selected and the machine already has open dispatch of the same type operator will receive "Machine is Already Down for Critical Dispatch Type". Note: If you plan on tracking resource utilization DO NOT CHECK THIS BOX!!!! Allowing resources to be on multiple events at same time will multiply their man-hours and give an incorrect view of how much time is being allocated.
- Available for Selection in New Dispatch Screen: Disabling this setting would remove the Dispatch Type from being selected in the New Dispatch Screen.
View Dispatch Settings
- Flag Dispatcher Until Dispatched: This setting is used to flag the dispatcher with visual and audible signal when new dispatch has been submitted. Note: not typically used for sites self-dispatching.
- Display Lines Downtime Cost on Dispatch Screen: This setting is used to display the cost of downtime on each dispatch on the main screen.
- Highlight on Critical Machine: This setting sets the dispatch screen background color to a hot pink color when dispatch type is selected for a critical machine.
Edit Dispatch Settings
- Users cannot add or remove documents from Dispatches: With this setting enabled, only an Administrator can add or remove documents within a Dispatch.
- Allow a Resource to be dispatched to multiple Dispatches of this Type simultaneously: With this setting enabled, a resource can be working on more than one call at a time.
- Enable Spares, Attached Tooling, Reason Codes, External Costs, Action & Component Codes, and Why Codes: These default to ON. With the setting disabled, the section for the corresponding name will not appear within the Dispatch.
Complete Dispatch Settings
- Automatically Launch Follow Up Dispatches on Completion: When a dispatch is completed (not closed), and a follow up dispatch type is specified in the dispatch type setup, launch a new dispatch as a follow up. You can select more than one dispatch type as a follow up.
Close Dispatch Settings
- Resource must be Dispatched Before Dispatch can be Closed: This setting requires a resource to be dispatched to an event before it will allow the event to be closed. This helps ensure accountability and accurate historical information
- Action/Component codes must be added before Dispatch can be closed: This setting requires Action & Component code entries before dispatch can be closed.
- A Reason Code must be selected before the Dispatch can be closed: This setting requires Reason code selected before dispatch can be closed.
- A Why Code must be selected when an Action and a Component are supplied to close a Dispatch: This setting requires the user to supply a Why Code.
Production Dispatch Settings
- Exclude from Production Status Dashboard: This setting excludes the dispatch type from being included on the Production Status Dashboards
- example: You may want to use this for dispatch types like Audit, FMEA Review, Part Order, Work Order, etc. that have no significant impact or status on production
- Available for Selection in Operator Portal: This setting allows the Dispatch Type to be selectable from the Operator Portal.
- Automatically launch Dispatch when a metric meets line threshold: Enabling this will provide a new section beneath to select lines and metrics that you want to launch a Dispatch. Launch Dispatch / Notification when Line meets set Metrics Threshold
We're now showing Related Items in the Dispatch Type Setup screen: Documents, Questions, Notifications, Areas, Work Order Categories, Actions, Components, Reasons, Why Codes, and Schedules. The arrow will take you to that section of Dispatch. This is an easy way to set up this information for the Dispatch Type as well as one place to view everywhere in the system a Dispatch Type touches.
The grey space to the right of the screen displays recent dispatches that have used that Dispatch Type in the last 24 hours, 7 days, and 30 days. Clicking on any of the recent dispatch numbers will bring you to a Time Trend Chart. Beneath the Recent Dispatches, you'll find Top Lines, Top Actions, Top Components, Top Reasons, and Top Why Codes for the past 30 days for that particular Dispatch Type. Clicking into any of those will bring you to an Occurrence Pareto with that data.
- Here's an example list of Dispatch Types
- Code Red - Machine Down not Producing
- Code Yellow - Machine Producing at Reduced Rate
- Material Shortage - Machine/Line down for lack of material
- Jikoka - Machine/Line down for quality concern
- Engineering Red - Machine/Line down for engineering
- Safety Red - Machine/Line down for safety concern
- Kaizen - Employee improvement suggestion
- PM - Preventative Maintenance
- TPM - Total Production Maintenance
- Cal - Equipment Calibration
- Changeover - Product Changeover/Setup
- WO - Maintenance Work Order
- RCA - Root Cause Analysis
- PFMEA - PFMEA audit or review
- 5's - Scheduled cleaning
- Shutdown - Scheduled Line Shutdown
- Mod - Equipment Modification