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.

Component Hotel

 The component hotel in Annapurna has been updated.

The component hotel is used to store the components waiting for other components to arrive.  When a frame is sent in, it is automatically assigned to be be put away in the hotel. 

The production / put away module is used to put away components in the hotel.

The purchasing / receive module is used to receive components into te lab. If there is a waiting component in the hotel then advised on the room the matching component is saved in. If it is the first component then advised to put away the component.

Frame Repair Module Added

 A new module has been added to allow orders to be sent off-site for repairs. A configurable layout is also provided for the paperwork to accompany the frame.

Using Annapurna to create a SF6 catalogue.

 Information can be found here