Murray Automation can interface with Agvance using the following blender types: SSI Standard XML, Murray Liquid Extended or Dry Extended (TXT), or Murray Liquid Extended 2 or Dry Extended 2 (TXT).
Blender Type: SSI Standard XML Interface
Product Setup
Product setup is done at Hub / File / Open / Products.
- The Blender Factor, found on the Blend Setup tab of the product file in Agvance, is required on products used with this interface.
- The Product ID on the Profile tab of the product file in Agvance must match the Serial ID in Murray.
- Blending Units, also found on the Blend Setup tab in Agvance, must match the Import/Export Unit of Measure in Murray.
Product Set
Product Sets are maintained at Blending / Setup / Product Sets.
- On the Blender Interface / Print Preference tab, set the Blender Type to SSI Standard XML.
- For the Data Storage Path, select a path that is a shared folder where the file is created for the blender interface.
- The Shipped from Location Code is required for the SSI Standard XML Blender Type, but not used by Murray. Enter a user-defined number. Some companies with multiple locations use this area for the location number.
How it Works
- The Blend Ticket is created in Agvance using one of the Murray product sets with products set up with a Blender Factor. The Blend Ticket is created for application of a whole order. Agvance sends the product totals for each product. The Murray software allows the operator to resize batches to the truck.
- Agvance sends the ticket to the shared folder when the Create Automated Blender File option is selected on the Print Blend Documents window.
- Murray retrieves unimported tickets with a status of Ready from the shared folder.
- The product identifiers (Blender Factor) are matched with the Serial ID in Murray.
- Customer information is compared to the Murray records. If the customer is not found in Murray, a customer record is added.
- Murray uses the Blending Units to calculate the proper amounts to import.
- If any product identifier (Blender Factor) cannot be matched, Murray does not import any of the batch information in the file and moves on to the next ticket.
- The XML can be modified in Agvance and exported with changes until any portion of the batch has been made. When the batch is sent to be made, the ticket status changes from Ready to In-Process.
- When the last batch in Murray is completed, the ticket status is changed to Done and can be imported back into Agvance.
Blender Type: Murray Dry and Liquid Extended and Dry and Liquid Extended 2 Blender Type
Product Setup
- The Product ID on the Profile tab of the product in Agvance must match the Murray Part Number.
- Blending Units on the product in Agvance must match the Murray Unit of Measure in Murray.
Product Set
- On the Blender Interface / Print Preference tab, for the Blender Type select Murray Dry Extended, Murray Liquid Extended, Murray Dry Extended 2 or Murray Liquid Extended 2.
- For the Data Storage Path, select a path that is a shared folder where the file is created for the blender interface.
How it Works
- A Blend Ticket is created in Agvance using the product set to send to Murray and with products set with a Blender Factor. The Blend Ticket is created for application of a whole order. Agvance sends the product totals for each product. The Murray Dispatcher software allows the operator to resize batches to the truck.
- Agvance sends the ticket to the shared folder when the Create Automated Blender File option is used. The file has a .txt extension.
- Murray matches the Product ID with the Murray Part Number, and uses the Murray Units to calculate the proper amounts to import.
- The customer information from the file is compared to the customer record in Murray. If the customer is not found, it is added.
- When the last load in Murray has been completed, a file is created with a .txt extension and has a 2 in line 1 of the file. This file can be imported back into Agvance.
