About Bundle-Track
Home Solutions Products About Us About Us

 

  Bundle-Track Main Menu
 
  What's New
 
  Solutions
 
  For the Factory
 
  Reports
  Integration
  Requirements
  Support
 
   

Bundle-Track Typical Usage

To help you understand how Bundle-Track may fit into your world, here's a description of typical usage.

Cutting, before Assembly

  1. Someone orders a production run.
     
  2. Within Bundle-Track, a user creates a new Lot record, specifying the Product to be made
    • Here, if necessary, the user can set Lot-specific overrides to the Product's normal Routing steps or rates.
       
  3. Cutters prepare the cutting table for the next cutting session.
     
  4. Within Bundle-Track, a user creates a new Cut record from the Lot record, specifying the size and color of each of the bundles that will be produced in the Cut.

     
  5. Within Bundle-Track, a user prints the Bundle-Tickets.
    • Each bundle gets its own Ticket Sheet with a bar-coded of ticket for each assembly operation.
       
  6. The Cutter attaches Ticket Sheets to bundles and sends the bundles to the assembly floor.
     
  7. If a bundle's Ticket Sheet is lost or damaged, the Cutter reprints the sheet.

Assembly, daily

  • If there's a Time Clock system, Employees clock in at the beginning and end of the work day. Otherwise, they log this information on their time sheets.
     
  • Each time an employee completes an assembly task on a bundle, the employee detaches the corresponding ticket from the bundle's Ticket Sheet and attaches it to a time sheet.
     
  • If there's a Time Clock system, managers edit punches as needed to indicate transfers, interruptions, and other significant circumstance exceptions. Otherwise, the employees log this information on their time sheets for manual entry by office staff.
     
  • If managers need to track a step-specific production problem to its source, they use Bundle-Track's Bundle Adjustments tool to look up the corresponding ticket. The scan detail indicates who performed the step and on what date.
     
  • If managers determine that the production standard value for a given production step needs to be changed, they enter that change into Bundle-Track and update the rate for all related tickets, scanned or not.
     

Payroll, end of the day

  1. Managers collect ticket-laden time sheets from the employees and deliver them to the Payroll office.
     
  2. If the Bundle-Track system includes a Custom Time Clock Data interface, the Bundle-Track user initiates an import of the day's time clock data to automatically update Work Event records for all employees.
     
  3. A Bundle-Track user opens the Events window.
     
  4. For each employee ...
     
    • The user directs the Events window to the Employee's list of Work Events for the day.
       
    • (If there is no Custom Time Clock Data interface in place to automate the task, the user logs any necessary adjustments to the Hours and Pay Conditions in the employee's default list of Work Events for the day.)
       
    • With a handheld barcode scanner (no typos!), the user scans each bar-coded ticket from the employee's time sheet into the appropriate Work Event, entering Ticket Splits as necessary.
       
    • The user enters any adjustments to earnings or total pay.
       
  5. Bundle-Track automatically calculates Costs & Performance Ratings, increments experience hours counts for Training Curves, and calculates gross pay.
     
  6. The user previews or prints reports for validation, distribution, or archiving.

Payroll, end of the pay period - within Bundle-Track

  1. The user exports gross pay data to a file for delivery to a net payroll system (using either the built-in ADP pay export feature or a Custom Pay Export interface).
     
  2. After pay is transmitted, the user closes the pay period. Bundle-Track automatically archives activity data, updates rolling historic averages, and increments the pay period number.
 

top