Hey..the customer is always RIGHT !!
> From ipc.ipc.org!DesignerCouncil-request Tue Oct 1 14:28:48 1996
> Resent-Date: Tue, 1 Oct 1996 13:05:56 -0700
> Resent-Sender: [log in to unmask]
> Old-Return-Path: <[log in to unmask]>
> From: [log in to unmask]
> Mime-Version: 1.0
> Date: Tue, 1 Oct 1996 08:37:27 -0700
> Subject: Re[2]: Differences in net lists
> To: [log in to unmask]
> Content-Transfer-Encoding: 7bit
> Content-Description: cc:Mail note part
> Resent-Message-Id: <"cY7t22.0.yeD.RVJKo"@ipc>
> Resent-From: [log in to unmask]
> X-Mailing-List: <[log in to unmask]> archive/latest/2123
> X-Loop: [log in to unmask]
> Resent-Sender: [log in to unmask]
>
> I agree!
>
>
> ______________________________ Reply Separator _________________________________
> Subject: Re: Differences in net lists
> Author: [log in to unmask] at _INTERNET
> Date: 9/30/96 5:40 PM
>
>
> You bring up a problem that is as old as schematic capture itself.
> What would help is if the schematic s/w vendors would add a feature
> that once a random name was assigned, it became permanent.
>
> > From [log in to unmask] Mon Sep 30 17:36:39 1996
> > Resent-Date: Mon, 30 Sep 1996 19:25:42 -0700
> > Resent-Sender: [log in to unmask]
> > Old-Return-Path: <[log in to unmask]>
> > X-Sender: [log in to unmask]
> > X-Mailer: Windows Eudora Light Version 1.5.2
> > Mime-Version: 1.0
> > Content-Type> : > text/plain> ; > charset="us-ascii">
> > Date: Mon, 30 Sep 1996 16:05:03 -0400
> > To: [log in to unmask]
> > From: Doug Brooks <[log in to unmask]>
> > Subject: Differences in net lists
> > Resent-Message-Id: <"T5zPw2.0.nrG.Vz4Ko"@ipc>
> > Resent-From: [log in to unmask]
> > X-Mailing-List: <[log in to unmask]> archive/latest/2120
> > X-Loop: [log in to unmask]
> > Resent-Sender: [log in to unmask]
> > Content-Length: 2000
> >
> > We are an independent Service Bureau
> >
> > A year ago we completed a board for a customer. The board had
> > roughly 7200 individual nodes. Recently the customer asked
> > us to incorporate revisions affecting approx 500 of those nodes
> > (some parts deleted, several new parts + other changes.)
> >
> > Revisions are, of course, dynamic, so we received approx 4 up-dated
> > net lists during the process. The problem is that he had numerous
> > unnamed nets. The schematic capture system would assign random names
> > to those nets each revision. Our system doesn't care if names change
> > as long as the integrity of the overall net list is preserved.
> >
> > When we gave him the check plots he asked us for a printout of
> > just the changes, presumably so he could check just those. Since
> > most of the nets were renamed several times,
> > we didn't see how we could meet his request, but he insists that we
> > should be able to.
> >
> > So I'm looking for your input.
> >
> > 1. Isn't it the engineer's job to keep track of changes if he wants an
> > audit trail?
> >
> > 2. And isn't our job to implement them and create a design that matches
> > the netlist that he says is the final and correct one, but not to maintain
> > his audit trail of changes? (in particular, a "net-diff" list from two
> > net lists with randomly assigned net names?)
> >
> > 3. If a schematic capture system assigns names to the nets, isn't there
> > a way to fix those assignments and make them permanent?
> >
> > I'm not looking for sides, here, but a way to see this problem coming
> > and be able to solve it next time.
> >
> > Thanks for any input
> >
> > Doug Brooks
> >
> >
> >
> > ****************************************************************************
> > * The mail list is provided as a service by IPC using SmartList v3.05 *
> > ****************************************************************************
> > * To unsubscribe from this list at any time, send a message to: *
> > * [log in to unmask] with <subject: unsubscribe> and no text. *
> > ****************************************************************************
> >
> >
>
> ****************************************************************************
> * The mail list is provided as a service by IPC using SmartList v3.05 *
> ****************************************************************************
> * To unsubscribe from this list at any time, send a message to: *
> * [log in to unmask] with <subject: unsubscribe> and no text. *
> ****************************************************************************
>
> ****************************************************************************
> * The mail list is provided as a service by IPC using SmartList v3.05 *
> ****************************************************************************
> * To unsubscribe from this list at any time, send a message to: *
> * [log in to unmask] with <subject: unsubscribe> and no text. *
> ****************************************************************************
>
>
****************************************************************************
* The mail list is provided as a service by IPC using SmartList v3.05 *
****************************************************************************
* To unsubscribe from this list at any time, send a message to: *
* [log in to unmask] with <subject: unsubscribe> and no text. *
****************************************************************************
|
