| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5293.1 | more confusion | MKTCRV::MANNERINGS | | Tue May 20 1997 05:05 | 46 |
| re .0
I ran this search tool looking for all products with the string
"networker", which is a fair test, as quite often customers are looking
for something but they don't know what it is exactly.
The results of the search are incomplete. The names of the products are
wrong, and one product manager is (not listed).
This is a fine example of the anarchy I am talking about in our
information architecture. You search with two different tools and you
get different answers. Using wrong product names is not trivial,
customers are frquently confused about which product is which.
Compare
QA-02LAA-H8
POLYCENTER NetWorker Dec UNIX
QA-2ALAA-H8
POLYCENTER NetWORKER DecUNIX
QA-2ALAA-W8
POLYCENTER NetWorker DEC UNIX
YE-SC75C-01
TL820/NETWORKER CSS SERVICES
(Not Listed)
with this $search of an index of SPD's which used to be available on
DECWRL until recently:
50.98.10: NetWorker Save and Restore for DIGITAL UNIX, V 4.2C
55.04.00: NetWorker Save and Restore Database Modules for Windows NT
Alpha, V1.0
61.27.01: NetWorker Save and Restore for Windows NT Alpha, V 4.3
64.46.01: POLYCENTER Networker Save and Restore Database Module for
Oracle, V1.0
64.66.00: NetWorker Save and Restore Application Interface for SAP/R3,
Versi ...
70.01.02: NetWorker Save and Restore Digital Client Kit, V 3.0
This kind of stuff creates nightmares for inexperienced colleagues.
..Kevin..
|
| 5293.2 | Too Slow! | 26031::16.123.96.124::Bruce_May | POWDML::May_B | Tue May 20 1997 08:23 | 1 |
| Not too usefull for me. I could take a nap in between response time..
|
| 5293.3 | Not there yet :-( | TRUCKS::PARMAR | I'm so fast - I'm even fast asleep | Tue May 20 1997 08:46 | 6 |
| When was this list last updated? There are a few product managers in there who
were given their TFSO six to eight months ago. The person who has taken over
their products is not listed at all.
This could be a useful tool if the data base it searched was more accurate and
the response time was quicker.
|
| 5293.4 | I hear where you are coming from... | MKTCRV::MANNERINGS | | Tue May 20 1997 09:25 | 6 |
| >There are a few product managers in there who were given their TFSO six
>to eight months ago
Um, was .0 trying to tell us something in a subtle kind of way ??
..Kevin..
|
| 5293.5 | | ENGPTR::MCMAHON | | Tue May 20 1997 12:43 | 31 |
| Okay, a reply to the replies.
If the data is wrong, it's because the data in OML and APPIX is wrong.
These are the official, corporate repositories for this information.
They send out nightly updates which we apply, so if you know something
is wrong, let the OML and APPIX people know so they can fix it.
Anent the response time - if you do a search against the description
field of over 800,000 rows, it's gonna take a little time. We keep
tuning the database (SQL Server on an NT 4.0 machine) to get what we
can out of the technology we're all supposed to be moving to. I guess
you have to balance it against how long it would take you to find this
information elsewhere - if you can. One of the replies mentioned
comparing the results from the web query against a file that used to
exist - repeat, used to exist. Is this the absolute best possible way
to make this information available - probably not but we have
constraints within which we must work as laid out by our primary
customer.
If this tool is useful to you in any way, then consider it a bonus and
we will be happy that we made it a little easier to get our work done
amidst the morass of incomplete, incorrect and disappearing information
sources. If you don't like the tool and have a suggestion on how it can
be improved, drop me a line - we're always looking for a better way to
do things. If you don't like the tool, the response time, the logo in
the corner, etc. and just want to complain, then don't use the tool
anymore and remove just that extra little bit of stress from your life.
We're not trying to make things more difficult, we're trying to make
them easier.
Sincerely hoping this can make a positive difference.
|
| 5293.6 | | SSGV02::carney.zko.dec.com::GRANT | [email protected] | Tue May 20 1997 13:04 | 1 |
| Re last ... bravo, Patrick.
|
| 5293.7 | kudo | CSC32::MEREOS | | Tue May 20 1997 13:12 | 19 |
|
Thank you for making this information available.
I think too often we lose sight of the fact that new information
has been provided and focus on what is wrong with the information,
web site response time, someone's name is missing and so on.
As a telecommuter, I appreciate the fact that there *is* a web site;
and if I run across a product manager that has left, well at least I know
who it was "at one time" with is more than I knew before the
web site existed!!
So thanks again for your efforts!
Sandra Mereos
Colorado Customer Support Center
[email protected]
|
| 5293.8 | | a-61.tunnel.crl.dec.com::needle | Money talks. Mine says "Good-Bye!" | Tue May 20 1997 14:39 | 10 |
| I'd urge caution using this information. Every single product that I looked
up was incorrect. I looked up all product managers in my facility and not a
single current one was listed, although some who had left the company up
to 18 months ago were still listed. One guy who had left 12 months ago
is still listed with 263 products.
Anyone know who is responsible for the databases that feed this system?
The tool is great, but the data is poor.
j.
|
| 5293.9 | NetWorker is probably not a good test... | DECWET::montlake.zso.dec.com::lenox | this note posted from NetNotes | Tue May 20 1997 14:44 | 8 |
|
At least one of the NetWorker PMs is still a contractor,
so I don't think she would be listed in official company
lists of PMs. Another person doing some PM type work
is not officially a PM, so they wouldn't be there either.
Probably very few groups have a contractor as a major
PM since access to corporate systems PMs use is next to
impossible.
|
| 5293.10 | re .8 - they could be somewhere else | DECWET::montlake.zso.dec.com::lenox | this note posted from NetNotes | Tue May 20 1997 14:53 | 4 |
|
PMs might be at the wrong facility, I did
note that one of our PMs is listed at ABO
instead of ZSO.
|
| 5293.11 | | DECWET::ONO | Software doesn't break-it comes broken | Tue May 20 1997 18:02 | 8 |
| This kind of information is invaluable for field people. I
remember using the old VTX PMLOC application to do just this.
OML and APPIX are systems that are unknown to me. Who should be
contacted to fix this information, at least for NetWorker?
Wes Ono
NetWorker Engineering
|
| 5293.12 | Who does it? | TEAMLK::CAMPKIN | Bitter is sweet | Wed May 21 1997 09:07 | 8 |
| As a Product Mgt Mgr I certainly don't do anything to update these databases
with the names of our PMs and the products they are responsible for. Who
does? Also with the introduction of PRIME in the very near future, we
have gone through a very large exercise to update some database (origin
unknown - ask the Complexity Reduction Program which one it is - Wayne
Dupont @PKO) with the names of all our products and the relevant PM.
Gerry
|
| 5293.13 | Looks pretty good to me | IOSG::HOLTD | Dave Holt | Wed May 21 1997 09:22 | 6 |
| I checked my products out on this and parts I've only just submitted to the
Price File for publication June 2nd are already showing against my name which
suggests a link with DSPS at least.
Cheers,
Dave
|
| 5293.14 | Good now, getting better | 30168::PMC | | Wed May 21 1997 13:10 | 15 |
| RE: Last few.. [Pat -- correct any egregious errors]
The data is from the Option Module List (OML), maintained by the Chief
Engineer's Office. The SBU has a large ongoing data cleanup campaign,
including part number ownership, under the Complexity Reduction
Program. Non-SBU parts on OML may or may not enjoy the same rigor.
Ownership changes from one hardware PM to another are accomplished in
PRIME, which automatically notifies the Chief Engineer's Office (today
using mail, later by automatic update) to keep the data current. Software
PM data cleanup is just now underway and they will begin using PRIME in
a few months.
So this tool is pretty good now, it does searches VTX PMLOC never
contemplated and its usefulness will continue to improve.
|
| 5293.15 | | BBPBV1::WALLACE | john wallace @ bbp. +44 860 675093 | Wed May 21 1997 13:32 | 11 |
| Ahhhhh.
Is this then fed from the same data that VTX CEO uses ?
If you know a part number, you can find a PM within a few keystrokes
and without a big database search, using VTX CEO.
You have to "register". Registration is trivial.
regards
john
|
| 5293.16 | DECevent pm? | MKTCRV::MANNERINGS | | Fri May 23 1997 06:35 | 12 |
| There are a few product managers in there who
[seem to have left the company]. The person who has taken
over their products is not listed at all.
hmm. I don't suppose Grant Currier, the pm for DECevent is one of those
is he ? If so, does anyone know who the pm for DECevent is ?
I have a partner on the line who wants to sell our products...
He would like me to call him back in an hour. It would be nice to be
able to tell him honestly that I have left a message with the pm.
..Kevin..
|
| 5293.17 | | MSBCS::BROCK | | Fri May 23 1997 08:02 | 14 |
| To the past series....
It is the responsibility of the product manager to ensure that the
official systems which track product ownership - today these are found
in the Chief Engineer's office - are up to date and current. These
systems may be updated wither via Prime, via the CRP program, or via
direct contact with the CEO. Far too much depends on the accuracy of
this information for it not to be correct.
The biggest problem seems to be products for which the PM has departed
and no clear product ownfership transfer has taken place. I would argue
that these are the responsibility of the PM's manager, and product
ownership will default up the management chain until a new PM is
appointed.
|
| 5293.18 | | 26031::msodhcp-124-216-118.mso.dec.com::Bruce_May | POWDML::May_B | Fri May 23 1997 09:30 | 4 |
| I take back everything I said in .2 - Today the response time is great and the
format is user friendly. Thanks for the input
Bruce May
|
| 5293.19 | DECevent PM | BBRDGE::LOVELL | � l'eau; c'est l'heure | Fri May 23 1997 09:57 | 11 |
| and for the person who wanted info on DECevent, try the following ;
Common Name: DAN WATT
Search Surname: WATT, Dan Watt, Dan Search Given Name: DAN,
ROBERT,
ROBERT D, Dan DTN: 592-4518, 592-4518 Intrnl Mail Addr: CXO3
Location: CXO Node: TINCUP Username: WATT Org Unit: MCS HQ/GSO,
MCS AVAILABILITY SERVICES Position: SOFTWARE PRODUCT MANAGER
|
| 5293.20 | Updates | TEAMLK::CAMPKIN | Bitter is sweet | Fri May 23 1997 10:16 | 15 |
| >> It is the responsibility of the product manager to ensure that the
>> official systems which track product ownership - today these are found
>> in the Chief Engineer's office - are up to date and current.
Whilst I accept that Prod Mgt should have responsibility to keep
databases of PMs and products up-to-date, that is impossible if they don't
know what databases and who owns. As I said we have done a major exercise
to change the data that PRIME will input when we go live, and that data will
be updated from then on. Updating numerous legacy systems will not happen. It
is the responsibility of the database owners to advise Prod Mgt if there is
information that requires monitoring, and to advise how updates should be
submitted. Hopefully they will draw their info from PRIME and the
problem will go away!
Gerry
|