Bundle-Track 3.6
User’s Guide
The information in this document is subject to change without notice and does not represent any warranty on the part of Latitude Business Systems, Inc. The software described in this document is furnished under a license agreement that accompanies this manual, and may be used or copied only in accordance with this agreement.
Copyright © 2001 Latitude Business Systems, Inc.,
All Rights Reserved August, 2001
Table of Contents
Save,
Cancel, and Close Buttons in Setup Options areas
Overview of General Setup Sub-Areas
Pay Group
Controls – General tab
Pay Group
Controls – History Data Control tab
Premium
Rules Controls – General tab
Premium
Rules Controls – Overtime tab
Premium
Rules Controls – Shift Control tab
How
Bundle-Track Handles Overrides to Pay Rates
Pay Rates
Controls – General tab
Pay Rates
Controls – History Data Options tab
Pay Rates
Controls – Advanced tab
Overview of Product Setup area
How Custom
Lot Fields are Used
Custom Employee Fields (Network Version only)
Overview of the Operations area
Save,
Cancel, and Close Buttons in the Operations area
Multi-Operations (Network Version only)
Products
Controls – General tab
Products
Controls – Colors tab
Products
Controls – SKU Codes tab
Products
Controls – Routing tab
Elements
of the Routing Screen
Adding
Sections to the Routing
Removing
Sections from the Routing
Re-Sequencing
Sections within the Routing
Moving
Steps to Another Section or Another Stage
Introduction to Pay Conditions
Pay
Condition editor – General tab
Pay
Condition editor – Properties tab
Pay
Condition editor – Associated Rates tab
Pay
Condition editor – Standards tab
Employee
editor – Special Pay tab
Employee
editor – Custom Fields tab (Network Version only)
Makeup Set
Editor – Makeup Sets tab
Makeup Set
Editor – Properties tab
Makeup
Sets Editor – Member Pay Conditions tab
Cut Planning – the Cut Entry tab in Edit
Status
Leaving
Edit Status is Permanent
Ticket Printing – the Cut Entry tab in
Print-Ready Status
Print
Controls in Bundle Set View
Print
Controls in Spreadsheet View
Print
Controls in View Bundles Sequentially View
Leaving
Print-Ready Status is Permanent
Introduction to Production Entry – the
Production panel
Selecting
a Target Employee, Team, or Department
Accessing
the Production Panel
Production Entry – Bundle Tickets tab
Viewing
and Changing Unsized Rates throughout the Lot
Scanning a
"Variable" Rate Type (Network Version only)
Production Entry – Adjustments tab
Production Entry – Operations tab
Production Entry – Multi-Operations tab
(Network Version only)
Production Entry – Lot Ops tab (Network
Version only)
System Overview
Thank you for reading this manual.
One of the first things you should know about this manual is that it documents both the Desktop and Network versions of Bundle-Track 3.6. Some features described here are available only in the Network version. This will be pointed out in the text as necessary.
Starting Bundle-Track 3.06
Before your run the main Bundle-Track program for the first time, you must run Bundle-Track Links to let Bundle-Track configure the connection to its database. After this has been done, you do not need to run Bundle-Track Links to start Bundle-Track. (See the Bundle-Track Installation Guide for details.)
Start Bundle-Track as follows:
1. Double click the Bundle-Track shortcut on your desktop, or select StartŢProgramsŢBundle-TrackŢBundle-Track.
2. At the login prompt, enter your username and password. (Initially, the username is “sysdba” and the password is “masterkey”.)
3. Select the database you want to work with – either the Production or Test database.
4. Click OK to enter Bundle-Track.
Once Bundle-Track has connected itself to the database, it will display its main screen, giving you access to the main Tool Bar and Menu.
InterBase Server Manager Must be Running
If your password keeps being rejected, it might mean that InterBase Server Manager is not running. You need it to be running to support Bundle-Track. Try starting it: select StartŢProgramsŢInterBaseŢInterBase Server Manager. The panel indicates whether it is already Started or Stopped. If it was Stopped, start it. This may solve your problem. (At the top of the panel, you can set the Server Manager to start automatically when your computer is turned on.)
Changing Login Details
Users of the Desktop Version may not change the username, but may change the password. Instructions are found in the InterBase manual.
Users of the Network Version may use the Bundle-Track Roles application (not provided in the Desktop Version) to change the username and password and to create other user accounts. Refer to the “Bundle-Track Roles User’s Guide” for details.
Arrangement of Functions
Most of Bundle-Track’s functions are grouped into functional areas as follows:
|
Setup (p. 7) |
Engineering and human resources information that will be essential to processing data: information about the people working in your factory and how you pay them, and information about the Products you make and how you make them. |
|
Activities (p. 57) |
Tasks that users perform on a day-to-day basis: initiating production Lots, printing Bundle Tickets, updating Bundle information, and performing system maintenance. |
|
Database Administration (p. 81) |
Remove History Data. Compress the database. |
|
Printer Setup (p. 82) |
Just that. |
|
Help |
Online Help. |
Interface Basics
Moving through Forms
By Mouse
The mouse allows you to click from field to field to enter the information you wish in any order you wish.
By Tab Key
Pressing the Tab key will move you through the fields and buttons on the form in a programmed “tab order.”
By Enter Key
Pressing the Enter key will activate the highlighted Form Tool. This will usually be SAVE unless you have used the Tab key to highlight another button.
Code and Description Fields
Almost every record in Bundle-Track has a Code field and a Description field. Almost all of them have the same characteristics:
|
Code |
Required. Up to 15 characters. |
|
Description |
Optional. Up to 30 characters. |
We won’t bother you with these again, unless there is a notable exception.
Setup
To ready Bundle-Track to serve your factory, you must provide the system with engineering and human resources information that will be essential to processing data: information about the people working in your factory and how you pay them, and information about the Products you make and how you make them. You will input and maintain this information in Bundle-Track’s Setup area.
Setup Sub-Area Overview
The Setup area is divided into sub-areas which you access by clicking through the Setup Menu, or by clicking on one of the Setup buttons:
Figure 1. Setup Buttons
Setup Areas
|
· General Setup (p. 10) · Product Setup (p. 27) · System Tables (p. 29)
|
System settings that allow you to configure Bundle-Track to match your factory’s methods for things like engineering Units and Pay Rates. |
|
(p. 31) |
Lists and groupings of the various assembly tasks performed by your Employees and associated Rate information. |
|
(p. 36) |
Lists and groupings of the various Products assembled in your factory. |
|
(p. 46) |
Employees, Pay Conditions, and Schedules. |
Save, Cancel, and Close Buttons in Setup Options areas
The General Setup, Product Setup, and System Setup areas are all Setup Options areas. In all three of these, you will note that the same Save, Cancel, and Close buttons are visible in the right-hand side of the area, no matter what data is currently featured on the panel. It is important to note that these buttons take action on the entire area as a whole, not only on the currently visible data.
Save Button
The Save button writes the current settings to the database.
Note that the General Setup area’s tree view may not immediately reflect changes to Codes. This does not mean that Save did not work. If you change the Code of a Shift, for example, and Save this change, you will not see the change in the tree view until you close and re-open the Shift folder in the tree view, or until you close and re-open the General Setup area.
Cancel button
The Cancel button reverts all changes made since your last Save, not only those currently visible.
Because there are so many details you can change within a Setup area, we recommend that you make a habit of saving your changes in each sub-area before moving on to the next. In this way, you will keep the amount of unsecured changes small and protect yourself against canceling more changes than you intended.
Close button
The Close button closes the area.
If there are any unsaved changed in effect when you click Close, you will be prompted to save or cancel them before the area will close.
Options: General Setup
When you are ready to begin your set-up of Bundle-Track, the first place to go is Options: General Setup to tell Bundle-Track about your plant.
To access this area, either menu-select SetupŢOptionsŢGeneral Setup,
or click 
and select General Setup.
Overview of General Setup Sub-Areas
The General Setup form presents a tree view on the left, and a work area on the right. The form works much like your computer’s Windows Explorer application – you can open and close folders in the tree view on the left, and the right window shows the contents of the item currently selected in the tree view on the left.
The tree view offers access to the following sub-areas:
· Currency Settings (page 11)
· Plant Description (page 11)
· Departments (page 11)
· Teams (page 13) (Network Version only)
· Shifts (page 14)
· Pay Groups (page 15) (Only one Pay Group in Desktop Version)
· Premium Rules (page 16)
· Unit Settings (page 19) (Only one Unit Setting in Desktop Version)
· Rate Types (page 20) (Only one Rate Type in Desktop Version)
· Pay Rates (page 21)
· Operation Base Rates (page 24)
· Ticket-Scanning Settings (page 24)
When you click on any of these items in the tree view (the left side of the form), the corresponding work area is displayed on the right.
Currency Settings
In this area, you will tell Bundle-Track which Currency is used in your plant.
Selecting a Currency
1. Click on Currency Settings in the tree view to access the Currency Settings area.
2. In the work area (on the right), click on the Country dropdown to display the available Countries and click on the selection that is appropriate for your factory. (If your country is not listed, you may add it to the System Tables. See page 32.)
3. Click on the Currency dropdown to display the available currencies and click on the selection that is appropriate for your factory. (If your currency is not listed, you may add it to the System Tables. See page 31.)
Plant Description
When you click on Plant Description, you’ll reveal the Plant Description fields. These details are optional.
Departments
Having Departments lets you organize your Employees and their activities into cost centers. This lets you generate measurements and reports by Department on payroll amounts, productivity, excess labor costs, etc., and to answer questions like, “How much Machine Down time was there for each Department” or “Which Department had the highest overtime expenses.”
How Departments are Used
· Employees are assigned to Home Departments (under the Setup sub-area called “Personnel & Pay”).
· Every Event record specifies a charged Department (and Latitude Business Systems can use this information to build custom Pay-rules to calculate departmental incentives.).
· Some Reports may be ranged by Department.
Department Controls
When you highlight the Departments folder, you reveal a table that lists the currently defined Departments. You can then add, edit, or remove Departments.
If you access the Department editor for an individual Department – whether by clicking the Add or Edit buttons under the Department table, or by expanding the Department folder and clicking on an individual Department – you will see the full set of Department fields:
|
Shift |
Required. Select from the dropdown. When an Employee is assigned to this Department, the Shift specified here will be assigned to that Employee by default. You will be able to override this assignment on the Employee form (page 50). |
|
Pay Group (Network version only |
Required. Select from the dropdown. When an Employee is assigned to this Department, the Pay Group specified here will be assigned to that Employee by default. You will be able to override this assignment on the Employee form. |
Adding Departments
1. Highlight the Departments folder in the General Setup tree-view.
2. Click the Add button.
3. In the form, enter a unique Code for the new Department.
4. Optionally, enter a Description for the new Department.
5. Select a Shift.
6. Select a Pay Group. (Network Version only.)
Editing Departments
1. Access the Department record you wish to edit:
a. Highlight the Departments folder in the General Setup tree-view.
b. Highlight the Department record you wish to edit.
c. Click the Edit button.
-Or-
d. If there is a + next to the Departments folder, expand the folder by clicking the +.
e. Highlight the Department record you wish to edit.
2. Edit the information in the form.
Removing Departments
1. Highlight the Departments folder in the General Setup tree-view.
2. Highlight the Department record you wish to remove.
3. Click the Remove button. Bundle-Track will ask whether you really wish to remove the record.
4. Click Yes to remove the record.
Note: You cannot remove Departments that currently have Employees assigned to them, or that have been charged in any Event in the current Pay Period. To remove a Department that has been in use, you must first reassign any related Employees to other Departments, and ensure that no Events throughout the entire Pay Period are charged to the Department.
Identifying Department Dependencies
You can get a list of all Employees who are currently assigned
to a Department (and, optionally, those who transferred into it during the
Pay Period) by clicking the Ellipsis button (
) next to
the Description field on a Department’s details page.
Teams (Network Version only)
You’ll notice that each Department record in the tree view can be expanded further to reveal a Team folder for each Department.
You may define Teams within each Department. A Team is a group or team of Employees within a Department.
How Teams are used
· Employees are assigned to Teams (under the Setup sub-area called “Personnel & Pay”).
· Pay-rules may be defined to calculate Team incentives.
· You can compensate Teams based on the output of the group.
Team Controls
Highlighting the Teams folder reveals an editor for creating and maintaining Teams. This editor works just like the Department editor.
When you select an individual Team, you will see all of its fields:
|
Shift |
Required. Select from the dropdown. The Team inherits its Department’s default Shift, but you can override the Department default. When an Employee is assigned to this Team, the Shift specified here will be assigned to that Employee by default (overriding the Department’s default Shift). You will be able to override this assignment on the Employee form. |
|
Pay Group |
Required. Select from the dropdown. The Team inherits its Department’s default Pay Group, but you can override the Department default. When an Employee is assigned to this Team, the Pay Group specified here will be assigned to that Employee by default (overriding the Department’s default Pay Group). You will be able to override this assignment on the Employee form. |
Adding Teams
1. Expand the tree-view for a Department to reveal its Teams folder.
2. Highlight the Teams folder to see the editor.
3. Click the Add button.
4. In the form, enter the Code for the new Team record.
5. Optionally, enter a Description.
Identifying Team Dependencies
You can get a list of all Employees who are currently assigned to a Team (and, optionally, those who charged to it during the Pay Period) by clicking the Ellipsis button next to the Description field on a Team’s details page.
Shifts
You define Shifts and Shift Premiums here.
How Shifts are Used
· Employees are assigned to Shifts (under the Setup sub-area called “Personnel & Pay”).
· Every Event record specifies the charged Shift.
· Pay-rules may be defined to calculate Shift Premiums.
Shift Controls
If you access the editor for an individual Shift, you will see the full set of Shift fields.
Premium Method
If you don’t want this Shift to pay Shift Premiums, leave the text field in this area blank. Otherwise, select from the radio buttons and set a value in the text field accordingly:
|
Percentage |
The Shift Premium Rate will be calculated as the specified percentage of the Overtime Basis (as defined on the Overtime tab). Format note: specify 10% as “10”, not “0.1”. |
|
<Currency> per hour |
(The label changes according to your Currency Settings.) The Shift Premium Rate will be simply the currency amount specified in the text field, per hour. |
Apply Shift Premium to Overtime
If this box is not checked, the Shift Premium has no effect on the Overtime Premium.
If this box is checked, the Shift Premium is added to the Overtime Basis before the Overtime Premium is calculated.
See Premium Rules Controls – Overtime tab, page 17, for more about the Overtime Basis.
Pay Groups
This is where you tell Bundle-Track some simple things about your fiscal year. Bundle-Track uses this information to organize data into Pay Periods for reporting and data storage purposes.
Note to users of Desktop Version: you can have only one Pay Group.
Pay Group Controls – General tab
|
Number of Days per Period |
Enter the number of days in a Pay Period. If you process weekly, enter 7. If bi-weekly, then 14. Bundle-Track automatically advances the Current Period Close Date by this many days when you close a Period. |
|
Current Period Close Date |
Enter a date (MM/DD/YY) or use the calendar button to specify the date on which the current Pay Period will close. Bundle-Track automatically advances the Current Period Close Date when you close a Period. |
|
Current Period Number |
Enter the number of the current Pay Period. This number will automatically increment at the close of each Pay Period. After you close the last Period of the fiscal year, you must manually reset this number. |
Pay Group Controls – History Data Control tab
|
Keep Ticket Detail for __ Periods |
Bundle-Track stores the detail of every Bundle Ticket for a limited time. The maximum is 4 periods. You may specify a shorter time. Ticket Detail beyond the specified limit is purged when the database is compressed, but summary Ticket information is retained. |
|
Compress Data Automatically |
To keep the database healthy, the database should be compressed regularly. If you check this box, Bundle-Track will do this automatically for this Pay Group when you close a Pay Period for this Pay Group. If you leave this unchecked for any Pay Group, you should compress the database manually at least once a month (see Compress Database, page 81). Occasionally, there is a practical reason to suppress automatic compression, but generally, we recommend that you leave this option checked. |
Pay Group Controls – Members
The table on this tab lists all Departments, Teams, and Employees assigned directly to this Pay Group. It is read-only (cannot be edited).
Premium Rules
Premium Rules define how Overtime and Shift Premiums are to be calculated.
Each Employee is indirectly assigned a Premium Rule: each Employee is actually assigned a Home Pay Condition, and that Pay Condition belongs to a Pay Condition Group, which is assigned to a Premium Rule. All work the Employee does is subject to the rules defined in the Premium Rule record assigned to the Pay Condition Group under which the Employee’s Home Pay Condition belongs.
Premium Rules Controls – General tab
This tab holds only the Code and Description fields.
Premium Rules Controls – Overtime tab
This tab houses the controls for telling Bundle-Track how to calculate Overtime Premiums for Events whose Pay Conditions are assigned to this Pay Condition Group.
Overtime Basis x Overtime Factor = Overtime Premium
Here’s how Bundle-Track calculates Overtime Premiums. An hourly Rate called an Overtime Basis is computed according to the rules you specify. That Basis is then multiplied by the Factor you specify, and the result is an Overtime Premium.
Overtime Premiums are paid on top of regular pay for the same time period. So, to pay the conventional “time and a half”, you set an Overtime Factor of 0.5 to generate an Overtime Premium that represents the “and a half” part. For “double time”, set a Premium Factor of 1.0.
What “Overtime Eligible” means
If hours are called Overtime Eligible, it means that, for the purposes of comparing hours worked against the overtime threshold, those hours count, no matter whether they are actually worked hours or not.
Suppose it is your policy to pay overtime for any time over 40 hours in a week. That’s a 40-hour Weekly Threshold. If someone works 45 hours, 5 of those hours count as Overtime Hours. Suppose instead of working on Monday, they take a paid Vacation day (8 hours), and they put in 37 hours later in the week. If you call those Vacation hours Overtime Eligible, then the worker has 45 Overtime Eligible hours to compare against the 40-hour threshold, and that makes 5 Overtime Hours. If you do not consider Vacation hours Overtime Eligible, then the worker has only 37 Overtime Eligible hours in the week, and despite the longer hours on the non-Vacation days, the worker gets no Overtime.
Typically, Extended or Unexcused absences are considered not Overtime Eligible.
Specifying the Overtime Rule
Use the Overtime Rule dropdown to specify how Bundle-Track will differentiate between Regular Hours and Overtime Hours under this Premium Policy:
|
(No overtime rule) |
Bundle-Track will always set Overtime hours to zero and will not calculate Overtime Premiums. (When this is selected, the Threshold and Factor fields on this form will be hidden, and the setting of the other radio buttons will have no meaning.) |
|
Single - Based on Daily Hours |
Any hours beyond the threshold in a given day are Overtime Eligible. |
|
Single - Based on Period Hours |
Any hours beyond the threshold in a Pay Period are Overtime Eligible. Hours worked in an individual day do not matter. |
|
Double - Daily Hours and Sunday |
Two overtime rules are in effect: any hours worked on a Sunday are Overtime Eligible, regardless of any other hour count; and any non-Sunday hours beyond the threshold in a given day are Overtime Eligible. |
|
Double - Period Hours and Sunday |
Two overtime rules are in effect: any hours worked on a Sunday are Overtime Eligible, regardless of any other hour count; and any non-Sunday hours beyond the threshold in the Pay Period are Overtime Eligible. |
|
Overtime hours are imported |
This option is supported only if you have the Bundle-Track Import Utility software (not standard). Bundle-Track itself will not identify Overtime Hours. Instead, some other system will determine the number of Overtime hours. Bundle-Track will then import the Overtime Hours information and calculate Overtime Premiums accordingly. Further details are provided with the Import Utility software. |
Setting the Threshold and Factor with Single Threshold Rules
If you select a Single Threshold Overtime Rule, you will see a Threshold field and a Factor field.
In the Threshold field, you must specify the number of hours in the Day/Period (depending on the selected Overtime Rule) that must be logged before subsequent hours are Overtime Eligible.
In the Factor Field, you must specify the amount of the Overtime Premium in terms of a multiple of the Overtime Basis.
Setting the Threshold and Factor with Double Threshold Rules
If you select a Double Threshold Overtime Rule, you will see two sets of Threshold and Factor fields. The first set will work just as described above for Single Threshold Rules. The second set will apply only to hours worked on a Sunday.
The second Threshold field, you will note, reads “Sunday” and is not editable.
In the second Factor Field, you must specify the amount of the Sunday-specific Overtime Premium in terms of a multiple of the Overtime Basis.
Setting the Basis for On-Standard Events
If you have selected “(No overtime rule)” from the Overtime Rule dropdown, you can ignore all other controls on this tab. Otherwise, select one of the three options under “Basis: On-Standard Events” to specify how the amount of the Overtime Basis will be determined for on-standard Events:
|
Daily On-Standard Average |
Considers only incentive-based earnings within the Day. Divides the Employee’s total incentive-based earnings for the day by total worked hours in the day to get the average incentive-based Rate for the day. |
|
Period On-Standard Average |
Considers only incentive-based earnings within the Period. Divides the Employee’s total incentive-based earnings for the Period by total worked hours in the Period to get the average incentive-based Rate for the Period. |
|
Period Total Earnings |
Divides the Employee’s total earnings for the Period (including on-standard Ticket totals, adjustments, make-up, and any off-standard or hourly pay) by total worked hours in the Period (both straight time and overtime) to get the average Rate for the Period. |
Setting the Basis for Off-Standard Events
If you have selected “(No overtime rule)” from the Overtime Rule dropdown, you can ignore all other controls on this tab. Otherwise, select one of the three options under “Basis: Off-Standard Events” to specify how the amount of the Overtime Basis will be determined for off-standard Events:
|
Event Condition Pay Rate |
A Premium is calculated for each Event. The Basis is simply the pay Rate prescribed by the Pay Condition charged in the worked Event. |
|
Home Condition Pay Rate |
The Basis is simply the pay Rate prescribed by the Employee’s Home Pay Condition, regardless of the Pay Condition charged in any worked Event. |
|
Period Total Earnings |
Divides total earnings (both on-standard and off-standard) for the Period by total worked hours in the Period to get the average Rate for the Period. |
Premium Rules Controls – Shift Control tab
You must select one of these two options:
|
Always Pay Home Shift Premium |
No matter what Shift is charged, pay the Shift Premium defined for the Employee’s Home Shift for all hours worked. |
|
Always Pay Charged Shift Premium |
For each Event, pay the Shift Premium defined for the Event’s charged Shift. |
Unit Settings
Here you define the engineering units for the operations used in your factory. Whether you assign production value in terms of dollars per unit, per dozen, or per some other standard quantity, or in standard minutes per units or standard hours per hundred, Bundle-Track can process and report information accordingly.
Note to users of Desktop Version: you can have only one Unit Setting.
|
Money-Based Rates |
In this area, you
define the units for Money-Based Rates. The numerator will always be your
factory currency (as specified in Currency Settings). You must specify a
“Per” Unit for the denominator by selecting it from the dropdown. |
|
Time-Based Rates |
In this area, you define the units for Time-Based Rates. For the numerator, you must select a standard time unit. For the denominator, you must select a “Per” Unit. |
Note: You cannot remove a Unit Settings record while there are Rate Types defined under it. To remove a Unit Settings record, you must first remove all Rate Types under it.
Rate Types
You’ll notice that each Unit Settings record in the tree view can be expanded further to reveal a Rate Type folder for each Unit Setting. You may define Rate Types for each Unit Setting.
Note to users of Desktop Version: you can have only one Unit Setting and only one Rate Type – called Piece Ticket – which you cannot view or edit. The details of that Rate Type are pre-set to serve a typical Piecework environment.
How Rate Types are Used
Each Operation is assigned a Rate Type. Each Rate Type carries attributes that determine whether a Ticket is printed for each Operation, with or without a bar-code, how the operation is valued, and whether confirmation is required at scan time.
Printing and Scanning options
Note to users of Desktop Version: These options are pre-set for you.
|
Print Ticket |
If this is checked, all Operations associated with this Rate Type will generate Tickets. A Rate Type that leaves this option unchecked might be useful for Operations that that contribute to overall unit cost but are not involved in payroll calculations. Desktop Version: this is checked. |
|
Print Bar Code |
If this is checked, all Operations associated with this Rate Type will generate Tickets with bar-codes on them. Desktop Version: this is checked. |
|
Stop at Scan |
If this is checked, when an Operation associated with this Rate Type is scanned, a confirmation panel will pop up and prompt the user for the production quantity. This is useful where production volume makes it impractical to pull a Ticket for each Bundle. Instead, operators can count the units processed and report this quantity in summary on one Ticket. Desktop Version: this is not checked. |
Rates Multiplied By options
Note to users of Desktop Version: This option is pre-set for you.
|
Count in Bundle |
If this is selected, when an Operation associated with this Rate Type is scanned, the production quantity will default to the number of units in the Bundle. Desktop Version: this is selected. |
|
One (Flat Rate) |
If this is selected, when an Operation associated with this Rate Type is scanned, the production quantity will default to one (1). |
|
Other |
If this is selected, when an Operation associated with this Rate Type is scanned, the production quantity will default to the value specified in the text box next to this option. |
Pay Rates
This is where you define a library of standard Pay Rates. As you later define pay rules, you will specify the Rates that should be used by selecting from the Pay Rates you define here.
How Bundle-Track Handles Overrides to Pay Rates
It is important that you understand that Bundle-Track allows overrides to a Pay Rate’s natural value, and that you understand how the proper Rate is selected.
When Bundle-Track is directed to use a given Pay Rate, it follows a procedure to locate the proper value for that Rate under the given circumstances. The details at issue are the Pay Condition involved, and the Employee involved.
1. Bundle-Track first checks the Employee’s Special Pay settings (page 51). If the Employee has a special Rate assignment there for the Pay Rate at issue, then Bundle-Track accepts the Employee’s special Rate and stops searching.
2. If the Employee has no special Rate for the Pay Rate at issue, Bundle-Track checks the Pay Condition for an override. If it finds one there, Bundle-Track accepts the Pay Condition’s override Rate and stops searching.
3. Finally, if there is neither an Employee special Rate, nor an override in the Pay Condition, Bundle-Track uses the Pay Rate’s natural value – the one defined here in the General Settings area.
Pay Rates Controls – General tab
The Rate field lets you specify a global fixed value for this Pay Rate.
If you are going to define this Pay Rate’s value directly under each Pay Condition, or make it a calculated rate that is different for each Employee, you may leave this value blank.
Pay Rate Dependencies
By clicking the
Ellipsis button (), you call
up a Cross Reference panel that lists all Pay Conditions referencing the Pay
Rate and identifies the context in which each reference is made:
· A check in the Hourly column indicates that the Rate is specified as the Pay Condition’s Hourly Rate (see Pay Condition editor – Associated Rates, page 48).
· A check in the Base Rate column indicates that the Rate is specified as the Pay Condition’s Base Rate (see Pay Condition editor – Standards, page 48).
· If either Rate has an override specified at the Pay Condition level, the overriding value will be shown in red.
Pay Rates Controls – History Data Options tab
Rather than setting a fixed Rate, you can make Bundle-Track calculate the value of a Rate independently for each Employee, based on historical data, so that the value can be Employee-specific and can change over time.
Calculate using history data
Mark this box if you want Bundle-Track to calculate the Rate automatically, based on historical data. If you leave this unmarked, Bundle-Track ignores the rest of the controls on this tab.
Calculate automatically after Period close
Mark this box if you want Bundle-Track to update the Rate’s values when you close a Pay Period.
If the Rate is to be based on a date range that does not renew with each pay Period – such as a quarterly average – you should leave this unmarked and instead invoke the calculation manually when appropriate. (See Updating Employee Averages, page 78.)
Data Range options
You may select only one of these two options.
|
Rolling date range |
If this is checked, you must specify a number of Pay Periods in the text box on that line. Bundle-Track will base its calculations on data spanning that number of Periods. |
|
Fixed Date Range |
If this is checked, you must specify a range of dates (MM/DD/YY) in the text boxes on that line. Bundle-Track will base its calculations on data spanning those dates. |
Performance Measure options
You may select only one of these two options.
|
On-Std Earned Rate |
With this selected, the Pay Rate will be valued at the average of the Employee’s on-standard earnings. |
|
Total Earnings (less overtime premiums, bonuses) |
With this selected, the Pay Rate will be valued at the Average of the Employee’s total earnings, including on- and off-standard earnings and adjustments, but excluding Overtime Premiums, Shift Premiums, and bonuses). |
Pay Rates Controls – Advanced tab
Hours worked per Period
If the History tab’s Data Range option is set to Fixed Date Range, this field is ignored.
If the Data Range option is set to Rolling Date Range, this value sets the minimum number of hours an Employee must have worked in a Period for that Period to be eligible for inclusion in the calculation of the Employee’s Rolling Date Range average.
For example, if the Hours Worked Per Period field is set to 32 hours, then Bundle-Track bases its average only on Periods in which the Employee worked at least 32 hours. If the Rolling Date Range specifies that the average will be based on 6 Periods of data, and two recent Periods found the Employee working fewer than 32 hours, then Bundle-Track will skip over those two Periods and look to the 7th and 8th historical Periods to come up with a total of 6 qualified Periods.
Set the minimum number of worked hours you require for a Period to be worth including in a data sample.
Hours worked per calculation
This field determines whether the selected date range contains enough hours to be considered a valid data sample.
No matter whether the History tab’s Data Range option is set to Fixed Date Range or to Rolling Date Range, if the number of hours the Employee worked in the selected date range is fewer than the number of hours specified in this field, the data sample will be deemed invalid and the Pay Rate will not be updated.
Set the minimum number of worked hours you require in a data sample before a Rate may be recalculated.
Operation Base Rates
Operation Base Rates assigned to Operations enable conversions between time values and money values.
In time-based pay systems, Operation Base Rates are used to convert earned time to earned pay. When using currency-based Rates to calculate pay, Operation Base Rates are used to convert earned money to earned time, enabling the system to calculate an Operation’s standard (100%) efficiency Rate and an Employee’s actual efficiency. (Exceptional operators will exceed 100% efficiency.)
Operation Base Rates Controls
Rate
Specify the currency per hour Rate in terms of the Currency selected in the Currency Settings area.
Operation Base Rate Dependencies
By clicking the Ellipsis button (), you call
up a Cross Reference panel that lists all Operations that reference the Operation
Base Rate.
Ticketing-Scanning Settings
Here you specify how you want to enter Cut Ticket quantities, how those quantities will be displayed on Bundle Tickets, and other information about the ticket paper and Bundle Ticket layout.
Cut Entry tab
These settings affect the entry of production quantities for a Cut.
Units
Though your Rates may be engineered in Dollars per UNIT, your production planning and data entry personnel may be used to operating in terms of Dollars per DOZEN or some other “Per” Unit.
The Units dropdown lets you specify the “Per” Unit that will apply to the quantities you specify when you are planning a Cut. (See Cut Planning – the Cut Entry tab in Edit Status, page 61.)
Example: If DOZEN were selected, then a Cut quantity entry of 1 would mean 12 units, and 3 would mean 36 units. If UNITS is selected, or any other item with a divisor of 1, then the Cut quantity is valued at face value: 12 = 12 and 36 = 36.
Enter Fractions As
Actual production quantities may not always neatly fit the “Per” Unit that you have specified in Cut Entry Quantities. For example, you may have set Cut Entry Quantities to DOZEN (12 units) and you may need to schedule the production of 15 units. Since 15 does not neatly fit the DOZEN unit, you must decide how to represent this quantity.
The Enter Fractions As radio buttons let you tell Bundle-Track how you want to input production quantities. Pick the one that is most convenient for your users.
|
No fractions |
When you are entering Cut quantities, you may enter integers only. Bundle-Track will not allow you to use the decimal point. You will be strictly constrained to the “Per” Units you have chosen in the Cut Entry Quantities dropdown. |
|
Decimals |
When you are entering production quantities, you may enter decimal fractions. You must calculate the proper fraction to represent the actual production quantity, using the formula (Actual Production Quantity) / (“Per” Units value) = (Cut Quantity). For example, if Cut Entry Quantities is set to DOZEN (12 units) and you have actual production of 15 units, you must calculate 15 / 12 = 1.25. Your Cut Quantity is 1.5. |
|
Remainders |
When you are entering production quantities, Bundle-Track will expect you to use the “whole and remainder” method. It will interpret the Cut Quantity value you enter as a two-part piece of data – whole “Per” Units to the left of the decimal point, and extra single units to the right. For example, if Cut Entry Quantities is set to GROSS (144 units), a Cut Quantity of 2.25 means “Two GROSS and 25 singles.” |
Matrix Comparison of Sample Calculations
|
|
1.5 DOZEN |
2.25 GROSS |
|
Decimal: |
1.5 x 12 = |
2.25 x 144 = |
|
Remainder: |
(1 x 12) + 5 = |
(2 x 144) + 25 = |
Matrix Comparison of Sample Calculations
|
|
18 single units with Cut Entry Quantity set at DOZEN |
324 single units with Cut Entry Quantity set at GROSS |
|
Decimal: |
18 / 12 = 1.5 |
324 / 144 =2.25 |
|
Remainder: |
18 / 12 = 1.5; (1
whole unit) |
324 / 144 =2.25;
(2 whole units) |
Default Quantity
Each time you define a new Lot, Bundle-Track will suggest a default number of units in a Bundle. Set that default number here.
Bundle Ticket tab
These settings affect the way information is presented on Bundle Tickets.
Units
The Units dropdown lets you specify the “Per” Unit that will be used when printing quantities on Bundle Tickets.
Order In Section
This option lets you determine how your Tickets will be ordered on the Bundle Ticket Traveler: