MaintScape Documentation

MaintScape Documentation - Bar Code Process
GrandRavine Software
MaintScape Documentation - Bar Code Process
Table of Contents
Table of Contents............................................................................................................................. 1
Introduction...................................................................................................................................... 2
Starting the MaintScape PDT Program ........................................................................................... 2
Stopping the MaintScape PDT Program.......................................................................................... 3
Using the MaintScape PDT Program............................................................................................... 3
Main Menu ................................................................................................................................... 3
Part to Work Order....................................................................................................................... 4
Inventory Menu ............................................................................................................................ 6
Inventory Count ........................................................................................................................ 6
Receipt ...................................................................................................................................... 7
Direct Issue ............................................................................................................................... 7
Part Location ................................................................................................................................ 8
Transaction-Specific Part Location .......................................................................................... 8
Default Parent Part Location .................................................................................................... 9
Erase Last Record ........................................................................................................................ 9
Utility ......................................................................................................................................... 10
Unitech PDT Data File Edit Program..................................................................................... 10
Uploading the Transaction Data File to a PC ................................................................................ 11
Processing the Transaction Data File within MaintScape ............................................................. 13
Installing the MaintScape PDT Program ....................................................................................... 15
Warm-Starting and Cold-Starting the Unitech PDT...................................................................... 16
January 22, 2009
www.maintscape.com
Page 1 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
Introduction
MaintScape uses Unitech Portable Data Collection Terminals (PDT) as its bar code device.
Uni
t
e
c
h’
swe
bs
i
t
ei
s
:www.ute.com .
This document covers the PT600, PT630 and HT630 devices. The PT600 and PT630 units are
both discontinued. The HT630 is their successor.
Documentation herein that applies to all devices r
e
f
e
r
st
ot
hede
v
i
c
ea
s“
Unitech PDT”
,
whi
l
e
documentation applying to one of the devices refers to the specific device name (i.e. PT600,
PT630, or HT630).
The MaintScape program for the Unitech PDT supports the following transactions:
1. Issue Parts to Work Orders
2. Part Inventory Counts
3. Receiving Parts
4. Direct Issuing Parts from Inventory
The Unitech PDT builds a transaction file of commands which is then uploaded onto a PC
running MaintScape. The transaction file is then processed within MaintScape, implementing
the transactions.
MaintScape PDT transactions can be performed in any sequence and intermingled with eachother. For example, you can perform a set of Part to Work Order assignments, then perform
some Inventory Counts, then continue with more Part to Work Order assignments, etc.
Starting the MaintScape PDT Program
Please consult your Unitech Us
e
r
’
sGui
def
orba
s
i
ci
ns
t
r
uc
t
i
ons. The PT630 and HT630 ships
with the User Guide on CD-ROM only.
Your Unitech PDT will come pre-loaded with the MaintScape PDT program if you acquired the
device from GrandRavine Software. If this is not the case, or you wish to re-load the MaintScape
PDT program, please consult documentation section Installing the MaintScape PDT Program
(page 15).
To run the MaintScape PDT program, first power on the Unitech PDT by holding the inset power
key for approximately 2 seconds.
If the Unitech PDT powers on with a display similar to:
PT630 BIOS V1.94
MEM 512 KB
>
… Then hold down the [CMD] key for approximately 2 seconds.
January 22, 2009
www.maintscape.com
Page 2 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
You should now be at the Unitech PDT main user menu, which looks like:
1.
3.
5.
7.
RUN
COM
ERA
CPY
2.
4.
6.
8.
TER
DIR
TYP
SET
Pr
e
s
s‘
1’ont
hen
ume
r
i
ck
e
y
pa
d.Yourdi
s
pl
a
ys
houl
dl
ookl
i
k
e
:
< RUN PROGRAM >
MAINTSCP.EXE
I
fapr
og
r
a
mf
i
l
eot
he
rt
ha
n‘
ma
i
nt
s
c
p.
e
xe
’i
sd
i
s
pl
a
y
e
d,pr
e
s
st
he key until MAINTSCP.EXE
is displayed. Press the [ENT] key to run the MaintScape PDT program.
Please bear in mind the following important key sequence:
 Whe
