Supusa e (Bam)

AUTOMET Revision 1.
0
METALPROGETTI
Perugia, 16/05/2002
Battista Automat Metalprogetti (BAM) is a software procedure produced by the

METALPROGETTI company and it is set up to command and control the garment handling systems
produced by the company under the name of BATTISTA. This procedure has been designed to
enable connection with management softwares for dry-cleaning shops manufactured by third parties
(TP).
The purpose of this document is to furnish a preliminary description of how information is
exchanged between BAM and TP.
This document has been drawn up on the assumption that the reader is already familiar with the
BATTISTA automatic systems in terms of both components and operation.
LOCAL NETWORK
The two personal computers are connected through a local network such as Ethernet. The actual
transmission system and the network protocol are to be established. The exchange of information
between the two systems is designed to operate through the use of files visible on the local network.
COMPUTER ARCHITECTURE
The minimum computer architecture is composed of two personal computers, one at the reception
desk dedicated exclusively to the TP and the other one at the automatic distribution gate dedicated
exclusively to BAM. The screen of the latter computer is used by BAM to give the users the
information needed for proper management of the automatic distribution process.
BAM operates under WINDOWS 9X/NT/W2000/WXP/WVISTA/W7.
The system envisions a shared directory, either located in the BAM computer and called BAMEXC,
or located in the TP computer and in this case it is necessary to share an M disk in which BAM has
full rights (reading, writing, canceling).
All the exchange files will pass by the shared directory.
During the installation BAM creates a file named READY.NET to effectuate a connection test
between the PCs and a subdirectory named BAMCOPY maintaining a copy of its database. These
files cannot and must not be cancelled or modified.
The location and name of this directory can be changed based on specific needs of the TP.
NOTES ON THE OPERATING LOGIC
BAM has a private database through which it performs the various garment handling and
management phases. This database is fed by the TP that, at the time of a new recording, must send
BAM the data on the garments that have been received, using the procedure and format described
below. It is also the TPs responsibility to send BAM any variations made in the status of the
garments after they have been recorded.
1-16
AUTOMET Revision 1.0

METALPROGETTI
During the various handling phases, BAM modifies its own database so that the position of the
garments is always uniquely identified and at the same time, it also transmits the data on new
statuses to the TP. The TP is responsible for updating its own database to reflect each status
variation it receives.
BAM is connected to the automatic handling installation which includes the automatic delivery gate,
the screen for the customers and the magnetic card reader for identifying the customers. Concerning
the screen, the messages to the customers originate in the TP who transmits to BAM the information
content that should be shown to the customer; similarly, concerning the card reader, BAM is in
charge of implementing the management of the device and of the magnetic card, but once the card
has been read the content of the track is transmitted from BAM to TP, who is responsible for
managing this information.
TYPES OF DATA
BAM manages three kinds of data:
1 data concerning the garments and their change of status during the various management
phases, as well as status of the corresponding conveyor slots;
2 data concerning the content of the magnetic cards which the customers uses to retrieve their
garments at the automatic delivery gate;
3 data concerning the messages to appear on the automatic delivery gate screen once the
customer has asked for his garments by inserting his magnetic card.
DATA EXCHANGE ON GARMENT HANDLING
The exchange of data regarding garment handling takes place through an ASCII format file. Each
line/record has a fixed length of 91 characters (data) + 2 (CR+LF) for the end of the line, with a
possible but not necessary end-of-file character after the last record [chr(27)].
FLOW CHART:
Tp create files
AUTOMAT.IN
BAMEXC
BAM CHECKS FILE AND

COMPLETES DB
The TP generates an AUTOMAT.IN file in the format described below. BAM takes it for processing
and upon completion cancels it. The TP must monitor the completed cancellation of the file in order
to generate the next one. The TP must make the AUTOMAT.IN visible to BAM only when all the
writing operations on the file have been completed, in order to avoid taking over incomplete data.
The data that the TP must communicate to BAM is:
- each new garment that is recorded
2-16

