Specifications for OSS Items
Specifications (also referred to as a spec) help define the acceptable range of values within which an item under inspection will pass the test. Office Smart Solutions (OSS) will need to define a separate spec for each item. Their business process so demands. However, depending on the business need one spec can be applied to more than one item.
Here, Dave creates a Spec for the Linear Hub defined as item number LH101. If specs are item-specific then it is a good practice to carry the item code or number in the Specification Name.
Specs are of three types:Item SpecSupplier SpecCustomer Spec
Here, Dave creates an Item Spec for LH101.
However, as the name suggests, a Supplier Spec defines acceptable range of values for collection elements relating to an item coming from a specific supplier. If Dave were to define a Supplier Spec for LH101, then he would have had to enter the Supplier code in the screen below.
Similarly, a Customer Spec defines acceptable range of values for collection elements relating to an item going to a specific customer. If Dave were to define a Customer Spec for LH101, then he would have had to enter the Customer code in the screen below.
So, what's Acceptable?
Dave defines the values given to him by Becky. For the Linear Hub LH101, the acceptable range or the Spec Limits are as follows.
Dave saves his work. The Spec is created in Draft status. In that status, a spec will not be available for use with a collection plan.
The spec can be routed through the e-signature approval process. However, if the e-signature setup is non-existent then the spec status changes to No Approval Required.
The spec is now available for use.
Next: A Purchasing Collection Plan for Office Smart Solutions
Previous: Collection Elements in Oracle Quality
Return to Oracle Quality from Specifications