npr
ompt
e
df
oraYe
s
/
Nor
e
s
p
ons
e
,‘
1’i
sYESa
nd‘
2’i
sNO.
Stopping the MaintScape PDT Program
The only way to exi
tt
heMa
i
nt
Sc
a
p
ePDTPr
og
r
a
mi
st
o“
wa
r
ms
t
a
r
t
”or“
c
ol
ds
t
a
r
t
”the Unitech
PDT. Please see documentation section Warm-Starting and Cold-Starting the Unitech PDT
(page 16) for instructions.
Using the MaintScape PDT Program
Main Menu
The Main Menu of the MaintScape PDT Program looks like:
1.
2.
3.
4.
5.
F2
Part to WO
Inventory
Part Loc
Erase Last
Utility
Upload
?
The main menu functions are summarized below, and then described in detail further below:
Part to WO
Start the module for issuing Parts to Work Orders.
Inventory
Access the Inventory menu for performing Part Inventory transactions,
including: inventory count, receiving parts, direct issuing parts.
January 22, 2009
www.maintscape.com
Page 3 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
Part Loc
Display the parent Part Location currently in effect, and allows you to clear the
value.
Erase last
Erase the last transaction.
Utility
Access the Utility menu of less often used utility functions.
See documentation section Uploading the Transaction Data File to a PC (page 11) for more
i
nf
or
ma
t
i
onont
he“
F2Upl
oa
d”f
unc
t
i
on.
Part to Work Order
The first screen of the Part to Work Order function looks like:
Part to WO
Scan Work Order
________________
F2 Upload
F4 Menu
At this point, you may now scan the bar code on a printed MaintScape Work Order.
The bar code text contains the same information as coded into the bar code - for example,
‘
40-123-1’
.‘
40’i
ndi
c
a
t
e
s‘
Wor
kOr
de
r
’
,‘
123’i
st
hei
nt
e
r
na
lMa
i
nt
Sc
a
pei
de
nt
i
f
i
e
rf
ort
he
Work Order, which is also the work or
de
rnumb
e
r
,a
nd‘
1’i
st
hei
nt
e
r
na
lMa
i
nt
Sc
a
pei
de
nt
i
f
i
e
r
for the work order task. Work Orders may have multiple tasks, and parts are issued to a
particular task. Therefore, if your work order is multi-task, ensure you are scanning the bar code
associated with the correct task.
January 22, 2009
www.maintscape.com
Page 4 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
If you successfully scanned a Work Order, your PDT screen will look similar to:
Part to WO
WO: 123-1
Scan Part or WO
________________
F3 Back F4 Menu
As indicated, you may now scan either a Part bar code label or another Work Order bar code. If
you successfully scan a Part bar code, your PDT screen will look similar to:
Part to WO
WO: 123-1
Part: 248
Enter Quantity
____________
F3 Back F4 Menu
ThePa
r
ti
de
nt
i
f
i
e
r‘
248
’a
bov
ei
sa
ni
nt
e
r
na
lMa
i
nt
Sc
a
pei
de
nt
i
f
i
e
rf
ort
hepa
r
t
,nott
hePa
r
t
Code. The Part Code is usually too large to be bar coded. The MaintScape bar code label for the
a
bov
ePa
r
twoul
dha
v
es
ubt
e
xt‘
24-284’whi
c
h,a
swa
st
he case with the Work Order bar code, is
t
hes
a
mei
nf
o
r
ma
t
i
ona
sc
ode
di
nt
ot
heba
rc
ode
.I
nt
hi
se
xa
mpl
e
,‘
24’i
n
di
c
a
t
e
s‘
Pa
r
t
’
,a
nd‘
248’
is the internal Part identifier.
You may now key a quantity into the PDT and press the [ENT] key to accept. The quantity
s
houl
dbei
nt
h
epa
r
t
’
suni
tofme
a
s
ur
e
.The PDT screen will then prompt for another Part to
issue to the Work Order - e.g. look similar to:
Part to WO
WO: 123-1
Scan Part or WO
________________
F3 Back F4 Menu
This is the same display presented when adding the first Part to Work Order 123, task 1. You
may now either scan another Part to issue to Work Order 123, task 1, or you may scan another
Work Order bar code. Scanning another Work Order bar code is a convenient shortcut for
e
xi
t
i
ng‘
a
ddpa
r
tt
oWO12
3’ba
c
kt
ot
heSc
a
nWor
kOr
de
rpr
ompt(
F3)
,t
he
ns
c
a
nni
ngt
hene
xt
Work Order.
January 22, 2009
www.maintscape.com
Page 5 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
Inventory Menu
The Inventory Menu of the MaintScape PDT Program looks like:
Tran Types:
1. Inv Count
2. Receipt
3. Direct Issue
F4 Menu
?
The inventory menu functions are summarized below, and then described in detail further below:
Count
Start the module for performing inventory counts.
Receipt
Start the module for receiving parts into inventory.
Direct Issue
Start the module for direct-issuing parts from inventory.
Inventory Count
An Inventory Count transaction record wi
l
lbe
c
omea
ni
nv
e
nt
or
yt
r
a
ns
a
c
t
i
onoft
y
pe“
Count
”
when processed into MaintScape.
The first screen of the PDT Inventory Count function looks like the following:
Inv Count
Scan Part
________________
F2 Upload
F3 Inv Menu
F4 Menu
At this point, you may now scan a Part bar code label. If successful, your PDT screen will look
similar to:
Inv Count
Part: 248
Enter Quantity
____________
F3 Back F4 Menu
ThePa
r
ti
de
nt
i
f
i
e
r‘
248
’a
bov
ei
sa
ni
nt
e
r
na
lMa
i
nt
Sc
a
pei
de
nt
i
f
i
e
rf
ort
hepa
r
t
,nott
hePa
r
t
Code. The Part Code is usually too large to be bar coded. The MaintScape bar code label for the
January 22, 2009
www.maintscape.com
Page 6 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
a
bov
ePa
r
twoul
dha
v
es
ubt
e
xt‘
24-284’whi
c
hi
st
hes
a
mei
nf
or
ma
t
i
ona
sc
ode
di
nt
ot
he bar
c
ode
.I
nt
hi
se
xa
mpl
e
,‘
24’i
ndi
c
a
t
e
s‘
Pa
r
t
’
,a
nd‘
248’i
st
hei
nt
e
r
na
lPa
r
ti
de
nt
i
f
i
e
r
.
You may now key a quantity into the PDT and press the [ENT] key to accept. The quantity
s
houl
dbei
nt
h
epa
r
t
’
suni
tofme
a
s
ur
e
.The PDT screen will then prompt for another Part for
which to enter an inventory count.
Receipt
A Receipt transaction record wi
l
lbe
c
omea
ni
nv
e
n
t
or
yt
r
a
ns
a
c
t
i
onoft
y
pe“
Re
c
e
i
pt
”whe
n
processed into MaintScape.
The first screen of the PDT Receipt function looks like the following:
Inv Receipt
Scan Part
________________
F2 Upload
F3 Inv Menu
F4 Menu
At this point, you may now scan a Part bar code label. If successful, your PDT screen will look
similar to:
Inv Receipt
Part: 248
Enter Quantity
* Unt of Meas *
____________
F3 Back F4 Menu
Fora
ne
xpl
a
na
t
i
o
noft
hei
de
nt
i
f
i
e
r‘
248’
,pl
e
a
s
econsult documentation section Inventory Count,
above.
You may now key a quantity into the PDT and press the [ENT] key to accept. The quantity
s
houl
dbei
nt
h
epa
r
t
’
suni
tofme
a
s
ur
e
.The PDT screen will then prompt for another Part to
receive.
Important: Youmus
te
nt
e
rt
her
e
c
e
i
v
e
dq
ua
nt
i
t
yi
nt
hepa
r
t
’
suni
tofme
a
s
ur
e
,nott
heuni
tof
order for the receipt. For example
,i
ft
hepa
r
t
’
suni
tofme
a
s
ur
ei
nMa
i
nt
Sc
a
pei
s“
e
a
c
h”
,a
ndy
ou
r
e
c
e
i
v
e2box
e
sof10uni
t
s
,y
oumus
te
nt
e
rqua
nt
i
t
y“
20”
.
Direct Issue
A Receipt transaction record wi
l
lbe
c
omea
ni
nv
e
n
t
or
yt
r
a
ns
a
c
t
i
onoft
y
pe“
Di
r
e
c
tI
s
s
ue
”whe
n
processed into MaintScape.
January 22, 2009
www.maintscape.com
Page 7 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
You create a Direct Issue inventory transaction when you want to remove parts from inventory
without assigning the part to a work order. Note that when a work order with an inventorycontrolled part is closed, MaintScape creates an inventory transac
t
i
o
noft
y
pe“
I
s
s
uet
oWor
k
Or
de
r
”
.
The first screen of the PDT Direct Issue function looks like the following:
Direct Issue
Scan Part
________________
F2 Upload
F3 Inv Menu
F4 Main Menu
At this point, you may now scan a Part bar code label. If successful, your PDT screen will look
similar to:
Direct Issue
Part: 248
Enter Quantity
____________
F3 Back F4 Menu
Fora
ne
xpl
a
na
t
i
o
noft
hei
de
nt
i
f
i
e
r‘
248’
,pl
e
a
s
econsult documentation Inventory Count, above.
You may now key a quantity into the PDT and press the [ENT] key to accept. The quantity
s
houl
dbei
nt
h
epa
r
t
’
suni
tofme
a
s
ur
e
.ThePDTs
c
r
e
e
nwi
l
lt
he
npr
omptf
ora
not
he
rPa
r
tt
o
direct-issue.
Part Location
MaintScape Part Inventory Transactions always occur at a Part Location. When a Part is
recorded in MaintScape as stored at more than one Part Location, it may not be clear which Part
Location applies to a particular transaction recorded by the PDT program.
Transaction-Specific Part Location
Part bar codes may optionally include Part Location information. You can determine this by
inspecting the bar code label subtext. For example:
24-27
Thi
sba
rc
oder
e
pr
e
s
e
nt
st
hePa
r
twi
t
hi
nt
e
r
na
li
de
nt
i
f
i
e
r“
27”
.Thepr
e
f
i
x“
24”
identifies the following token as a Part.
24-10-29-31
Thi
sba
rc
oder
e
pr
e
s
e
nt
st
hePa
r
twi
t
hi
nt
e
r
na
li
de
nt
i
f
i
e
r“
10”a
tt
hePa
r
t
Loc
a
t
i
onwi
t
hi
nt
e
r
na
li
de
nt
i
f
i
e
r“
31”
.Thepr
e
f
i
xe
s“
24”a
nd“
29”i
de
nt
i
f
yt
he
following tokens as a Part and Part Location respectively.
January 22, 2009
www.maintscape.com
Page 8 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
The Part Location specified for a Part applies to the current transaction only. If none is
specified, the Default Parent Part Location will apply if one is set (see below).
Default Parent Part Location
A Part Location bar code label may be scanned any time the bar code Scanner is active when
running the MaintScape PDT program. For example, whenever prompted to scan a Part or Work
Order. When a Part Location is successfully scanned, the PDT will issue a distinctive halfsecond beep, then prompts again for the object originally prompted for. The Part Location
s
c
a
nne
di
s‘
r
e
me
mbe
r
e
d’a
st
he‘
de
f
a
ul
tpa
r
e
nt
’f
ors
ubs
e
que
ntt
r
a
ns
a
c
t
i
onsunt
i
lt
hev
a
l
u
ei
s
cleared or replaced by scanning another Part Location.
How this works is best illustrated by Example. Say you enter a part warehouse assigned Part
Location \Building_1\warehouse_1 in MaintScape, and then you scan a label for the Part
Location at the warehouse door. Then all subsequent Inventory Transactions for Parts are
a
s
s
ume
dt
obea
tt
hePa
r
t
’
sPa
r
tLoc
a
t
i
onwi
t
h
i
nt
ha
twa
r
e
hous
e
.I
not
he
rwor
ds
,a
tt
hePa
r
t
’
s
Part Location below the warehouse in the MaintScape Explorer tree. This clears up the
uncertainty of which Part Location to use if a Part is recorded in MaintScape as stored in
multiple warehouses.
Note: There is no need to scan Part Locations unless Parts scanned are recorded in MaintScape
as stored in multiple Part Locations. Even if Parts scanned are stored in multiple Part Locations,
you can also specify the default Parent Part Location when processing the PDT transaction file.
You will want to scan Part Locations, however, if Parts are stored in multiple Part Locations, and
you are moving between warehouses for those Part Locations.
There is also no need to scan Part Locations if the Part labels you scan contain a Part Location
component (see Transaction-Specific Part Location, above).
If you are running MaintScape multi-site functionality, the only part locations that will be
considered are those within the active site in effect when processing the transaction file created
by the MaintScape PDT program. Therefore there may be multiple part locations for the part at
the various sites, however if there is only one part location at your active site, you do not have to
worry about scanning part locations.
The‘
Pa
r
tLoc
a
t
i
on’Ma
i
nMe
nuf
unc
t
i
onpr
e
s
e
nt
sas
c
r
e
e
nwhi
c
ht
e
l
l
sy
out
h
ei
nt
e
r
na
l
MaintScape identifier for the parent Part Location currently in effect, and gives you the option to
clear its value. Remember - to change the parent Part Location, scan a Part Location bar code
label any time prompted by the MaintScape PDT program to scan a bar code label.
Erase Last Record
For all the MaintScape PDT program transactions described above, a transaction file record is
created after entering a Part Quantity, and pressing the [ENT] key. The Erase Last Record
function lets you erase that last record.
Use the MaintScape transaction file processing window on an uploaded transaction file to erase
records other than the last record.
Whe
ne
r
a
s
i
ngt
hel
a
s
tr
e
c
or
d,y
ouwi
l
lbepr
ompt
e
d“
Er
a
s
eLa
s
t
?
”
.‘
1’i
n
di
c
a
t
e
sYe
s
,‘
2’
indicates No.
January 22, 2009
www.maintscape.com
Page 9 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
Utility
The Utility Menu provides the following functions:
Edit
Invokes the Unitech PDT data file edit program. This program lets you edit the
transaction file created using the MaintScape PDT program. Be very careful your modifications could make the data unusable. Please consult
documentation section Unitech PDT Data File Edit Program, below, for more
details.
Erase All
This function will completely erase the transaction file. This should be done
after it has been successfully uploaded to a PC for processing. Otherwise,
further transactions will simply be tacked onto the end of the existing file, and
you may end up performing the same actions more than once.
You typically erase the data file within the Communication Manager program
that you use to upload the data file to a MaintScape computer. This is
described in documentation section Uploading the Transaction Data File to a
PC (page 11).
Unitech PDT Data File Edit Program
The Unitech PDT data file edit program can be used to modify the data file created by normal
operation of the MaintScape PDT program. Be very careful - your modifications could make the
data unusable.
The Unitech PDT data file edit program operates in one of 3 different modes: Edit, Browse and
Search.
The program starts in browse mode. I
ni
t
i
a
l
l
yi
tdi
s
pl
a
y
s“
Br
ows
eR1,
F1”i
ndi
c
a
t
i
ngbr
ows
e
mode displaying row 1 and field 1. Following this is displayed the data in the row and field.
Press the  or  arrow keys to navigate through the fields in a row, and the  or  arrow keys
to navigate through the rows.
Press the [F3] key to enter row and field coordinates to jump to directly. When prompted to
enter a row number, the number in parentheses after “
R”indicates the total number of records in
the file.
There is a problem with the Edit program in that you cannot use the  arrow key to scroll past
an empty field to a non-empty field. If necessary, you can browse the non-empty field by using
t
he[
F3]“
j
ump”f
unc
t
i
onde
s
c
r
i
be
da
bov
e
.
Enter edit mode from browse mode by pressing [ENT] when browsing a particular row and field.
Not
et
ha
tt
het
opwor
d“
Br
ows
e
”c
ha
ng
e
st
o“
Ed
i
t
”
.Thec
oor
di
na
t
e
sa
ndda
t
aa
r
edisplayed as
before. The  key acts as a backspace in edit mode and the  key recovers backspace-deleted
characters. Press [ENT] to accept changes and return to browse mode.
Press the [F4] key to enter into search mode. Search mode defaults the search value to the value
in the current row and field. You can erase or modify this value using the  key as a backspace.
Press [ENT] after entering a search value to search for data values starting with the search value
in the current column in rows after the current row.
January 22, 2009
www.maintscape.com
Page 10 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
The [Exit] action will cancel from edit or search mode to browse mode, and exit from the data
file edit program when in browse mode. The [Exit] action is performed by pressing the [CMD]
key followed by the [ESC] key.
You need to understand the structure of the data file in order to edit it. The first row is a
“
ma
r
k
e
r
”t
ha
ti
de
nt
i
f
i
e
st
hef
i
l
ea
sc
omi
ngf
r
omt
heMa
i
nt
Sc
a
pePDTpr
og
r
a
m.I
ts
houl
dnotbe
modified. Subsequent rows represent MaintScape PDT program actions –i
.
e
.“
Pa
r
tt
oWork
Or
de
r
”orI
nv
e
nt
or
yt
r
a
ns
a
c
t
i
ons
. The fields are defined as follows:
Field
Description
1) wk_ord_id
Da
t
a
ba
s
eI
Dofwor
kor
de
rwhe
nt
her
owr
e
pr
e
s
e
nt
sa“
pa
r
tt
owor
k
or
de
r
”f
unc
t
i
on.Cur
r
e
nt
l
yt
hi
sv
a
l
uei
st
hes
a
mea
st
hewor
kor
de
r
number.
2) wk_ord_prt_key_no
Database identifier of the work order task. This value is only
specified when a value is specified for wk_ord_id. Work orders are
us
ua
l
l
ys
i
ng
l
et
a
s
k
,a
ndt
hi
sv
a
l
uei
sus
ua
l
l
y“
1”
.
3) prt_id
Database ID of part involved in the current action. This value is
always specified.
4) quantity
Quantity of part for the current action. This value is always
specified.
5) prt_loc_id_rltve
Database ID of Part Location bar code scanned as described in
documentation section Part Location (page 8). A scanned part
location appears in the current transaction record, and all subsequent
transaction records until a new part location is scanned or the ineffect part location value is cleared.
6) Action Type
Each row in the data file represents a MaintScape PDT program
action type. This column identifies the type, and the valid values
are:
1.
2.
3.
4.
Part to Work Order
Inventory Count
Receipt
Direct Issue
Uploading the Transaction Data File to a PC
Your transaction data file is uploaded from the Unitech PDT to a PC using the Unitech PTComm
Manager program. If not provided by GrandRavine Software, you may download this program
from the Unitech web site. Presently this program may be downloaded from the following web
s
i
t
e(
l
ookf
o
r“
PTCommMa
na
g
e
r–32bi
t
”a
tt
hebot
t
omoft
h
edownl
oa
dsl
i
s
t
)
:
http://www.ute.com/downloads.php?product_id=29
If the above link does not work, navigate to the product web site for the HT630 at
http://www.ute.com a
n
dl
ookf
ora“
Downl
oa
ds
”l
i
nk
.
January 22, 2009
www.maintscape.com
Page 11 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
IMPORTANT: You must pr
e
s
s“F2Upl
oad”f
r
om aMaintScape PDT program screen that
displays this option prior to uploading data. Your MaintScape PDT program screen will then
look like the following:
Upload
Maintscp.txt
using PTComm
Manager then
delete
using same.
F1 Done F4 Canc
In order to communicate from your PC to the Unitech PDT, you must do the following:
 Connect the cable supplied with your Unitech PDT to a serial port on your PC and to the