METALPROGETTI
garments or order to delete; it is not possible to delete a garment or an order that had a status
variation (status <>R)
garments to be delivered to the customer through the automatic delivery gate or, alternatively, by
means of an unloading arm inside the shop
garments to be delivered manually to the customer, i.e. all items that are not stored on the
conveyor; in this case it is possible to deliver a garment even if its status is other than R.
BAM generates an AUTOMAT.OUT file with the same format as AUTOMAT.IN in which it signals
the TP with the data on all the handling operations performed independently or following requests
received in AUTOMAT.IN.
The TP must rapidly use and cancel this file, because for the entire time that BAM sees the existence
of the file it cannot generate another one and in these conditions, the automatic handling operation is
blocked (the installation is not operative).
BAM transmits AUTOMAT.OUT each time that any handling operation is performed on the
garments. The purpose of this is to allow the TP to record the handling operation in its files.
These are the files from which the TP can retrieve information on the status and position of the
garment on the system if the BAM files need to be reconfigured.
The data that BAM communicates to the TP involve:
- list of all handled garments (change in status)
- list of all slots whose status has changed
The format of each file record is shown below:
Field Name
LOT
Type
Character
NGARM
GARMENT
GARCODE
GARDESC
PERC
Numeric
Numeric
Character
Character
Numeric
HUNG
Character
STATUS
Character
W
Format
20 00000001 Code of the lot order #. Unique number for each
lot. Once the length of the code to use has been

decided, the code has to be aligned on the left and
filled up with spaces on the right
2
Number of garments making up the lot.
2
Garment order number in the lot.
20
Garment code. Unique number for each garment.
30
Garment description.
3
Occupation percentage of the garment/slot.
100 = 1 slot. Depends on garment thickness.
Example: SHIRT
= 30
JACKET = 150
COAT
= 300
1
Indicates whether garment can be hung or not:
"N" = garment not hung
"S" = hung garment
1
Garment status flag
"R" = new record
"A" = to be canceled/canceled
"D" = cancel order
"L" = being handled/ready
"M" = for retrieval/retrieved manually
3-16

METALPROGETTI
"U" = for retrieval/retrieved at automatic

distribution gate
P = To pick the entire order from the 24h pickup
C = you receive the commit on the creation of a
new order
O = Change Order Amount Due
01= distribution conveyor
05= sorting conveyor
Slot number in which the garment is loaded.
Position code for garment ready off conveyor.
Free string indicating the location in which the
garment has been placed ready for retrieval.
The TP is not allowed to use the characters # @ *
because they are used by BAM for the various
automatic sorting phases.
Customer Code, used to load on conveyor as close
as possible the Orders of the same customer
Parameter to define in which sequence BAM
should unload ORDES from Conveyor.
Possible Value:
0 = Optimize by Slot (Normaly used for stores
Orders)
5 = BAM respect the sequence given on the file
MAG
Character
01
SLOT
OUT
Character
Character
5
5
00001
CUSTOMER
Character
20
ORDERTYPE Character
ORDERKEY
ARM
Character
Character
20
3 Blank
Price
CUSTOMER
Name
STORE
Description
Item
Description 2
Delivery
Character
Character
10
50
Not Used
Define the extraction Arm to use to unload the
order:
Blank = BAM decide automatically the ARM to
use
To assingn a specific ARM use 001, 002 ecc.
Price of the item
Customer Name
Characther
20
Store info
Character
20
Additional description for the item
Character
CardNumber
Character
254
CardExp
TotPar
Character
Character
4
10
DropDate
Character
0 = Pickup not allow

1 = Pick up Allow
Credit Card number used for the DROP off.
The number is encripted
Expiration date of the card in the format YYMM
Total amount of the order, alligned on the right.
Example
30.25
(30 dollars and 25 cents)
Drop off date
DDMMYYYY
4-16

METALPROGETTI
DropTime
Character
PromiseDate
Character
PromiseTIme
Character
Drop off time

HHMMSS
Promise Date for pickup
DDMMYYYY
Promise Time for pickup
HHMMSS
To simplify the description, we have defined several key words to show the combination of several
record fields, identifying some of the fundamental garment-management conditions.
STAT
MAG
CAS
OUT
DESCRIPTION
NOT READY just sent from TP to BAM
05
00100
READY hanging on sorting conveyor
#100#
READY unloaded from sorting conveyor on chain
*100*
READY loaded on automatic loading chain
05/01
00123 @100@ READY ordered to be unloaded from conveyors
01
01450
READY hanging on storage conveyor

ABCDE
READY OFF CONVEYOR
1 AUTOMAT.IN
The fields can take on different meanings depending on the context.
1.1
RECORD NEW LOT COMMAND
The file must contain a record for each garment comprising the lot.
FIELD
DESCRIPTION
NOTE
Compulsory
LOT
Lot code
aligned on the left
yes
NGARM
Total number of garments in the lot
yes
GARMENT
Garment order number in the lot
yes
GARCODE
Garment code
GARDESC
Item description
PERC
Percentage occupied by garment/slot XXX
yes
HUNG
Garment hanging or not
S/N
yes
STATUS
New record
yes
MAG
Storage conveyor
Blank
MAGSLOT
Slot
Blank
aligned on the left
5-16
yes

