FAQs

Within L2L we have a site hierarchy. You have an Area/Line/Machine.  Every Machine has to be assigned to a line Line and every Line is assigned to a Specific Area.  Within Area Settings you will see a 'default dispatch type', therefore whenever you select a machine or line it will default to the Area Dispatch Type the Line or Machine belongs to. 

Often times customers will Save and Schedule reports but can not find a users name to include as a recipient.  You know the operator is in the system and can select him for other functions but is not showing in the reports section. The first thing to check is does the user have an email address listed and if so is it correct.  If you have checked this check out our Save and Scheduled Reports article under Trouble-Shooting for more tips. 

You clicked on your Dispatch Menu and you now only see 3 options.  This happens when the Dispatch Portal set as Default View.  You can edit this under your User Settings.  

Are you trying to dispatch a Resource by their names not appearing as an option?  This often happens when the Resource has marked themselves as 'unavailable' on their home screen.  Check out this article for more. 

Due to the way our system is structured, a machine can only be assigned to one line, and a line can only be associated with one area. This means that we are unable to customize the process to allow for selecting an area when creating a dispatch with the machine and line selected, as it will automatically default to the area the line/machine is associated with. In order for an area to be the "default" the machine would have to be assigned to the line in that area.

Generally, a safe limit is 1 post to the "pitchdetails/record_details/" method per minute, per line.
Staggering the posts by multi-threading is not a problem, provided that posts are not more frequent than once per minute, per line. 
It shouldn't be a problem to run a single thread per line and have them run asynchronously, as long as each thread doesn't post more frequently than once per minute. 
If you find that your integration is regularly posting a backlog of pitch details in rapid succession, consider using the "pitchdetails/record_details_batch" method to send the backlog of pitch details. This method allows you to send pitch details to many different lines, with unique part counts and unique start and end timestamps, all in a single post. It is not instantaneous, since it takes time to update many records, but it could help make your integration more efficient. 

You are a user or a resource and have been granted permissions under Admin Security Settings such as Resource Manager, User Manager, API Manager, System Manager, or IT Manager but still get kicked out when trying to perform those tasks associated.  The reason this happens is you need to be an Administrator with Admin Security Setting Permissions in order to do so.  A user or resource with these permissions will not perform that way. He is an article on our Comprehensive Guide to Access in L2L

Currently, links to Dispatches are not always included in every Notification.  Under notification format you can choose what you want included in the notifications, however Dispatch link is included with Assigned Resource Notifications and with Dispatched Resource Notifications only at the present time.
When setting up notification formats to include links you have 3 different types of notification 1. Downtime, 2. Assigned Resources or 3. Completed. Once you have selected one of those, you have the option to select what you would like to include in your notification email and the link options is available for all three of those options.

The work order status does affect how the work order will launch into dispatch. Work orders that are in a 'New' status and have not been approved will not launch. Additionally, approved work orders that have been set to a New status such as "Read to Schedule" may also prevent the work order from launching. Once a Work Order is Approved you should set this to Scheduled. 
Additionally, work orders will not launch if they are in 'Reviewing' or 'On Hold' status.

Are you receiving an error that says Machine Already Has Open Critical Dispatch, but you do not have one open? This happens when you have any dispatch types with the setting "only one dispatch allowed per machine one at a time" this error will happen as this is not just restricted to just code reds. To troubleshoot, check your open dispatches against your machines and then check their dispatch type setup to see if the below option is selected, if so turn that off. 

• Allow Only One Dispatch per Machine Open Simultaneously: This setting is used to limit 1 critical Dispatch Type against a machine at any given time. 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". This setting essentially marks the Dispatch Type as critical.

You need to have Production Planner Permission under Production settings in order to load pitch schedules. 

To cancel a scheduled report that was set up by another user, you will need to have the appropriate permissions to manage scheduled reports. If you have these permissions, you can navigate to the scheduled reports section in your account settings and locate the specific report with the subject.  If you do not have administrator permissions, you can request the creator of the report cancel this or remove your name from the list. 

By selecting a specific checkbox in the reports section, you can view only the specified information you wish to view from the report you are running. Each checkbox will narrow or broaden the search scope requested from the report. By using the checkbox functions, you can review more precisely the information you hope to obtain from the History Report.  However, it is important to Note: You can only run one checked option at a time, otherwise you may return with "no data showing."  To see everything, do not check any boxes.  

You have created resource shifts and a pitch template but it is not pulling into the Op Portal.  A couple of things to check. 1. Are your shifts set up completely and make sure there are no overlapping times. (i.e. if you have a shift running from 00:00-00:00, it would need to be 00:00-23:59 so it does not overlap into the next day) 2. Does the schedule pitch template match my shift times i.e without overlapping times. If you have overlapping time it will not pull the template into the Op Portal.