Batch Processing and Tracking

Batch Processing and Tracking................................................................................................................................. 1

Batch Processing – Overview ................................................................................................................................ 2
Batch Processing – Merging Jobs ............................................................................................................................. 3
Batch Processing – Monthly Material Usage Example.............................................................................................. 3
Batch Processing – Multiple Processing ................................................................................................................... 8
Batch Process – Mode ............................................................................................................................................ 10
Batch Process – Requirements ............................................................................................................................... 10
Batch Process – Insulation Scanning and Cutting Example ................................................................................... 10
Batch Processing – Insulation Scanning and Cutting Example -Prerequisites ....................................................... 10
Batch Processing – Insulation Scanning and Cutting Example - Procedure........................................................... 12
TrackIt...................................................................................................................................................................... 13
TrackIt – Insulation Scanning Mode ........................................................................................................................ 13
TrackIt – Status Change Configuration ................................................................................................................... 14
 
Batch Processing and Tracking
Batch Processing – Overview
Batch processing is a feature within PM2000 allowing users to ‘combine’ multiple jobs into one larger jobs,
process multiple jobs at the same time and/or background process requests from our TrackIt module.
Typical uses of the batch processing function could be:
1) Rather than nesting small jobs individually generally results in very poor material utilization, batch
processing can combine all the individual small jobs into one larger job.
2) A ‘month’ end report of materials used across multiple jobs for that month.
3) A summary of all materials used on a particular project to-date.
4) Process (nest, print, etc) multiple jobs in one step rather than opening-processing, opening-processing,
etc jobs one by one
5) Using PM2000 to automatically process items captured by TrackIt, nesting them and printing out
appropriate paperwork. (e.g. scanning barcodes and automatically processing the required liner for
automated liner cutting).

2
 
Batch Processing – Merging Jobs
The two main uses of batch processing in ‘merge’ mode would be to produce monthly material usage reports and
to combine multiple small jobs (e.g. field call in jobs) into one larger, more economical job.
Batch Processing – Monthly Material Usage Example
Batch processing can only be started from the File – New Job menu in PM2000. If you have an existing job open,
close it first. If you are using the Job Browser interface, use the cancel button.
From the File – New Job menu, you will be presented with the Job Wizard.

As we want to process existing jobs (i.e. jobs that have already been input and/or processed by the system), click
on the ‘Existing Jobs’ tab to see the options available for existing jobs.

3
The option we require off this screen is the ‘Batch Process Jobs Together’ (this effectively ‘merges’ all of the jobs
selected).
This will now take you to the job selection screen where you will choose what jobs you wish to combine.

The ‘Look in’ drop down allows you to navigate to your ‘base/root’ project folder and the Large Icons and Details
(at the top right of the dialog box) allow you to view the projects and jobs in different ways.
Tip: Easily selecting the jobs to combine them depends on the folder structure you are using for your
jobs/projects. In the above screen, projects have been organized into folders, each folder containing the takeoffs
for that project. This makes extracting ‘project to-date’ information per project easy but for ‘monthly usage’ type
reports, it means going through all the folders looking the date range you are interested in. The folder structure
you are using doesn’t impact the batch merging but different folder structures can make it easier for the operator
to get to the information quickly and easily. Possible folder structure considerations would be to add ‘month’

4
(Jan/Feb/Mar/etc) sub-folders into each project and during the normal entry of takeoffs the operator would select
the Project and then the month to create the new takeoff. Another option would be to use Month as the top level
of the folder structure and have each project name as a sub-folder. The above folder structure where each project
has its own folder and no sub-folders is probably the most common format used but, re-structuring the folders if
you intend making heavy use of batch merging may be something to consider.
As this example requires date ranges (i.e. we need to know the job date to be able to decide if it should be
included in our ‘batch’) the better view is the ‘details’ (top right icon).

The ‘Details’ view allows us to see the job date information.

Note: The date displayed is the ‘modified’ date (i.e. the last time the job was changed). Certain assumptions need
to be made in deciding what jobs to include in our date range. In this example, the assumption is that all jobs input
are processed and cut essentially on the same day. Obviously this isn’t always the case but, by doing it this way,
it does make the jobs easier to select. The software doesn’t actually ‘know’ when a job has been cut.
We can now select the jobs that we want to include in our ‘batch’ by opening up each job folder.

