Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
0Activity
0 of .
Results for:
No results containing your search query
P. 1
03_Quality White Paper

03_Quality White Paper

Ratings: (0)|Views: 3 |Likes:
Published by Muruga Samy

More info:

Published by: Muruga Samy on Jul 30, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

07/30/2012

pdf

text

original

 
 
 A Guide to Oracle Quality 
 An Oracle White Paper 
 August, 2003
 
1
A Guide to Oracle Quality
ABSTRACT
This paper introduces the reader to the concepts of quality management in Oracle Quality andreinforces that understanding with the aid of a business case that spans across the Work InProcess (WIP) and the Purchasing modules. As we walk across the shopfloor and the receivingbay, we study the data collection process from the perspective of Oracle Quality business flow.The paper also covers the enhanced features that have been added to Oracle Quality throughFamily Packs G, H and I.
SCOPE
This paper covers the basic business flow for Oracle Quality. It also takes a close look at GlobalSpecifications (Family Pack I), Parent Child Relationships (Family Pack H) and Collection PlanSecurity (Family Pack G), to obtain a better understanding of Oracle Quality as it stands today.This paper is intended for an audience familiar with Work In Process and Purchasingtransactions and desirous of gaining an insight into how to set up a quality inspection process atstrategic junctures to ensure that products are conforming to specifications and of how to definethose specifications, standards and measurable parameters in the first place, using OracleQuality.
CONCEPTS IN ORACLE QUALITY
Oracle Quality is integrated with the Oracle Manufacturing and Distribution applications toprovide consistent quality data definition, data collection and data management across theenterprise and throughout the supply chain. Oracle Quality application can be used to gather user-defined quality data. Data collected and input into Oracle Quality may come from functionssuch as purchasing, service, shopfloor inspection or directly from the customer, to name a few.Quality data can also be collected in a totally standalone method or may be linked to third partysystems. It is possible to import data from other systems to give the users a full view of thequality process in their plants.The data collection structure in Oracle Quality comprises
!
Collection Elements
!
Specifications
!
Collection PlansThe basic building block of this structure is the collection element, which is used in both thespecification and the collection plan. Collection elements define the characteristics or the qualityparameters of the product or the process, which is being analyzed and for which we collect andreport data. Collection Plans are similar to test or inspection plans. Collection plans specifywhich are the collection elements to be used in collecting data. Collection plans specify whenand how to collect the data as well as the actions to take based on the data collected.Specifications set the quality standards to which the product or the process should conform.These standards can be in the form of absolute values or a specific range within which theresults would be acceptable. The type of collection elements being used determines the natureof the specification. Examples from the business case used in this paper would elucidate theseconcepts.
DESCRIPTION OF THE QUALITY INSPECTION SCENARIO FOR THIS PAPER
The organization manufactures steel shafts for use in different assemblies and also for sale asspares. One such product is the item SS180/15. The prefix “SS” stands for steel shaft. 180specifies the finished shaft length of 180mm and 15 specifies the finished shaft diameter of 15mm. The organization receives the raw material for SS180/15 in the form of a rough-cut job,
 
2
which is in fact a cylindrical steel shaft of length measuring approximately 200mm and diameter measuring approximately 20mm. This raw component is termed as SRCJ200/20 (“SRCJ” for steel rough cut job and 200/20 signifies length/diameter). This component undergoes the“Cutting” operation to have its length trimmed to 180mm. The result is the intermediate productSCJ180/20 (“SCJ” for steel cut job and 180/20 signifies length/diameter). This component nowundergoes the “Turning” operation to have its diameter reduced to 15mm. The result is theintermediate product STJ180/15 (“STJ” stands for steel turned job). In the final operation,STJ180/15 undergoes ”Grinding” to attain a smooth and presentable finish. The end result or thefinal assembly is SS180/15.Thus, moving down from the final assembly level, SS180/15 has STJ180/15 as its component.STJ180/15 has SCJ180/20 as its component. SCJ180/20 has SRCJ200/20 as its component(refer Fig 1). This process will be mapped into 3 separate routings of a single operation each.
The Collection Elements used in this paper 
To suit our quality inspection scenario, we have defined
five
collection elements. These are
!
SHAFT LENGTH
!
SHAFT DIAMETER
!
FAILURE CODE
!
MY ITEM
!
MY SERIALBesides these five collection elements we have also used some predefined collection elementsviz., Quantity, Inspection Result, Transaction Date and UOM Name, to name a few.
Note
: Oracle Quality provides a (seeded) reference information type collection element –
Item
.This collection element can be used in collection plans wherein data is to be collected againstitems or item codes. However, sometimes customers prefer to define and use a referenceinformation type collection element instead of the
Item
collection element. An example would bethe case of the organization that prefers the term
Device
or 
Product Code
instead of 
Item
intheir collection plan. Though this leads to the creation of redundant collection elements, sincethey all point to the same data object – the item, Oracle Quality allows users to define referenceinformation type collection elements to suit their terminology or business case. MY ITEM is acollection element defined and used in this paper, to demonstrate this very point.But, before we probe into the rationale for these collection elements, let us take a brief look atthe collection element types available in Oracle Quality. Oracle Quality provide us with threepredefined collection element types,
Attribute
,
Variable
, and
Reference Information
which areavailable in the list of values (henceforth referred to as LOV) in the field
Element Type
when wedefine the collection element.
Variable
collection element type represents numerically measurable parameters. They can andoften do, have a range of acceptable values defined as specification limits. In this paper, SHAFTLENGTH and SHAFT DIAMETER are the two
Variable
type collection elements. As the namessuggest, one measures the length of the shaft and the other measures the diameter. For SHAFTLENGTH the desired value (Target Value) is determined as 180 MM. However, the upper specification limit has been set at 182 MM and the lower specification limit has been set at 179MM. Similarly, specification limits have been determined for SHAFT DIAMETER. A collection element of type
Attribute
represents a characteristics or an attribute of an item suchas colour (possible list of values includes pink, blue, orange,…) or it represents the outcome of aprocess (possible list of values could include damaged, scrapped, to-be-reworked, use-as-is,…).Collection elements of type Attribute have only a limited list of acceptable values. In this paper,FAILURE CODE is the
Attribute
type collection element. Refer Fig 2, for the values assigned tothis collection element.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->