Re: PARADOX product life cycle

Hi Rodney,

>those doctors depending on the internet to
>conduct business, could not conduct business
>for several weeks after the hurricane we experienced.

If I remember correctly, in certain areas there wasn't any business of any type conducted for a few weeks. However those doctors would have the peace of mind knowing their records were safe and intact and once they could conduct business again all their records were ready and waiting. They would have certainly been millions of times better off than they were. You make some otherwise excellent points and indeed you have identified a critical issue.

>If the WAN or Internet is not available, then
>the system should be able to run in a "crippled mode"
>locally. This "crippled mode" would be one
>where business could continue to function with
>a reduced feature set and update the remote server
>automatically once an Internet connection
>was restored.

That is absolutely 100% correct and in my mind is a key issue to more widespread use and acceptance of this model. That is what I am working on now. I am rewriting my Paradox app for the web with this in mind. Unfortunately it is a complete rewrite and that makes it a very arduous process. It is almost like starting from scratch in many ways.

>Why not consider using a network storage device?

I really don't want to get into supporting hardware. And even though you can tell people not to mess with it, you never know what will happen or what someone will try to do. I did just get one for my network, and will set it up, try it out and see what I think.

>In addition... you should insist that your
>software is sold and installed
>ONLY through a network of trained
>value added vendors (VARS)

That's tough in my position as the variance in price for this type of software is huge and for a variety of reasons I am concentrating on the segment of the market that can't afford the big buck stuff. VARS would rather sell the high priced stuff for obvious reasons. That's another reason I like the internet based approach. You need many fewer technically saavy highly trained people as everything is administered centrally.

You certainly seemed to have hit the nail on the head with most of this analysis. It is a difficult market, but a real world problem waiting to be solved non the less.

Regards,
Roy F.


Rodney Wise wrote:
Roy,

I agree with you... your scenario points out "real" issues. However... those doctors depending on the internet to conduct business, could not conduct business for several weeks after the hurricane we experienced. Internet, Telephone and Cable TV were all down in some cases for over a month.

I believe there needs to be a combination setup. Data specific to a Doctors operations needs to be maintained locally and the application software needs to maintain data synchronization and application updates seamlessly in the background. If the WAN or Internet is not available, then the system should be able to run in a "crippled mode" locally. This "crippled mode" would be one where business could continue to function with a reduced feature set and update the remote server automatically once an Internet connection was restored.

If a doctors office depends on your software for the core functions of their business.... and an on-site IT staff is not practical.... then the software and system must be as "self-healing" as possible.

Why not consider using a network storage device? One of the inexpensive Linux OS computers designed to operate as a network file server.... They are pretty dependable and can be serviced remotely.

In addition... you should insist that your software is sold and installed ONLY through a network of trained value added vendors (VARS).... All VARS who sell your solutions must successfully complete a training course (which you provide at a price)... During this training course, you instruct them how to install and maintain your software... you also provide a list of "Approved Hardware" and "Approved Hardware Configurations". These Vars become the endusers first level for service. The endusers never call you (the software developer)... only the Vars contact you if there is a problem they can't fix.... In which case, if the installed Hardware at the problem site is not approved.... or the Hardware configuration is not approved... you then tell your Var to correct it before you can provide any tech support. If a particular Var seems to violate this list of requirements often, then you drop them as a Var. By not following your instructions, they are giving your software a bad reputation... re-assign the enduser to another Var.

If a Doctor gets a hold of your software through some other means (the purchase of another Doctors business or an auction for instance), then you direct them to their local Var (if they call you). This prevents the semi tech savvy brother in-law from installing your software and creating problems for you and everyone else..

You can have complicated systems running in offices without a full time IT department... but they do need:
1. Software that is not finicky.
2. A "known system configuration".
3. A trained VAR to service them.


.

Relevant Pages

  • Re: PARADOX product life cycle
    ... those doctors depending on the internet to conduct business, ... conduct business for several weeks after the hurricane we experienced. ... Doctors operations needs to be maintained locally and the application ... If a particular Var seems to violate this list of requirements ...
    (comp.databases.paradox)
  • ebooks share lits 80
    ... Handbook of Global Social Policy Public Administration and Public ... What Every Business Leader Should Know ... States in the Global Economy: ... Electronic commerce, XML, Internet ...
    (sci.med.nutrition)
  • Re: why have a server?...advice needed
    ... I don't need to know EXACT SPECIFIC DETAILS, but I'm being forced to generalize because I know nothing of what the business will do, other than it will have 20-30 users and many with laptops. ... If your web site were BUSY, THEN you want it hosted on a reliable system in a data center somewhere where they have emergency generators and multiple connections to the internet in case one fails. ... SBS will allow you to redirect everyone's My Documents and Desktop folders to a folder on the server. ... why not use an online backup tool for each computer. ...
    (microsoft.public.windows.server.general)
  • Annoying Redirect
    ... build a website, business directory, business finder, ... business ideas, business listing, business listings, ... domains, core name, corporate domain, corporate website, ... id names, international domain, internet address, internet ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Barron Thomas: No Unhappy Customers Here ( vs. Unhappy "Prospects")
    ... It goes with the territory in any business. ... Go check it on the internet, ... hour late with the Doctor and the Seneca: ... posting a criticism that "I should have let the Doctor know I was ...
    (rec.aviation.owning)