2. 1. To improve the measurement of
components received within the company
2. Ensure that parts comply with the
specification
3. To lay a foundation for subsequent
component/supplier analysis
Objectives
3. Templates are
generated by
SolidWorks macro and
can be incorporated
into ePDM on release
of a drawing.
Process Outline
Inspection
Template
Inspection
Report
Inspection
Report
Inspection
Report
Reports are generated
from the template on
and “as and when”
basis by an inspector.
The current stock
holding is generated
for the report.
4. Principal areas:
1. Header
2. Dimensions and
tolerances
3. Measurements
and comments
4. Designed as a
continuous form with a
header on each page
5. Watermark to show the
status (lifecycle)
Inspection Template
5. Template (Header)
• Data exported from SolidWorks
includes:
• Drawing, Revision, Part number,
Status, Description & last
modification. Includes hyperlink to
drawing in ePDM!
• File Properties
• Material & manufacturing data
• Default drawing / manufacturing
tolerances
• Part attributes
• Image with hyperlink
• Purchasing/Quality
• Approvals
6. Template (Dimensions & Tolerances)
• Dimensions imported
view-by-view and show:
1. Grouped by Drawing/View
Dimension name, XY
location & layer.
2. Min, Nom & Max values.
3. Prefix & suffix.
4. Units.
• Tolerances taken from
drawing in line with the
chosen manufacturing route.
• Modified GN’s template
editor - all fields are now
controlled by a database
(“SolidWorks settings.mdb” in O: drive)
7. Template (Measurements & Comments)
• Measurements can only be
entered in to
coloured cells
• Error values are calculated
and conditionally formatted
to clearly display non-
conformity.
• Comments can be added for
any row of data.
• Errors are collated for each
batch & overall and includes
“Inspection” dimensions.
8. • Generated from ePDM via
a right-mouse click on the
selected drawing(s)
• Multiply select via query.
• All other file types other
than drawings are ignored.
• Can be generated directly
from SolidWorks via a
macro with UI
• Separate sub-directory of
the templates.
• Name of:
“Inspection Template – “ & PN; Rev
Generating a Template
9. • On entering the
template the purchasing
data is added by the
system:
1. Quantity in stock
2. Last received date
3. Quantity on order
4. Demand/month
5. Calculates priority.
• The following is required
from the user:
• Supplier & Order Number
(potentially obtained ERP system?)
Generating a Report
10. Saving a Report
• The system saves a file automatically upon
generation of the report.
• Separate sub-directory
• Name of:
• “Inspection Report – “ & PN; Rev_YYYYmmDD
(Assumes no more than 1 batch/day/part)
11. • A database has been
created to manage all
reports.
• Scheduling
• Reporting
• Supplier analysis
Database integration
Inspection
Report
Access
12. • Buttons are provided to
allow the inspector to
commence a workflow
after collating the data
• Traffic light system
• Workflow states
• “Unapproved” (Default)
• “Pending ”
• Reject, Concess or Accept
• “Accepted”
• “Rejected”
• “Concessed”
Typical workflow
Reject Concess Accept
13. Typical workflow
• On each change of state
an entry is made in the
database to record
decision
1. Sent to recipients with a link
to the file on the server.
2. File is sealed against change
3. Decision recorded in database
Access
15. Pre introduction
• Dimensioning protocol
1. A numbering system has
been introduced (catered
for) but could further
improve by:
a. Using a layering
convention to colour code
importance / frequency of
inspection?
b. Catered for by the system
(Demo)
To be discussed?
16. Post introduction
• Workflow:
1. Incorporate into ePDM?
2. Reject, Concess or
Approve?
3. Notifications?
4. Supplier analysis?
• Generate templates for
all released drawings on
ePDM?
To be discussed?