Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Eyf Code:        The frame piece description sent from Eyefinity
Part Type:        “F” for frame piece
Frame Manuf: The Rx-Universe manufacturer to use for this piece
Frame name:   The Rx-Universe frame name to use for this piece
Frame type:     The Rx-Universe frame type (groove, etc.) to use for this piece
Eye:                 The nominal eye size of the frame
DBL:               The nominal DBL or bridge of the frame
Temple:           The nominal temple length of the frame
Color:              The Rx-Universe color to use for this piece

3.0    Setting Eyefinity Communications Parameters

Rx-Universe uses an internet connection to download orders from Eyefinity using ftp (file transfer protocol).  The computer that Rx-Universe is running on (usually the server, running as a thin client application), must have an active connection to the internet.

...

Eyefinity pause (minutes):      selects the interval to check Eyefinity for orders.  This should be set to some delay to prevent Rx-Universe from constantly checking the Eyefinity ftp site.
Create Eyefinity Log:             If checked, Rx-Universe will create a file EYEFIN.LOG which contains a log of each step in the communication process.  This file is located in the default Rx-Universe folder.
Send shipping info: If checked, will send shipping info such as tracking number with the Eyefinity status updates
User name:                              This is the login name for Eyefinity, assigned by Eyefinity.  It is case-sensitive.
Password:                                This is the password assigned by Eyefinity.  It is case-sensitive.
Base file name:                       This is also assigned by Eyefinity.
VSP account #:                       This is the lab’s account number for billing to VSP.

4.0    Processing Eyefinity (and other) Remote Orders

Processing of Eyefinity orders is consolidated into the Remote Order Processing module of Rx-Universe.  From the “Remote” menu, choose “Remote Order Processing”, or start the automated remote order processing screen on the server.

...

As each order is processed, it is placed into the Active Orders table.  If the order was processed (blanks could be selected, pricing was done), a work ticket is automatically printed.  If there were any problems with the order, the order is saved unvalidated for later review at the lab.

5.0    Sending Status Back to Eyefinity

Eyefinity provides the ability for the lab to send back status on jobs, permitting the dispenser to see the status of their jobs in the lab.  Rx-Universe allows the lab to control how much information to send back to the dispenser.

...

To ensure proper reporting of Status back to Eyefinity, the lab needs to ensure that the job tracking stations are set up to properly indicate when jobs pass through each Eyefinity stage of the lab process.

6.0    Viewing Eyefinity Orders (valid and unvalid)

Orders received from Eyefinity (and other sources) are stored in the Active Order table along with other orders.
On the order entry screen, the source of the order (if not manually entered) is shown as follows:

...

This is a standard scrollable list box – you can use your mouse or keyboard to scroll up and down to see the entire original order.  The first portion of the order, to the EOJ=END OF JOB line, is the order that Rx-Universe created from the Eyefinity order (in standard Rx-Universe VCA/GIF format).  Everything after the EOJ line is the text as it came from Eyefinity.  While we recognize that labs won’t often have the information to interpret all of the information shown, it is useful to verify customers sometimes (especially if an order has been received through Eyefinity, in error, from a customer that the lab doesn’t have).  It may also be useful when working with technical support at either Eyefinity or Rx-Universe to resolve issues.

7.0 Daily Process for Eyefinity Orders

  1. Process jobs from Eyefinity throughout the day (this will be automatic in many cases).

  2. Check the Eyefinity Translation table for new entries with no corresponding Rx-Universe translation.  Customer records, Lens codes, and Addons should be checked regularly.  Frame items should be checked if the lab supplies frames for orders.

  3. At least monthly, run the option to update lens codes from OSI web site.

8.0 Checklist Before Implementing Eyefinity Interface

  1. Install Internet connection from server (high speed is best).

  2. Obtain list of Efan accounts that have placed orders within the past 60 days, from Eyefinity.  Build Customer translation file with Efan and Rx-Universe account numbers.

  3. Set up any addon codes that will be coming from Eyefinity - these are usually a combination of the pricing code (QT, QN, etc) plus the description of the coating. A list of current addons is released by Eyefinity monthly.

  4. Obtain your Eyefinity basename, username and password for their ftp site.

  5. Set up the Eyefinity customer number (the account you use to bill Eyefinity)

  6. Set up the VSP price list if desired (VSP pays what they calculate is due based on the job as entered by the ECP, not based on what the lab sets up in pricing).

9.0 Enhancements in March 2007

Eyefinity has made several enhancements to the interface effective 27 March 2007:

...

Shipping information - Eyefinity can also now accept shipping information back from Rx-Universe.  To do this, a lab must use the shipping method field, on the account and/or order, to actually identify which shipper is used for an order.  If the “Send shipping info status” field (above), is checked, then this will be sent back to Eyefinity as the shipper.  While Eyefinity also accepts a tracking number, Rx-Universe does not store this nor send it back.

10.

...

0 Description of Communications

Eyefinity makes orders available, and receives status information, by means of encrypted files on their ftp site.

...