Unitech PDT. A serial adapter to USB adapter can be used if your computer does not have a
serial port.
 Within the PTCommMa
na
g
e
rpr
og
r
a
m,u
s
eme
nui
t
e
m‘
Transfers/Connect Portable…’t
o
establish a connection. Adj
us
t“
ComPor
t
”a
nds
e
t
t
i
n
g
sv
a
l
ue
si
fne
c
e
s
s
a
r
y
.
If connection is successful, you will see a screen similar to:
The left panel shows files on your PC and the top-right panel shows files on the Unitech PDT.
The file MAINTSCP.TXT in the top-right panel is the transaction file created by the MaintScape
PDT program. Simply drag it from the top-right panel and drop it on a directory (folder) in the
left panel.
You will be prompted with a confirmation window when dropping the file. At this time you may
rename the copied file if you choose –e
.
g
.modi
f
y“
To:
”de
s
t
i
na
t
i
onf
r
o
m“
c
:
\my di
r
e
c
t
or
y
”t
o
January 22, 2009
www.maintscape.com
Page 12 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
“
c
:
\my directory\PT 2007-08-13 –j
b.
t
x
t
”
.We suggest you adopt a directory and/or naming
convention which reminds you who created the file and when.
IMPORTANT: You should erase the transaction file on the Unitech PDT after it has been
uploaded. Otherwise, further transactions will simply be tacked onto the end of the existing file,
and you may end up performing the same actions more than once. Erase the transaction file
within PTComm Manager byhi
l
i
g
ht
i
ng“
ma
i
nt
s
c
p.
t
xt
”in the top-right panel and clicking menu
b
a
ra
c
t
i
o
n“
Fi
l
e
”
/
”
De
l
e
t
ePor
t
a
bl
eFi
l
e
…”
.
Your MaintScape PDT program screen should now look like the following:
MAINTSCP.TXT
UPLOADING
..
OK !
Press any key..
Press any key on the Unitech PDT device (e.g. [ENT] key). Your MaintScape PDT program
s
c
r
e
e
ns
houl
dnowr
e
v
e
r
tba
c
kt
odi
s
pl
a
y
i
ng
,“
Upload Maintscp.txt using PTComm Manager then
delete using same.”
.Pr
e
ss the [F1] key to indicate the upload is done. The MaintScape PDT
Program will then create a new transaction file (you deleted the prior one), and you will be able
to continue creating transactions.
Processing the Transaction Data File within MaintScape
The uploaded transaction data file is processed using the Transaction Batch window accessed by
c
l
i
c
k
i
ngma
i
nme
nui
c
on‘
Ut
i
l
i
t
i
e
s
’
,t
he
ns
e
l
e
c
t
i
ngopt
i
on‘
Tr
a
ns
a
c
t
i
onBa
t
c
h(
ba
rc
ode
)
’
.An
example of this window is as follows:
January 22, 2009
www.maintscape.com
Page 13 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
The Transaction Batch window lets you:
 Browse the pending transactions and scan for errors.
 Apply all or part of the batch transactions.
 Delete batch transactions.