METALPROGETTI
OUT
Position off conveyor
Blank
CUSTOME
R
Customer name or code
Blank
ORDERTYP
E
Blank
ORDERKEY
Blank
ARM
Blank
There is no AUTOMAT.OUT response.

1.2
GARMENT RECORD CANCEL COMMAND
For canceling garments, the file must contain a record for each garment to be canceled. To cancel
the entire lot, one single line is sufficient for all the garments of the same lot.
A garment can be canceled only if STATUS = R. To delete one entire order all the garments
belonging to it must be in the status R.
FIELD
DESCRIPTION
NOTE
Compulsory
LOT
Lot code
aligned on the left yes
NGARM
yes
GARM
yes
GARCODE
Garment code
GARDESC
Item description
PERC
yes
HUNG
S/N
yes
STATUS
New record
A in case
garments
D in case
orders
MAGSLOT
Storage conveyor
SPACE
SLOT
Slot
SPACE
OUT
SPACE
of yes
of
When the cancellation has been completed, BAM transmits AUTOMAT.OUT composed of a record
for each garment that has actually been canceled. The record format is identical to the one received
6-16

METALPROGETTI
in AUTOMAT.IN. When deleting entire orders BAM will send back all the deleted items and the
status will always assume the status A.
It is also possible to delete one single garment belonging to a certain order , but the order will have
to be sent back correctly, in a second phase, into the fields NGARM and GARMENT.
1.3
COMMAND FOR MANUAL DELIVERY OF A GARMENT THAT IS NOT READY
The file has to contain one record for each garment that is being delivered manually.
FIELD
DESCRIPTION
NOTE
Compulsory
LOT
Lot code
NGARM
yes
GARM
yes
GARCODE
Garment code
GARDESC
Item description
PERC
yes
HUNG
S/N
yes
STATUS
New record
M
unloading
MAGSLOT
Storage conveyor
SPACE
SLOT
Slot
SPACE
OUT
SPACE
manual yes
Once the manual delivery has been completed, BAM transmits AUTOMAT.OUT composed of a
record for each garment that has been unloaded. The record format is identical to the one received in
AUTOMAT.IN. If the unloading order refers to a garment, not yet ready, belonging to a lot that
does not exist, the lot is created and then unloaded.
1.3
COMMAND FOR MANUAL DELIVERY OF A GARMENT THAT IS READY OR THAT

IS READY AND OFF CONVEYOR
The file has to contain one record for each garment that is being delivered manually. It is not
possible to delivery manually a single garment that is READY if in the lot several garments are
READY.
It is also possible to deliver manually a single garment if its status is READY OFF CONVEYOR.
FIELD
DESCRIPTION
NOTE
LOT
Lot code
7-16
Compulsory

METALPROGETTI
NGARM
yes
GARM
yes
GARCODE
Garment code
GARDESC
Item description
PERC
yes
HUNG
S/N
yes
STATUS
New record
M
unloading
MAGSLOT
Storage conveyor
as transmitted by
Automat.out file
SLOT
Slot
as transmitted by
Automat.in file
OUT
Position
conveyor
manual yes
off
This command has been simplify, to allow to send only one line for the order to be
unload/Deleted and can be used to DELETE an order not ready or to UNLOAD an order
from conveyor to the manual unloading point:
FIELD
DESCRIPTION
NOTE
LOT
Lot code
NGARM
BLANK
GARM
BLANK
GARCODE
BLANK
GARDESC
BLANK
PERC
BLANK
HUNG
BLANK
STATUS
Unload / Delete command
MAGSLOT
BLANK
SLOT
BLANK
OUT
BLANK
CUSTOMER
BLANK
8-16
Compulsory
yes

METALPROGETTI
ORDERTYPE
0 = Bam optimize
by slot
1 = Bam respect
the sequence given
on the file
ORDERKEY
Not Used
ARM
Extraction ARM to use
XXX
Once the manual delivery has been completed, BAM transmits AUTOMAT.OUT composed of a
record for each garment that has been unloaded. READY garments that were hanging on the
conveyor will mean a new record on AUTOMAT.OUT for each new free slot. The record format is
indicated below in paragraph 3 SLOT STATUS RECORD.
1.3
COMMAND FOR AUTOMATIC DELIVERY AT THE GATE OF A GARMENT THAT IS

