Showing posts with label Thin-Client. Show all posts
Showing posts with label Thin-Client. Show all posts

Tuesday, January 29, 2008

Customer Relation Management

At Tuppas Software, I spent the last day working on part of our Customer Relation Management (CRM) package for Stone Interiors, a manufacturer of custom countertops. We had a photocopy of one of their "Estimates" which could be printed in one of two ways: either with all of the detail, or just summarized. This Estimate, along with the schematics, is then given to the customer for final approval.
For each Estimate, there are quite a few options available - override pricing, on either an individual line item or for an entire section (such as a kitchen or a bathroom); discounts, either a flat amount or a percentage, some items being charged by the square foot, others by the inch, and still others by the piece; different price groups; etc.
Since our CRM solutions and CRM systems are thin-client, web based, we're using ASP to display a copy of the estimate before printing it. So it was a challenge to blend the HTML, ASP, and CSS together to produce the Estimate, to get all of the formatting and layout to match their existing estimate. I have to get back in touch with Chad at Stone to go over it, but it's now quite close.
At the end of yesterday I was given some changes to their Inventory System and was able to make most of them then. The rest I'll be working on today, along with MES Systems for other clients.
More later. Until then.
Hal Hamer

Friday, January 25, 2008

Why Should I Look at Thin Clients

In the right environments/situations, Thin Clients can be quite beneficial from a cost and performance point of view. In the wrong situation, well... This paper will look at various reasons why someone might want to consider using Thin Clients in some situations instead of using Thick Clients.

Advantages

  • Costs
    • Hardware
      • Since a Thin Client does not contain a disk drive or fan, and needs less application memory, Thin Client hardware is less expensive, thus saving on initial cost.
      • In most cases a Thin Client terminal can remain in service for a longer period of time before being replaced, thus saving on replacement cost.
      • In addition to saving on replacement costs, reducing the need to constantly replace hardware also saves on the disposal cost, both to the company and to the environment.
      • Less network bandwidth. No longer are large files being transferred from server to client. All of the work is done on the server.
    • Software
      • Since each Thin Client uses a centrally stored application/program, it does not need each application/program to be installed on its box.
    • Energy Consumption
      • Less powerful hardware requires less energy to operate.
      • It's also possible that with less energy consumption, a less expensive air-conditioning system may be appropriate.
    • Administration
      • No more money spent on having a tech physically update each machine with hardware and software.
  • Security
    • Data
      • Sensitive data is more secure since that data is stored at the server, which will be more protected and in a securer environment, instead of the desktop which is much less secure. This would help not only with problems of theft, but also in those cases where the thick client failed or was damaged.
    • MalWare, SpyWare, Viruses
      • Since there is no hard drive, there is no OS on that hard drive which can be compromised with malware, spyware, or viruses
  • Performance
    • Hostile Environments
      • Since there is no need for a fan, Thin Clients can be put on the shop floor without having to worry that dust will accumulate on the fan blades and ultimately cause the system to fail.
      • Also without fans, the system is noticably quieter.

As with most things in life, there are advantages and disadvantages. Situations where a Thin Client does not work are limited, but they do include using applications where:

  • a high bandwidth is necessary (for multimedia performance)
  • the OS is designed for the use of local, and not network, resources
  • poor network connections

Some places where Thin Clients can be used include the following:

Copyright 2008
Written by Hal Hamer