|
>I was glad to see that DECmcc BMS V1.2 has reached the SSB. However, I
>have a couple of questions that I need answered so that I can pass the
>information along to my customer running DECmcc SMS V2.1.
>
>Q. Since SMS is no longer part of the DECmcc package with the V1.2 release,
> do we still plan to upgrade those customers with SMS to EMS V2.2 at no
> charge provided they have the software update service?
The Corporate Product Manager for this is Junell Silver
(delni::j_silver) , I'll ask her to answer for US customers .
In Europe we plan to provide DECmcc SMS customers one part-Number
in order to get the DECmcc EMS License . The price of this Part-Number
will be very low (# 100 $) , mainly because in Europe we have a large
numbers of customers under services contracts or Warranty .
>Q. How far away are we from having the EMS V2.2 ready to ship?
Again for Europe , latest dates for DECmcc EMS 2.2 , DECmcc
Director 1.2 , and all the a-la-carte FM's are targeted for
mid-September . This means that this should be available
around mid-August in the US . Again Corp. Product Mgr need
to confirm .
>Q. In the interim (between BMS V1.2 and EMS V2.2) do we have an official
> policy for providing V1.2 functionality to those customers who have
> invested their time and trust in the original DECmcc 1.0 products
> (e.g., SMS V1.0, EMS V1.0) which has promised an upgrade path all along?
As you have seen in this notes file , you can have DECmcc-BMS ,
ELM , TSAM interim PAK and install in the meantime this on your
customer site .You need to go through the simple procedure
described in this notes file .
Hope it helps ,
Regards ,
MaRc MaLaIsE , European Network Mgt Marketing Mgr .
ps - who is your customer ?
>My customer invested in DECmcc SMS V1.0 when it first came out in Nov '89.
>They have purchased four complete management systems to-date and have upgraded
>hardware at two locations. They have been waiting patiently for V1.2
>functionality for nearly a year now since we began delivering the PIDs on
>DECmcc futures. There is an element of support for MCC within this
>customer organization that wants to proliferate MCC as their company
>management standard and roll it out to 30 additional sites. However,
>there are also the DECmcc antagonists who see DECmcc as "proprietary" since
>it was not part of the OSF/DME selection and therefore they are pushing
>other management solutions that *ARE* OSF/DME "compliant". I keep fighting
>the battles and delivering the appropriate messages around our directions,
>but the DECmcc supporters are finally backed into a corner to the extent
>that they are asking "Where's the beef?"
>They want V1.2. And they don't want to wait til October to get it.
>
>Please. Someone tell me what I can do to help the customer, so that we
>(Digital) can help ourselves.
>
>If any product management folks would like to discuss this off-line,
>please feel free to call or send mail to the address below.
>
>Thanks
>
>Merlin Clayton
>DTN 445-7217
>(314)991-7217
>TRIGG::CLAYTON
|