READY
The file has to contain one record for each garment that is READY. It is not possible to delivery
manually a single garment that is READY if in the lot several garments are READY.
FIELD
DESCRIPTION
NOTE
Compulsory
LOT
Lot code
NGARM
yes
GARM
yes
GARCODE
Garment code
GARDESC
Item description
PERC
yes
HUNG
S/N
yes
STATUS
Automatic unloading
yes
MAGSLOT
Storage conveyor
as transmitted by
Automat.out file
SLOT
Slot
as transmitted by
Automat.in file
OUT
SPACE
This command has been simplify, to allow to send only one line for the order to be unload on
the automatic PICK-UP
9-16

METALPROGETTI
FIELD
DESCRIPTION
NOTE
LOT
Lot code
NGARM
BLANK
GARM
BLANK
GARCODE
BLANK
GARDESC
BLANK
PERC
BLANK
HUNG
BLANK
STATUS
Unload / Delete command
MAGSLOT
BLANK
SLOT
BLANK
OUT
BLANK
CUSTOMER
BLANK
ORDERTYPE
0 = Bam optimize
by slot
1 = Bam respect
the sequence given
on the file
ORDERKEY
Not Used
ARM
Extraction ARM to use
Compulsory
yes
XXX
Once the automatic delivery has been completed, BAM transmits AUTOMAT.OUT composed of a
record for each garment that has been unloaded. There will also be a new record on
AUTOMAT.OUT for each new free slot. The record format is indicated below in paragraph 3
SLOT STATUS RECORD.
1.6
FILE SETUP COMMAND
The first record of the file contains the key word "RESET" in the LOT field; all the other fields are
empty.
This record must be followed by:
- a record for each garment in the stock being managed
- a record for each slot on the conveyor
Record referring to a garment:
LOT
NGARM
GARMENT
GARCODE
Lot code
Garment code
10-16

METALPROGETTI
GARDESC
PERC
HUNG
STATUS
Item description
Percentage occupied by garment/slot
N" or "S"
R or L as transmitted in AUTOMAT.OUT following the last handling
operation for the garment being managed
MAG,SLOT Fields containing data as transmitted in AUTOMAT.OUT following the last
handling operation for the lot/garment being managed
OUT
Fields containing data as transmitted in AUTOMAT.OUT following the last
handling operation for the lot/garment being managed
Record referring to a slot:
see paragraph 3 - SLOT STATUS RECORD
2 AUTOMAT.OUT
In addition to the cases described above, the AUTOMAT.OUT file is also generated whenever BAM
performs any type of handling operation on the garments being managed.
3 SLOT STATUS RECORD

LOT
Lot code if the slot is occupied by a garment;

00000000 if the slot is free
NGARM
Number of garments in the slot
GARMENT 00000
GARCODE Empty field (SPACE)
GARDESC Empty field (SPACE)
PERC
Slot occupation status (0 if free or > 0 if occupied by garments)
HUNG
Empty field (SPACE)
STATUS
"O"= Indicates slot occupied by garments
L"= Indicates slot free
MAG
Conveyor number
SLOT
Slot number
OUT
Empty field (SPACE)
4 CARD MANAGEMENT
Every time BAM reads the contents of a magnetic card, a file called CARDREAD.OUT is
generated, which contains 3 character strings; each one ends by CR+LF.
Every line represents on the right of the = the content of the corresponding magnetic card ISO track.
Track 1 = data of track 1
11-16

METALPROGETTI
The TP reads the file CARDREAD.OUT and after reading, cancels it.
BAM expects the file SCREEN.IN with the data listed below, but the restoration for the next
reading originates in the key-words CARDIN or CARDOUT.
The SCREEN.IN file followed by CR+LF includes:
a) Special words:
CLEAR
Clear the screen
CARDOUT Send the card out
CARDIN
Accept the card in
When BAM finds these words, it executes the command and gets ready for a new reading
WAITssc
ss = seconds before clearing the screen
R or G for turning on Red or Green lights (Battista 97)
b)
Screen:
LINE
COLUMN
CHARACTER
COLOUR
2 Numeric
2 Numeric
1 Numeric
1 Numeric
DESC
30 Characters
from 00 to 25
from 00 to 80
0=small, 1=large
from 0 to 7
0=Black
1=Blue
2=Green
3=Light blue
4=Red
5=Purple
6=Yellow
7=White
Text
For the temporary message which is always on the screen, there is a permanent exchange file which
is never cancelled, INSCARD.TXT consisting of three lines with the text:
SCAN THE
BAR CODE
or
INSERT
THE CARD
12-16

METALPROGETTI
13-16

