Browse Prior Art Database

Module Design Change Zero Defect Verification System

IP.com Disclosure Number: IPCOM000109615D
Original Publication Date: 1992-Sep-01
Included in the Prior Art Database: 2005-Mar-24
Document File: 3 page(s) / 162K

Publishing Venue

IBM

Related People

Basile, JE: AUTHOR [+6]

Abstract

In a manufacturing process of a product which as a computer representation of the end product (i.e. a computer design data base) and which uses tools whose control is a set of electronic instructions, add the process step which transforms the tool instructions (numerical control or NC data) and the representation of the design to a common format and compare the two to insure that they are the same.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Module Design Change Zero Defect Verification System

       In a manufacturing process of a product which as a
computer representation of the end product (i.e. a computer design
data base) and which uses tools whose control is a set of electronic
instructions, add the process step which transforms the tool
instructions (numerical control or NC data) and the representation of
the design to a common format and compare the two to insure that they
are the same.

      The Module Design Change Zero Defect Verification System
prevents the manufacture of module hardware with injected errors from
physical design and manufacturing processes.  Module design changes
originate due to functional enhancements, correction of logic errors,
commodity mix, or manufacturing defects.  All design changes are
subject to the potential of injected errors, due to software and/or
human errors.

      No existing software or manual verification processes or
methodologies were able to detect these injected errors prior to
module hardware build, regardless of their source. The only method of
finding these errors was to trace module hardware failures in a
functioning processor.

      The solution was to develop a process and algorithms to
validate the NC (numerical control) data.  NC data feeds the
manufacturing robots that actually apply the ECs (engineering
changes) to the data base of existing printed wires and top surface
wires.  This NC data is compared with the earliest level of system
logical design data describing connection requirements.  The
comparison is performed in software, prior to module hardware build,
to ensure that no errors have been injected during any stage of
module design.  The process for design and EC is described in the
flowchart in Figure 1.

      This is a complete process addressing all logical requirements,
all printed connections, all top surface EC wires, and all NC data.
This ensures that no requirements are omitted and that no existing
connections are extraneous.

      The basic process is described in Figure 2 and involves a
manufacturing NC data file being sent to a processing account wher...