Subject: From: Date:

Re: [ECS] Support, custom interfaces Bill Walters Wed, 30 Sep 1998 23:28:31 -0500

---

ust some comments for what it's worth to all -

 
> While I don't believe that $50/year would be excessive for what we get in
> terms of support now, I should point out that ECS is $195.  So that annual
> $50 is roughly 25% of purchase price.  I am responsible for a bunch of
> equipment and software at work, and annual support contracts generally cost
> in the 10%-15% of purchase range.
> 

Well and good and I certainly understand.  However, this is not the
first time we've gone through this thread and I'm willing to be that
Mark hasn't seen a single nickel from anyone.....  Myself
included......  I downloaded ECSD 3.4 and inquired about upgrade
charge... Response was that it was 0$.....

I, too agree, that we who participate here get far more out of ECS than
"joe average consumer".... but..... If Mark were to institute "rolling"
authorization code (i.e., software works for a year, then "kapoot"), I'd
be off ECS like a heartbeat.... Bet most folks here would be also....  

Folks, you don't provide a "consumer product" and then expect annual
licensing fee....  This would be the "death" of ECS ('D too!)

However, IF ECS (D) came with 6 months E-mail support as part of the
package, then well and good; additional support could be "subscibed" for
an additional $25 per year....That's not unheard of and entirely
reasonable in light of the purchase price of the package.  Those of us
who are somewhat familiar could provide "free" support (user group
style); but past the 6 months, a direct response from Mark, well...... 
that's what you pay the $25/year for.....Yea, I know, would be hard for
Mark to "bite his tongue" ........

> It's possible that Mark is gearing up for this even as we speak.  The new
> Authorization code that replaces EVMOVE seems to enable just this model.
> Once a year, Mark could change the auth code - only those with support
> contracts would get the new one - everyone else gets to keep using the old
> one.

Now there's a novel idea, and one which I could "pony-up" for... Upgrade
of capabilities doesn't come for free and Mark is (should be) justified
in asking for "nominal" upgrade fee.... Hell, I just upgraded to 3.4
after almost a year.


> The only place where this *will* become a headache for Mark is in bug fixes.
> To me, bug fixes are a right, not a privilege, and you should be able to get
> them without a support contract.  But for Mark to be able to give out bug
> fixes on last year's software will require him to split his build trees and
> support multiple releases... not fun.
> 

You're correct here, too.  Perhaps Mark could maintain separate "builds"
for a period of 2 years; then appropriate "upgrade" fees would apply.


> Perhaps Mark could expand his Auth codes to be aware of what features you
> are entitled to depending on whether or not you have a support contract or
> when your last year of support ended.  Then it could be a single build, with
> features enabled/disabled per your Auth code.

I don't think this is a very good idea and one of the reasons I didn't
consider "Cyberhouse" beyond looking at the pretty ad; extra charges for
each and every module that I would want to use.... Kinda like buying an
accounting system and then paying extra for "trial balance" stuff...
yeech....

> 
> I'd rather not have to buy ECS features one-by-one.  Buying the hardware is
> often expensive enough.  And I think it would splinter the user base too
> much.
> 
> Mark, I don't want to tell you how to run your business - I just want to
> show my support and my belief that your continued improvement of ECS is
> worth some extra money, at least to me.  I'm growing to depend on ECS more
> and more every day, and would hate to see something happen to take it away.
> I guess I want to protect my investment.
> 

I truly think that's all we all want to do....  Problem is that our
intentions aren't helping Mark stay in business.

Mark's root problem is that ECS is a "nich" software product without any
substantial advertising support.  He isn't even in the HAS Catalogue
which is where most newcomers get their first taste of HA....  I can't
even think of the last time I saw ECS mentioned in
"comp.home.automation" newsgroup......  

If we TRULY want to help Mark, we need to become proactive.... Sending
him $25 or $50 per year won't help - he needs new customers, and lots of
them!

I've thought of trying to write a "PRIMER for ECS" and place it
(gratefully) in the public domain....  I don't think I'm smart enough
but perhaps if enough of us "collaberate" we could turn out something
truly worthwile....  As a "newcomer" I have to admit being truly
"put-off" by the complexity of the documentation, and I printed out all
of it!  Unfortunately, there's no easy "starting point" other than ECS
LITE and the CFG file for that is, well, above the audience which Mark
needs to target.  Perhaps "plug-in" modules for various functions would
help; I'm willing to "carve up" my CFG file (its an UGLY mess, but it
works for me!) and place it in PD...  I'm also willing to take a shot in
the next 2 months on trying to put together a "PRIMER" for ECSD; anyone
else care to collaberate?  Sorry, but I don't know squat about ECS
(windows) and judging from the information I've gained here, without
some capability for retrieving phone messages elsewhere other than the
computer keyboard (which should be "out of sight/out of mind" in a truly
automated home) Mark has some serious work to do to make ECS completely
functional....  Heck, who wants to blow $1k and not be able to have the
functionality of a $29 answering machine?????

My 2 cents worth, so now "flame" away....

Bill Walters

---