METALPROGETTI
Example of files:
---- TP create a new two pieces order
C:\BAMEXC\AUTOMAT.IN 30/12/2002 09:09:46
12000539
020100003389
12000539
020200003390
Regular
Trousers
033SR
033SR
---- MP send the commit file (this is an option that you can disable)
C:\BAMEXC\AUTOMAT.OUT 30/12/2002 09:09:46
12000539
020100003389
Regular
12000539
020200003390
Trousers
033SC
033SC
---- MP send the file after a loading operation

06020548
1 0
06020548
1 176006997
Pants, Regular
100 O0100028
100SL0100028
---- TP send the comand for a internal unload

06020600
---- MP Send the command to inform that the unload has been made
0 0
06020600
2 175006331
Pants, Regular
06020600
2 275006367
Pants, Regular
---- A customer insert the card on the card reader
MP send the card information...
C:\BAMEXC\CARDREAD.TMP 08/01/2003 10:39:22
Trak 1=%B4323721751280002^WAGNER/SUSAN J BROWN^04101018005102
Trak 2=;4323721751280002=04101018005102688?
Trak 3=
Type =
---- TP send some comands to write information on the screen
C:\BAMEXC\SCREEN.IN 08/01/2003 10:39:22
CLEAR
101916Card Inserted
14-16
0 L0100549
33SU0100549
33SU0100549
00688000000?

METALPROGETTI
142016Please wait...
WAIT90
CLEAR
CARDOUT
CLEAR
062516Welcome
101616Wagner, Susan
151906There are 2 orders ready
182216Please wait
WAIT60
---- TP send the commands to unload some orders from the 24H pick up machine
01000044
01000045
---- MP Send the command to inform that the
C:\BAMEXC\AUTOMAT.TMP 08/01/2003 10:41:02
0 0
01000044
3 100003589
01000044
3 200003590
01000044
3 300003591
unload of order 01000044 has been made

Regular
Slacks
Sleeveless
---- TP write some message on the screen to inform the customer

CLEAR
101516Delivering 1 of 4
WAIT30
CLEAR
WAIT30
CLEAR
WAIT30
15-16
P
P
0 L0100208
33SU0100208
33SU0100208
33SU0100208

METALPROGETTI
---- MP Send the command to inform that the unload of order 01000045 has been made
C:\BAMEXC\AUTOMAT.TMP 08/01/2003 10:41:09
0 0
0 L0100282
01000045
1 100003592
Mid-length
33SU0100282
---- TP write some message on the screen to inform the customer. The delivery operation has been completed
now.
CLEAR
WAIT30
CLEAR
CARDOUT
102316Thank You
141016Please Come Again
WAIT05
16-16

Supusa e (Bam)

Uploaded by

Copyright:

Available Formats

Supusa e (Bam)

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Supusa e (Bam)

Uploaded by

Copyright:

Available Formats

AUTOMET Revision 1.

Battista Automat Metalprogetti (BAM) is a software procedure produced by the

AUTOMET Revision 1.0

BAM CHECKS FILE AND

AUTOMET Revision 1.0

lot. Once the length of the code to use has been

AUTOMET Revision 1.0

"U" = for retrieval/retrieved at automatic

Additional description for the item

0 = Pickup not allow

AUTOMET Revision 1.0

Drop off time

READY hanging on sorting conveyor

READY unloaded from sorting conveyor on chain

READY loaded on automatic loading chain

00123 @100@ READY ordered to be unloaded from conveyors

READY hanging on storage conveyor

READY OFF CONVEYOR

RECORD NEW LOT COMMAND

aligned on the left

Total number of garments in the lot

Garment order number in the lot

Percentage occupied by garment/slot XXX

Garment hanging or not

aligned on the left

AUTOMET Revision 1.0

Position off conveyor

Customer name or code

There is no AUTOMAT.OUT response.

GARMENT RECORD CANCEL COMMAND

aligned on the left yes

Total number of garments in the lot

Garment order number in the lot

Percentage occupied by garment/slot XXX

Garment hanging or not

aligned on the left yes

Position off conveyor

AUTOMET Revision 1.0

COMMAND FOR MANUAL DELIVERY OF A GARMENT THAT IS NOT READY

aligned on the left yes

Total number of garments in the lot

Garment order number in the lot

Percentage occupied by garment/slot XXX

Garment hanging or not

Position off conveyor

aligned on the left yes

COMMAND FOR MANUAL DELIVERY OF A GARMENT THAT IS READY OR THAT

aligned on the left yes

AUTOMET Revision 1.0

Total number of garments in the lot

Garment order number in the lot

Percentage occupied by garment/slot XXX

Garment hanging or not

Position off conveyor

aligned on the left yes

aligned on the left yes

Unload / Delete command

AUTOMET Revision 1.0

Extraction ARM to use