| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 667.1 | Case History Description | CIMNET::BOURDEAU | Rich Bourdeau CIM Product Marketing | Thu Jun 14 1990 22:21 | 68 |
| Case Histories
==============
What are they ?
---------------
Case Histories are short case studies of actual customer
implementations. The focus of a case history is the business
problem, the solution, and the benefits derived. They are
designed to show how Digital tools and third party applications
can be used to solve customer problems by showing actual
examples. The intention of these case histories is to be short,
to the point, and stimulate interest to learn more about
Digital's manufacturing solutions.
What is the objective ?
-----------------------
One of the problems that most consumers have is visualizing how
a product can be used to meet their needs. One of the problems
with promoting the technical capabilities of our products is
that our customers are often overwhelmed by the possibilities
that they could use them for. If they don't understand the
possibilities, they are less likely to purchase our products.
To be more effective in helping our customers understand how our
products can actually be used you need to speak their language.
In Manufacturing the language is either industry focused:
process (Pharmaceutical, Food, Oil and Gas, etc.) and discrete
(Automotive, Aerospace, Semiconductor, etc.) or applications
focused (MRP, Shop Floor, Quality, Process Control, etc.). By
documenting solutions to business problems in different
industries and different application areas, case histories show
how Digital solutions can be used to solve actual customer
problems in a language the customer understands.
Which customers ?
Any Digital customer or Internal user who is using Digital
products to solve a business problem. The Case History will not
include the company name, only a business description (ie.
Automotive supplies manufacturer, plastics manufacturer,
etc...).
Where can they be used ?
There are many possibilities where these case histories could be
used the following is a list of potential usages:
� VTX
� Sales Tool
� Sales and Sales Support training
� Case Histories Reference Guide
� White papers and presentations (ie.. ISA and Autofact)
� Press and Consultants
What is the format ?
Attached you will find a template with some sample questions.
The template is standard and should not be changed. The
information collected from the questions could most likely fill
many pages. The purpose of the Case History format is to
consolidate the information and present it a concise format .
|
| 667.2 | case_hist_template | CIMNET::BOURDEAU | Rich Bourdeau CIM Product Marketing | Thu Jun 14 1990 22:23 | 93 |
|
| Case History
| -----------------------------------------------------------
| TEMPLATE
|
|
|
| PROJECT : A one sentence description of the project including
| what was implemented and why. A business problem, solution
| summary.
|
| e.g. A shop floor management system designed to improve the
| quality and yields of a thin film disk manufacturing operation.
|
| e.g. The Quality Solution System implemented to improve quality
| management, traceability and process optimization of a spindle
| fabrication area.
|
|
|
| PROBLEM : A description of the business problem,
+----------------------+ including:
| |
| Business: | � Manufacturing Environment
| Company Description | eg. type of manufacturing, products built,
| | discrete, process, repetitive, make-to-order
| Industry: | make-to-stock., etc...
| Industry Description |
| | � Business Problem
| Software: | eg. improve product/process quality, reduce time
| | to market, increase yields, etc...
| List of key product | � Conditions which drove need to change
| Third party appl. | eg. government requirements, need to reduce cost,
| or Digital Prod. | replace manual system, integrate functions, etc...
+----------------------+
|
| OBJECTIVE : Specific requirements or goals of the solution,
| features needed, and/or what the company wanted to
| achieve
|
| e.g. archive historic information for serial/lot traceability
|
|
| SOLUTION: A description of how the solution solved the business
| problem and the products and applications and services
| implemented.
|
| eg. See attached examples for additional details
|
|
|
| BENEFITS: List benefits against stated goals, preferably
| quantifiable.
|
| e.g. reduced scrap and rework, increased yields by 10%, reduced
| costs by 20% - or $X annually
(OVER)
System Details : A more detailed description of the
solution,which includes capabilities of individual components,
Integration,and technical problems. No more than half a page.
A Diagram of the Solution
|
| 667.3 | Case History Example | CIMNET::BOURDEAU | Rich Bourdeau CIM Product Marketing | Thu Jun 14 1990 22:26 | 72 |
|
Case History
----------------------------------------------------------------
A Time to Market Solution
PROJECT : A shop floor management system designed to improve the
quality Increase yields and reduce time to market of a thin film
disk manufacturing site.
PROBLEM : Time-to-market and product quality were key issues for
this manufacturer of disk platters used in disk storage
products. The company needed the ability to identify problems
early on in the implementation cycle to meet their goals in
these areas. To accomplish this task, process information
needed to be accessed by different groups residing in different
locations using a variety of tools.
+-------------------+ OBJECTIVE : Implementation of a shop floor management
| | system, which addressed the following requirements:
| Business: |
| Disk Manufacturer | � Automatic capture of process data
| | � Consistent process and product quality
| Industry: | � Multi-site, multi-tool access to product process
| Electronic | data
| | � Simultaneous development of product and process
| Software: |
| |
| Rdb |
| DECwindows | SOLUTION : A custom shop floor management system was
| Messaging - PAMS | implemented to schedule and track material movement
| Teamdata | through the manufacturing process, and to monitor
| BBM's RS/1 | quality process data. Process information was used
+-------------------+ by manufacturing, quality, and product engineering to
improve the design and manufacturability of both the
product and the process.
The implementation is based upon Rdb, DECwindows, and PAMS (a
messaging system available through the Digital Assets library).
The information captured by the manufacturing process was
integrated with their production scheduling systems at the
plant. In addition, the product quality information was made
available online to other manufacturing sites in the US and
Europe that manufacture disk drives.
BENEFITS : This system allows process problems to be identified
in a timely manner, with more reliable data, thereby improving
the product quality. Online availability of product quality
information for component parts also contributed to the overall
design and manufacturability of the finished product. This
company received the CASA/SME 1989 LEAD award for the their
successful integration of multiple manufacturing functions and
sites.
(OVER)
SYSTEM DETAILS : Each work cell controller consists of a
VAXstation 3100 with an 19 inch color monitor connected via
DECnet up to eight test devices (disk media certifiers). The
Operator/Engineer interface is handled via a combination of
DECwindows and touch screen input. Data collected by the testers
is passed to the shop floor management system via the PAMS
messaging bus. Process data is then stored in a Rdb database
where it can be accessed by end users using decision support
tools like Datatrieve, Teamdata, DECdecision and BBN's RS/1.
|
| 667.4 | Case History Example | CIMNET::BOURDEAU | Rich Bourdeau CIM Product Marketing | Thu Jun 14 1990 22:29 | 81 |
| |
|
| Case History
|--------------------------------------------------------------
| A Quality Management Solution
|
| PROJECT : Improve quality management, traceability and process
| optimization of a spindle fabrication area.
|
|
| PROBLEM : The spindle fabrication area is a low-volume, high
| value added manufacturing process. Detection of manufacturing
| faults was limited to post inspection of completed parts.
| Significant cost reductions and increased productivity could be
| achieved by detecting and correcting out of spec parts earlier
| in the multi-step process.
|
| Archiving of historical quality data was also required to meet
| government serial/lot number traceability requirements.
| Historical information was also required for
| experimental design and process capability studies
+-------------------+ designed to improve the manufacturing process
| Business: |
| |
| Helicopter |
| Manufacturer |
| | OBJECTIVE : Implement a complete quality management
| Industry: | system which addressed the following needs:
| Aerospace |
| | � Monitoring of real-time process data
| Software: | � Provide operators with the capability to monitor
| Salerno SPM+ | and adjust the process
| Digital QSS | � Archive historic information for serial/lot
| Rdb/VMS | tracibility
| BBN RS/1 | � Support experimental design, process capability,
| | and process development across different
+-------------------+ functional groups.
|
| SOLUTION : Digital worked closely with Salerno Industries and
| BBN's Software Products Corp. to combine Salerno's SPM+ process
| monitoring software and BBN's RS Series of data analysis
| products with Digital's Rdb/VMS database to provide an
| integrated Quality Information System. The solution integrates
| Statistical Process Monitoring and Control (SPC) with data
| analysis software by storing historical process information in
| Digital's Rdb/VMS database.
|
|
| BENEFITS : The implementation of this system resulted in:
|
| � Reduced Scrap and Rework
| � Improved Process capability/design capabilities
| � Change in philosophy from �detective� to �preventive�
|
|
(OVER)
System Details : SPM+ is a realtime statistical process
monitoring and control application. SPM+ captures and analyzes
data on out -of -control conditions, defect types, and
corrective actions taken. It also allows for the definition of
pre-programmed actions in response to specific out-of control
conditions. SPM+ updates the quality database with a
statistical sampling of the data it captures. The information
is stored in the Rdb/VMS quality database where it can be used
by RS/1 and it's layered products. Engineers and managers now
have easy and timely access to the same production information
for process analysis, process capabilities and quality
production reports.
A Quality Solution System Implementation
(Diagram Missing)
|
| 667.5 | Case History Questions | CIMNET::BOURDEAU | Rich Bourdeau CIM Product Marketing | Thu Jun 14 1990 22:32 | 97 |
|
Case History
QUESTIONS ?
The first series of case histories will focus on applications
which use Digital's data management products. The following
questions will help provide the information necessary to create
a case history.
1.Business Description
What is manufactured at this company/division/plant?
2.Industry
What Industry does this company/division/plant fall under ?
(eg. Automotive, Aerospace, Pharmaceuticals, Paper and Pulp,
Electronics, Oil and Gas, etc...)
3.Software
The solution should use Rdb and possibly other Digital
information management products listed below:
Interoperability Tools Vida, VAXLink,
SQLservices
VAX Data Distributor
4GL Tools Rally
Decision Support DECdecision, Teamdata,
DTR
Transaction Processing VAX ACMS
Data Repository CDD/Plus
4.What type of manufacturing environment is it? (e.g.
low-volume, high-speed batch processing, etc.)
5.What was the most successful (application-focused) project at
your account -- using Rdb? (e.g. shop floor management
system)
6.Is it a standalone application or does it involve integration
of other applications or groups of users from different
organizations ?
7.How many other projects (using Rdb) are there at your
account? Briefly, what are the projects
(applications/systems)?
Let's focus only on the most successful project first....
8.What was the business problem the customer was trying to
solve? (e.g. time-to-market, reduce costs, increase yields,
etc.)
9.What conditions drove the need to change the way the company
had been doing things in this area? (e.g. growth of
business, increased competition from overseas, government
regulations, etc.)
10. What, specifically, did the company want to accomplish with
the solution?
11. What solution features/benefits were important to them?
12. What solution was implemented?
a. Application/s (3rd party, homegrown, custom)
b. Digital Products
c. Digital Services (e.g. systems integration)
13. Why was Rdb selected ?
14. What were the alternatives ?
15. Please describe the solution so that we can present it in a
very simple diagram -- i.e. describe the flow of data.
e.g. from terminals on the plant floor, data is input to a
labor tracking and reporting system through bar code wands.
That data is stored in the Rdb database and then sent over
the SNA gateway to IBM host for payroll processing.
16 What benefits did the customer realize by implementing this
solution? (quantifiable if possible -- e.g. reduced costs by
20%)
17. Would your account be interested in participating in
Digital's testimonial program (and willing)? e.g. let us do
one or more of the following: brochure, articles (PR,
Enterprise, Insight), "Digital Has It Now" ad, speak at
special events (e.g. Analyst conference), etc.?
18. Name and location of account contact(s)
|