| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 711.1 | | KONING::KONING | Paul Koning, A-13683 | Thu Sep 17 1992 12:03 | 10 |
| The lights are the way they are so that each of the 5 or so important port
states of each ports has a distinct representation. This way you can look
at the thing and tell what is going on. If we did less, the lights would
not be nearly as useful. The assumption is that most people prefer to have
more useful information even if the result is somewhat "flashy" :-)
If the lights offend you, don't look at them. You can get the same
information via remote management.
paul
|
| 711.2 | Now they want MTBR too! | CTOAVX::BEAULIEU | | Thu Sep 17 1992 12:59 | 28 |
|
Paul,
> If we did less, the lights would not be nearly as useful. The assumption
> is that most people prefer to have more useful information even if the
> result is somewhat "flashy" :-)
Bingo...
Bad assumption. I don't care about the lights, but my customer does.
If the lights offend the customer, the person who is buying the
equipment, what do you think the customer will do if there is an equal
product out there that doesn't offend him???? I'm not trying to knock
anyone or anything, just relaying some information on customer input.
What the customer really doesn't like is the blinking red in standby.
Red means something is wrong... period. (this is the assumption most
people make) He kiddingly said that he would fix our wagon, and held up a
bunch of green paste on stickers.
Now I am not saying my customer is indictative of most customers, but
maybe on this one they have a point.
Anyways, what's the 45 second red-green light mean? Also, my customer
would like the MTBR #'s. Do we give these numbers out?
Thanks, Mike Beaulieu
|
| 711.3 | LEDs do sell boxes | BAGELS::LEVY | | Thu Sep 17 1992 13:46 | 26 |
| >Bad assumption. I don't care about the lights, but my customer does.
>If the lights offend the customer, the person who is buying the
>equipment, what do you think the customer will do if there is an equal
>product out there that doesn't offend him???? I'm not trying to knock
>anyone or anything, just relaying some information on customer input.
Experience (read market share) has shown that there are more customers
who like lots of LEDs than those who like very few LEDs. I think your
customer is in the minority.
>What the customer really doesn't like is the blinking red in standby.
>Red means something is wrong... period. (this is the assumption most
>people make) He kiddingly said that he would fix our wagon, and held up a
>bunch of green paste on stickers.
He's right. Blinking red means illegal connection, which A-M isn't.
This is a known bug in the DEFCN firmware. Look for a fix in 3.2.
>Anyways, what's the 45 second red-green light mean? Also, my customer
>would like the MTBR #'s. Do we give these numbers out?
Red-green is the correct indication for standby state. This is
documented in the manuals.
MTBF/MTTI/MTTR numbers are proprietary. They can only be distributed
under the umbrella of an NDA.
|
| 711.4 | by the time it breaks.... | CGOS01::DMARLOWE | PDP 11: MOV -(PC),-(PC) | Fri Sep 18 1992 12:25 | 12 |
| The fan assembly is listed as the component with the shortest expected
lifetime. And just how long does a fan run before failing???? 8^)
The fan manfacturer puts numbers on their products and this one
is listed at 72,000 hours (8 years). The MTBF is a best guess assuming
the parts or components are made properly.
We had to supply those numbers to a customer under a nondisclosure
and with numbers like the DB5xx/6xx series have, redundancy doesn't
seem so important and if its THAT important then you are into the dual
homing catagory
dmm
|
| 711.5 | | KONING::KONING | Paul Koning, A-13683 | Fri Sep 18 1992 15:05 | 4 |
| Note also that the concentrator will operate with only one of its two fans
running. (In other words, there is in effect redundant cooling.)
paul
|
| 711.6 | some have broken already... | BAGELS::LEVY | | Fri Sep 18 1992 19:23 | 5 |
| re: .4
Remember that MTBF is an _average_ value. Some will fail sooner; some
later. Digital Services' consumption of FDDI FRUs has been non-zero,
including fans.
|
| 711.7 | Procedure for getting MTBF/MTTR | PRIMES::BLASINGAME | Craig @PHH,ADEG,DTN-328-3038 | Wed Oct 07 1992 09:53 | 103 |
| New procedures for getting MTBF/MTTR information in the field, see
below.
I N T E R O F F I C E M E M O R A N D U M
Date: 22-Sep-1992 10:21am EDT
From: Aims Coney @MRO
CONEY.AIMS AT A1 AT USCTR1 AT MRO
Dept: US PRODUCT OPERATIONS
Tel No: DTN: 297-6541
TO: See Below
Subject: I:SIMPLIFIED MTBF/MTTR PROCESS
Effective imediately, the process for obtaining product reliability data
(MTBF and MTTR) has been streamlined.
Previously, requests for MTBF/MTTR on announced products were entered as
PID requests. Now, MTBF has been removed from the PID system and will be
handled instead by an automatic system which uses electronic mail.
I expect that response times will improve from days to hours. In addition,
the system will operate 24 hours a day, seven days a week.
NEW MTBF/MTTR PROCEDURE
1) The requester (Account Rep, Project Rep, Tech Support, etc.) mails a request
for MTBF/MTTR data to MTBF @OGO or CSSE::MTBF using the attached form memo.
2) The automated system returns the reliability data by electronic mail
together with the required disclaimer.
That's all there is to it. Send a memo and get a reply.
*** IMPORTANT NOTE FOR FEDERAL GOVERNMENT FROM THE ADEG PROGRAM ENGINEERING
GROUP- If the MTBF/MTTR data is being provided as: (1) a condition of
response to a US Government solicitation (i.e. RFP) or as information to a
company developing an offer into one, or (2) a response to an already
binding/contractual commitment, or (3) data which will be used by either
the US Government or its agents as a criteria in a competitive procurement
process, contact Mike D'Aquila (MIKE DAQUILA @MKO, STEREO::DAQUILA, or DTN
264-4327) for assistance.
See Sales Policy 1.4.2, MTBF/MTTR Data Release Approval for the full story.
MTBF/MTTR Request Form
----------------------
Fill in the information below, and send this memo to either MTBF @OGO or
CSSE::MTBF. The information, along with the required disclaimer, will be sent
to you at the ALL-IN-1 address or VMS address you specify below.
****************************************************************************
*** IMPORTANT - AN AUTOMATED SYSTEM WILL PROCESS AND REPLY TO YOUR ***
*** REQUEST. PLEASE DO NO DEVIATE FROM THIS FORMAT. ***
****************************************************************************
If you have any questions, please write or call the ADEG Program Engineering
Group at GSGPROGENG @MKO, or DTN 264-4727.
YOUR NAME:
YOUR ALL-IN-1 ADDRESS:
(Example: JOHN JONES @OGO)
or
YOUR VMS ADDRESS:
(Example: CSSE::JONES)
YOUR COST CENTER:
YOUR BADGE NUMBER:
CUSTOMER NAME:
CUSTOMER LOCATION:
BUSINESS REASON FOR RELEASING THIS INFORMATION:
Using one line per part number, list the part numbers for which you need
reliability (MTBF/MTTR) data below between the words "BEGIN" and "END". Please
use the 2-5-2 part number format (00-TK50 -AA), or you WILL NOT receive the
information that you requested.
DO NOT REMOVE THE WORDS "BEGIN" AND "END".
BEGIN
END
|