By default, the jobs aren’t displayed in any particular date order but by clicking on the column header ‘Modified’,
the jobs are displayed in ascending/descending date order (each click will reverse the order).

5
Once sorted, choosing the date range you want to batch is a little easier. You can select the jobs you want either
individually or in multiples by using shift or Ctrl key (standard Windows selection). Once you have select the jobs
from a particular folder, use the ‘+’ button (towards the bottom right of the dialog box) to add them to the list on the
right hand side (the ‘-‘ button allows you to remove them from your selection if needed.

Repeat the above procedure to select jobs from other folders as needed.
We can now select a pre-defined (or actually design a new) process that we want to run on the batch, from the
‘Process’ drop down menu.

6
Any process can be selected but typically, for a monthly summary, reports on material usage, inventory
information, etc would be typical. In the above example, a process has been selected which just prints out a
material usage list (just a regular report and a regular process – choosing a process that printed out labels,
nested sheets, etc would not normally be a good idea – make or a choose a process and select just the reports
that you need).
You can choose ‘None’ for the process in which case one big job is created that contains all the selected jobs.
This job can then be opened and viewed, processed, printed just like any other job. Unless you have a specific
requirement to look at the individual contents of the job, the better way is to create reports and a ‘process’ that
extracts the information you are looking for.
The final step prior to running the merge is to designate a job name.

7
Typically, the name would be relevant to what the batch merge was. In this case, as the merge is for all the jobs in
August, the job has been called August 07. If you intend saving the merged job for future reference (maybe at the
end of the year merge the monthly merges) you may want to create a specific folder (e.g. 2007) in the projects list
to keep the resulting job safe and easily locatable.
When you click the ‘Finish’ button, batch merging goes to work opening and merging all the jobs you have
selected and then applying the process you have selected.

Batch Processing – Multiple Processing

Batch processing, rather than just combining multiple jobs into one big job, can also be used to run the same
process on multiple jobs separately. For example, jobs may have been input during the course of the day and
then you want start printing the labels and paperwork for them at night. The procedure is exactly the same as the
Batch Processing – Merging Jobs example except that you select the ‘Batch Process Jobs Separately’ rather than
the ‘Batch Process Jobs Together’ option from the ‘Existing Jobs’ dialog.

8
9
 
Batch Process – Mode
PM2000 is capable of running in ‘batch’ mode in which it constantly scans for files to process. In batch mode,
PM2000 waits for appropriate files to be created, opens then up and processes them – all without operator
intervention.
There are a number of applications that this can be used for but probably the most popular is for processing
information from a bar-code scanner to cut the required liner parts for an item.
Batch Process – Requirements
Batch mode processing is part of the standard PM2000 but it is only available if the software can locate the
PROCESS folder (and its sub-folders). These folders MUST be located within the MAIN folder. To locate the
MAIN folder, open up the MAP.INI file being used by the PM2000 and locate the MAIN= file path (typically
towards the bottom of the file). Once you have located this folder, you will need to create the following folders
structure if it does not already exist.

Typically, the MAIN= path in the MAP.INI file will be pointing to the PM Shared folder which would mean that you
would create a sub-folder called PROCESS within PM Shared and then COMPLETE, PENDING and WORK
would be sub-folders of PROCESS.
To check that you have the folders in the right place with the right name, start PM2000 and from the File – New
Job menu, see if you have the ‘batch process mode’ icon.

If the icon isn’t there, PM2000 can’t find the PROCESS folder. Check the ‘Batch Process – Requirements’.
Batch Process – Insulation Scanning and Cutting Example
A common use of the ‘batch’ mode feature of PM2000 is to automatically process (nest and print) liner blanks for
the metal panels. The labels (for the metal) can include a barcode (or this information can be manually entered)
which is used to create a ‘batch’ file which is then picked up by ‘batch-mode’ PM2000, nested and printed ready
for the liner table operator to download and cut.
Batch Processing – Insulation Scanning and Cutting Example -
Prerequisites
The PROCESS folder and sub-folders must be in place (see Batch Processing – Requirements).
1) A ‘process’ called INSUL (BIR) must be present – Utilities – Process – Setup. The process would typically
just be nest (for liner table if applicable), write nc (for liner table if applicable) and print (usually a nest
print showing the sheet, size and material, and NC number so the operator can then load and run the
sheet at the liner table).
2) The job and project name needs to be present in the ‘metal’ NC data file. (From File – Setup – Installed
Machines, select your metal cutting table and then ‘Setup’. Under the ‘Remarks’ tab, make sure the

10
 ‘Suppress Remarks’ box is unchecked and the ‘Job File Name’ entry has been moved to the right hand
list.

3) The ‘Part NC/Cut Index Position’ ‘print object’ needs to be part of the metal material label. From File –
Print Layout – Part Labels, make sure ‘Part NC/Cut Index Position’ is on the label template.

