SSI Standard XML Automated Blender Interface

Overview

How does the SSI Standard XML Interface with different Automated Blenders?

Setup

Blender Type: SSI Standard XML Interface

Product Setup

Edit Product setup at Hub / File / Open / Products.

The Blender Factor found on the Blend Setup tab of the Product file in Agvance is required and must be set for the product to be included in the XML file.

Note: For Kahler, the Blender Factor must match the Import/Export ID in Kahler.
For Junge, Blender Factors cannot be between 41-70.
For Murray and Yargus, the Blender Factors can be any sequential numbers.

Blending Units, also found on the Blend Setup tab in Agvance must match the Import/Export Unit of Measure.

Product Set

Product Sets are maintained at Blending / Setup / Product Sets.

1. On the Blender Interface / Print Preference tab, set the Blender Type to SSI Standard XML.
2. Designate the Data Storage Path by selecting a path to a shared folder where the file is created for the blender interface.

Shipped from Location Code is required for the SSI Standard XML. Enter a user defined number. Some multiple location companies use this area for the location number. If the location number is entered, Kahler uses it to setup batch information for multiple locations.

How it works

1. The Blend Ticket is created in Agvance using one of the SSI Standard XML product sets using products setup with a Blender Factor. The Blend Ticket is created for application of a whole order. Agvance sends the product totals for each product. The Automated Blender software allows the operator to resize batches to the truck.
2. Agvance sends the ticket to the shared folder when the Create Automated Blender File option is selected on the Print Blend Documents window.
3. The Automated Blender retrieves unimported tickets with a status of Ready from the shared folder.
4. The Automated Blender will use a product identifier in the XML file to recognize products used, e.g. Blend Factor for Kahler and Product ID for Murray “Control Pro.”
5. Some automated blender software programs store customer records. If that is the case for the user's automated blender, the customer information will be compared to the information contained in the XML file. If the customer does not exist in the automated blender software, a record for the customer will be added.
6. The Automated Blender uses the Import/Export Units to calculate the proper amounts to import.
7. If any product identifier cannot be matched, the Automated Blender does not import any of the batch information in the file and moves on to the next ticket.
8. The XML can be modified in Agvance and exported with changes until any portion of the batch has been made. When the batch is created the ticket status changes from Ready to In-Process.
9. When the last batch in the Automated Blender is complete, the ticket status changes to Done and can import back into Agvance.

Note: There are three different ways to import.

1. In the Blending module, select the desired ticket and click Read Blender. This feature looks for the file that matches that specific ticket.

2. Edit the desired Blend Ticket and click Capture Blender at the bottom of the window. 

3. In Blending, navigate to Edit / Import Automated Blender Done Files. This utility is useful when there are multiple files to import.

After the XML file is imported into the Blend Ticket, the Blend Ticket is automatically marked as Loaded and the inventory in Agvance is affected.