Local Launcher for Annapurna.

 

Annapurna Launcher.

 In some configurations, where Annapurna is being used remotely from the server, it can be beneficial to have Annapurna installed on a local PC.

To manage this, AnnapurnaStart has been created.

Installation.

AnnapurnaStart needs to be installed on the local PC. There is an installer for this. This can be downloaded from

https://www.hawkstonedesign.co.uk/downloads/AnnapurnaStart_Install.exe

It is suggested that this is installed in the “Annapurna Progs” folder on the server and this can then be used to update the local PCs.

The installation will create a shortcut on the desktop.

Operation.

On the first time, AnnapurnaStart will ask for the location of the “Annapurna progs” folder on the server where Annapurna is installed. 

When this is set then a log in screen will appear.  Log in with the Annapurna credentials.

The software will then check for updates to Annapurna. If there are updates then these will be installed on the local machines. When Annapurna is up to date then Annapurna will start and the AnnapurnaStart will close.

 

________

 

Supplier Routing for rejects and by Order Type.

Local Supplier.

There are new settings in Annapurna to send glazed orders to a local supplier and uncut orders to another supplier that may be cheaper but the turnaround is longer.

In a similar way, rejects can also be set to be ordered from a local supplier.

It is still possible to set lens designs, coatings and frames to a designated supplier as any rules for these will take precedence. Any source rules for the customer will also take precedence.

Coating Warranty

 

Coating Warranty.

If an order is returned for a coating failure then it should be recorded as a return in Annapurna.  If, on examination, it is deemed that the lenses should be returned to the coating supplier then a new tick box has been added into the ‘Send to Coating’ to indicate that it is a return under warranty. 

A layout field has been defined to allow “Return under Warranty” to be printed on the accompanying printout to be sent with the lenses.

The cost price for the lenses will be set to zero.

Lens Colour and Corridor Selection

 There is a problem in that too many lenses can clutter up the lens selection lists.  To reduce this, a new CSV file has been created and can work with a reduced lenses csv file. The purpose is to select the lens, colour and corridor and from this create a composite code.

A short code is created to describe the lens and then colour and corridor options are added into the extended file.

For example, the short code for the lens is set as 

ABCDE

It is available in Clear, Brown and Grey.  It is available in 14, 16, 18 corridors.

Theextended.csv file has 4 columns.

Short Code

Short Lens Description

Colours

Corridors

The colours and corridors are colon(:) lists.

So the entry in Extended csv will be

ABCDE,Some Lens name, CLR,BRW,GRY,14:16:18

When a lens is selected then a composite code is created.  If CLR and 16 is selected then the composite code is ABCDEFCLR16.

The colour codes are held in the master treats csv file so that a description of the colour is presented in the selection screen.  The family for these colours should be set to a special code so the treatment does not appear in the usual operation. The usual family code is SPETINT.

Lens with fixed height on the centre line and specifying a specific LTYPE.

 There are some updates to the Technical data.

 A new option has been added for lens where height is not required.

Information here

There is also a new field for setting the LTYPE in the OMA files.  An example would be for a lens that is sold as a single vision but NV is to be set as the LTYPE.

Enhancement to the Source Rules in Annapurna

 It is now possible to put entries in the Exclusions column in the Sources csv file,

Column J should be entitled Exclusions.

It can contain a code lens or treatment and then this rule does not apply.

It can also contain TINT or UV to exclude these generic values.

It can also content DESIGN: or INDEX: to exclude designs or index.

I have just added ADD:  eg ADD:3 to mean that Adds over 3 are excluded.

If an exclusion is found then the Sources csv file is scanned for another matching entry.

User Reports Folder

 It is now possible to set a specific sub-folder for saving reports. The reports will be saved in a sub-folder below the reports directory. Annapurna will need to be started with runtime parameter

REPORTSFOLDER=roger

This will save the reports in "files"\reports\roger.

There is a special case

REPORTSFOLDER=user

In this case, the subfolder will be logged in Annapurna user name so if log in as Chris and 

REPORTSFOLDER=user is specified then the reports will be created in folder "files"\reports\Chris.