In the above example label template, the ‘properties’ of the print object have been set to ‘barcode’ so that a
scanner could be used to read the label. The ‘Barcode’ feature would be required on the PM2000 HASP key to
use this. Without the barcode, the operator would have to hand enter the Part NC/Cut Index Position information
rather than just scanning it. If you do intend to use barcodes you may also want to consider the TrackIt module

11
which has a number of ‘scan & report’, ‘scan & update’ features as well as being able to automate the collection
and processing of the label/liner parts.
Batch Processing – Insulation Scanning and Cutting Example - Procedure
Firstly, PM2000 needs to be started in ‘batch’ mode. This can be done one of two ways.
Method one is to start PM2000 and then from the File – New Job dialog, click on the ‘Batch Process Mode’ icon.
Method two is to modify the shortcut to start PM2000 and add ‘/PROCESS’ at the end of the ‘Target’ line. This is
normally a better solution as to successfully process batches as they are generated, PM2000 needs to be in
batch mode.
Note: Multiple instances of PM2000 can be run on the same computer with only one key. You could have a ‘batch
mode’ PM2000 automatically started (by placing it in Windows Startup folder) whenever the computer is turned on
and ANOTHER startup icon for PM2000 just on the Desktop that would let the input operator enter in jobs, etc
and do what he would normally do on that station.

When PM2000 is running in batch mode, it is normally automatically minimized on the Windows Taskbar but if
you do ‘full screen’ it, you will see an animated ‘Scanning for Tasks’ screen.

In ‘scanning’ mode, PM2000 is just waiting for an appropriate file to dropped into the PROCESS\PENDING folder
at which point it will grab the file (temporarily putting it into the PROCESS\WORK folder) and then, when finished

12
processing, move it to the PROCESS\COMPLETE folder (along with an error file if any problems were
encountered during the process).
In insulation processing mode, the file required is a BIR file. Whenever a file with a BIR extension is found in the
PENDING folder, this triggers PM2000 to open and process it using the INSUL (BIR) process. The format for the
BIR file is as follows:
NC Sheet Number Cut Index (Sheet), Quantity
A typical example could be:

The first line of this file calls for the liner for piece (cut) 1 from sheet 1146. The second line calls for the liner for
piece (cut) 3 of sheet 1146, etc. All the quantities are set to one so it is only going to nest each liner panel once
(potential use of the quantity would be if there were 8 identical end caps – rather than entering 8 lines in the BIR
file showing sheet number, cut number, etc – the entry could just give one sheet and cut number with a quantity of
8).
If this file is now placed in the PENDING folder, you will see it briefly moved to the WORK folder and ultimately
end up in the COMPLETE folder and whatever actions the INSUL (BIR) process called for will be performed.
TrackIt
TrackIt (this is the Unicode version – BarScan is the non-Unicode version) is a module that can provide a simple
and effective interface between user-supplied barcode scanner and the job files created by PM2000 and or CAD.
TrackIt has a ‘software’ lock but can be run in demo mode prior to buying it. It requires access to the database,
reports folder and projects folder (defined within the BARSCAN.INI file) to operate correctly.

TrackIt – Insulation Scanning Mode