To use this window, enter parameter values in the top part of the window and then click the
(search) button. Parameter fields are as follows:
Import File
This field is mandatory. It identifies the file uploaded from the Unitech PDT
that you wish to process into MaintScape.
Part Location
This field is useful if parts referred to in the batch transactions are stored at
more than one part location. If so, MaintScape will only consider those part
locations in the subtree below the part location specified here. See
documentation section Part Location (page 8) for more details on the issue
of multiple candidate part locations and for another possible solution.
Site
This field is only applicable when you are running the MaintScape multi-site
module and when multi-site functionality is enabled. It indicates the site
that the batch transactions were recorded at. This helps MaintScape
compute a part location for a part referenced in a transaction, as MaintScape
will only consider part locations at the identified site(s).
Default Tran
Sts
This field is an important consideration if you are processing Part
Receipt transaction records.
The Default Part Inventory Transaction Status value is only meaningful
when processing transaction records for part inventory transactions that can
be created into more than one status - typically 'Receipts'.
January 22, 2009
www.maintscape.com
Page 14 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
MaintScape can only assign a price to a processed receipt if it can match the
received part to a single Purchase Order or Purchase Requisition. Otherwise
the receipt will be created with a price of zero.
If you specify default status 'planned', you can later edit the generated
inventory receipt transaction to specify a receipt price in cases where
MaintScape could not calculate it. You should then finalize the transaction
by saving it as status 'issued'. This is more work, however it ensures that
MaintScape maintains an accurate average price for the part. MaintScape
Today's Status functionality can easily help you identify receipt transactions
that are status 'planned' and waiting accurate price data.
Important: Each batch transaction type must be processed separately. Select each transaction
type in the “
t
y
pe
”drop-down list box, review the transactions pending if necessary, and then
initiate processing by clicking the
(generate) button. The generate button works on the
records that are selected, or all records if none are selected.
The batch transaction process is designed to prevent the same transaction from being applied
more than once. You may wish to keep old transaction files for audit purposes: they contain
audit data which can be viewed within the same MaintScape window. You can re-display
processed transaction files in this window to view the processing results, and when doing so, you
can also print the old results.
Installing the MaintScape PDT Program
Refer to the documentation section Uploading the Transaction Data File to a PC (page 11) to
perform the following steps:
1. Install the Unitech PTComm Manager program on a PC.
2. Run Unitech PTComm Manager and connect it to your Unitech PDT.
If the top-right panel of PTComm Ma
na
g
e
rl
i
s
t
spr
og
r
a
ms‘
ma
i
nt
s
c
p.
e
xe
’a
nd‘
j
e
ng
.
e
xe
’
,t
he
nt
he
MaintScape PDT program is already loaded. You may delete these files from your Unitech PDT
by highlighting them in the top-right panel of PTComm Manager and clicking menu bar action
“
Fi
l
e
”
/
”
De
l
e
t
ePor
t
a
bl
eFi
l
e
…”
.
TheMa
i
nt
Sc
a
pePDTpr
og
r
a
ms‘
ma
i
nt
s
c
p.
e
xe
’a
nd‘
j
e
ng
.
e
x
e
’a
r
ef
oun
di
nt
hePT60
0, PT630 or
HT630 directory of your MaintScape CD-ROM. Navigate to these files in the left panel of
PTComm Manager, then drag and drop them one-at-a-time onto the PDT name in the top-right
panel of PTComm Manager (i.e. onto the top item of the name tree). Important: Drag-and-drop
‘
ma
i
nt
s
c
p.
e
xe
’be
f
or
e‘
j
e
ng
.
e
xe
’
.
If you want to install the MaintScape PDT program on a fully reset Unitech PDT, perform a
“
c
ol
d-s
t
a
r
t
”a
sde
s
c
r
i
be
di
nd
oc
ume
nt
a
t
i
ons
e
c
t
i
onWarm-Starting and Cold-Starting the Unitech
PDT, below.
January 22, 2009
www.maintscape.com
Page 15 of 16
MaintScape Documentation - Bar Code Process
GrandRavine Software
Warm-Starting and Cold-Starting the Unitech PDT
The difference between warm-starting and cold-starting is as follows:
 Warm-starting restarts the Unitech PDT returning you to the main user menu without
erasing any data (programs or data files). This is the only way to non-destructively exit
the MaintScape PDT program.
 Cold-starting erases all non-system files from the Unitech PDT (programs and data), and
ensures you start from a clean state. You may wish to cold-start your Unitech PDT prior
to loading the MaintScape PDT Program.
Both warm-start and cold-start are initiated from the same screen First, ensure the Unitech PDT
is turned off. If it is on, hold the inset power-on key until the unit turns off. When the Unitech
PDT is turned off, hold down the [CMD] and  keys, and then press the power-on key. The
Unitech PDT display will then show:
<START MENU>
1.SUPERVISOR
2.WARM START
3.COLD START
A warm-start will occur immediately upon pressing key [2]. If you press key [3] to select a coldstart, you will then be asked to press key [1] to confirm all data will be lost.
After the warm or cold start, the Unitech PDT will power on with a display similar to:
PT630 BIOS V1.94
MEM 512 KB
>
Hold down the [CMD] key for approximately 2 seconds to access the Unitech PDT main user
menu.
January 22, 2009
www.maintscape.com
Page 16 of 16