New filters in Annapurna Browse Orders.

 There are some new filters to assist.

In the customer area, click on Chains. The customer search options have been expanded to allow for

Business Area.

Search by customers in a specified business area.

Care Group.

It is now possible to collect customers into a care group that is specific to the logged in user.  The care group is useful if customer service operators work with particular customers and using this they can keep an eye on the orders for those customers. Customers can be in more than one care group.

To add or remove a customer from the care group click on the care group link.

Multiple Versions.

When a reject is recorded that requires lenses or the frame to be scrapped then a version number linked to the order is incremented. It is now possible to search for orders where there multiple versions created. The version number is placed before the tray so it is possible to sort by version, if so wished.  A version code of 2R means a version is now 2 and the right lens was scrapped last time, 3L means it is version 3 and the left was scrapped last time.

Target Search.

The target search (archery target icon) shows ordes with target date of this day.  It is now possible to refine this with selected attributes.

Treatment combinations

 There is a document here to explain how to treatment combinations such as a tint requires a UV filter can be set up.

Treatment combinations

Customer Options in the customer record have been moved.

 The optical processing options in the customer record have been moved to a new screen tab. This is to allow even more options to b e added in the future.

RFID

 There is a new module which will act as a bridge between RFID from Nordic and Annapurna.

This means that a RFID tag can be placed in a tray and when the tray is presented near the scanner then a message is sent which is picked up the new module. In turn, this is created into a tracking message as though the tray had been scanned by a barcode scanner.  Different RFID bridges can be set to indicate different Annapurna status points.

VCADevice over a VPN

 It is now possible to run Annapurna and send OMA files over a VPN to a copy of VCADevice in an external location for edging.

Tracers supported

 From time to time, e are asked what tracing formats are supported. This summarises:

Format.

There are 3 formats that we support.

OMA/VCA - preferred

Nidek

Hoya

If it is a Nidek or a Hoya tracer then it is necessary to check if  the tracer is set to the bespoke format.

OM/VCA format is preferred as that is the format that is used to transfer trace data to other systems so the Nidek and Hoya formats are converted. It is better to get the data in this format to avoid any risk of potential data loss in the conversion.

Communication.

Serial

Ethernet

USB Driver

Serial

This can be either a serial cable or more likely a serial to USB convertor at the PC end. Both of these 

Ethernet.

This is a connection over the LAN. There are two methods, where the tracer is the 'server/host' or the PC is. Which depends on the tracer manufacturer.

USB.

This requires a USB driver to be installed. Currently there is only a Hoya driver provided.

The default is OMA/VCA over Serial communication.

SF6 Option details

 There is an additional CSV file that can be used to set options requirements for the SF6 catalogue. On the SLZLang / SF6 tab there is a new link SF6 Option Details.  This is in version 2.70.

If this is clicked then a CSV file is opened with various columns for the information that SF6 require. Earlier versions made an educated guess on the values based on the treatment type and description.