One of the most common uses of TrackIt is in combination with the insulation batch processing mode described
above. In this mode, TrackIt reads data from a user-supplied barcode scanner and automatically creates the
batch processing file format as described above. TrackIt is configured to scan the serial port that the scanner is
attached to, reads the scans from the metal part labels and, when the operator presses a designated key on the
scanner, writes out the BIR file into the PENDING folder (which is then processed, the liner parts nested and
typically a ‘nest report’ generated so the liner table operator can then load and cut the liner sheet.

Configuration for this mode of operation is done purely from the ‘Scan Mode’ menu of TrackIt.

From the ‘Options’ menu of ‘Scan Mode’, start with the ‘Serial Mode’ tab. This allows you define (and activate with
the ‘Enable Serial Mode’ check box) the interface with your barcode scanner. The parameters are dependent of
the scanner you are using but the above are typical (baud rate, COM port, etc). Refer to you scanner
documentation for more details.
Moving across to the ‘Insulation Options’ tab, you can set up the next part of the setup.
13
The ‘Mode Trigger’ is the character that designates the end of the scan sequence. The operator will typically scan
multiple metal parts and then when finished, with the above setting, press zero on the scanner keypad and that
tells TrackIt to write out the batch file. The ‘Mode Trigger’ can be anything and if you don’t have a keypad on your
scanner, you can actually use a barcode from something else. (We have an installation that has a gum packet
barcode as the ‘Mode Trigger’ – the operator scans the metal parts and then, when all the required parts are
scanned, they scan the gum wrapper.)
Under the ‘Output Options’, the folder is typically the path the PROCESS\PENDING folder (the location the batch
file needs to written to) and the ‘Filename’ box contains the name of the file to written.
For scanning liner, the ‘General’ and ‘Status Options’ tabs aren’t used.
Once configured, you can put TrackIt into ‘Scan Mode’ – ‘Insulation Requests’. TrackIt now is self-dependent and
can be minimized. It records input from the scanner and then when the ‘Mode Trigger’ is input/scanned, the BIR
file is written to the PENDING folder. TrackIt returns back to recording scans.

TrackIt – Status Change Configuration

In this mode, TrackIt is scanning for completed items (not just the parts that make up an item) which it can report
and/or change the status.
From ‘Scan Mode’ – ‘Options’, the ‘Serial Mode’ tab needs to be configured as above to interface with the
scanner. The ‘Insulation Options’ tab is not used but the ‘Status Options’ and ‘General’ tab are.

14
‘Mode Trigger’ is the character/string you want to use to designate the end of a scanning run. (i.e. flag TrackIt that
you have finished selecting items to be processed). ‘Output Options’ designates the location and name of the file
you want to create that will contain the status updates.
The ‘Item Status Scanning’ allows you to select what status you want to change the scanned items to, the ID of
the user/scanner (you could have multiple scanners – ID 1 may be the scanner at the QC department, ID 2 may
be the scanner at the shipping dock, etc) and ‘Item Identifier’ – this tells the software whether you are scanning
for ‘Item Numbers’ or ‘Item Handle’ – the potential problem with ‘Item Numbers’ is that there could be multiple
copies of the same item in the job (there for TrackIt wouldn’t know which one to update).
‘Printing’ allows you to produce a paper trail if required. ‘Execution Mode’ can be set to ‘None’ (no print out
required), ‘Continuous’ (print a line per scan) or ‘Batch’ (run the selected report when the ‘Mode Trigger’ is
detected). The ‘Use Printout’ designates which report to print when in the various ‘Printing’ modes. These reports
are regular Profile Master reports.
The ‘General’ tab allows you to specify the folders for the database, projects and reports. These would typically
be mapped to the PM Shared folder structure.
To activate the ‘status change’ mode of TrackIt, from the ‘Scan Mode’ menu, select ‘Statuses’. TrackIt is now in
scan mode waiting for items to be scanned and then either reported on and/or generate the status update file
based on which ‘trigger’ is entered.

TrackIt is a very powerful and flexible module. Based on your requirements, you may need more than one license
(e.g. if you want to use the status change option to track an item through various phases of its life (manufactured,
shipped, installed, etc)).

15