The Importance of Reviewing New Technical Documentation.

When you are looking at upgrading any of your application software programs it is important to review ALL documentation related to the installation and configuration requirements, BEFORE attempting to install any new software.  This is especially true because of recent changes in both software and hardware technology.

When this isn't handled properly various problems can arise.

Some examples of this are:

If moving from a 32 Bit to 64 Bit Operating system environment, any or all of the following
may be present:

• The software application may require an updated 64 Bit compatible run-time.  - Assuming that this is available, it may require re-installation of the core software application.  If you are using a Client Server application, the workstation clients will most likely need to be re-installed as well.

• A supporting application that is used by the core application may be incompatible with the new 64 Bit Operation System, or require the purchase of new licenses for the new environment.

• The new operation system or application  may not have drivers for some of the existing peripheral devices that you intend to use with the new update.  This may require purchasing new equipment.
  So ideally, the should be known in advance.

• Technical Documentation is only as good as the ability or willingness of a person to follow it.

• Project documentation should be reviewed ahead of time, during, and afterward in order to confirm
  the completeness of the project at hand. - Having a poor plan is sometimes worse than having no
  plan at all.

• Have a test environment is preferred, so that you can have a good idea what to expect when the live
  update is done. 

• When a project is complete, changes made to the overall configuration should also be reflected in
  the documentation. - Most of us are not going to remember details, months (or perhaps years) later.

• Considerable time, frustration, and expense can be incurred by not properly documenting, or
  considering things. 

• There is a need to ave sufficient backups and documentation that will allow you to go backwards
  in the event the update process fails due to some yet as known issue.  - Time is money.  If either you or CCS has to spend more time on something, this results in increased support costs.  This is especially critical  for you the issue involves recovering a system that is down.

If you are contemplating any major projects involving your systems, please contact the CCS Retail Systems Support Department for a review.