Skip to main content


Improving Quality Management with Oracle Cloud Quality – Part 2

Welcome back!

In Improving Quality Management With Oracle Cloud Quality – Part 1,  we covered how Oracle Cloud quality is changing the game of managing quality data.

Specifically three pain points!

  1. Reducing the need for tribal knowledge by requiring data collection at specific points in the supply chain
  2. Not having the right resources notified of a non-conformance by leveraging automatic notifications
  3. Trying to report from various systems and files to reporting from a central data point

All big wins…right?

Today we are going to look at the structure and FLEXIBILITY of collecting quality data.

Imagine that we are going to manufacture batteries… and before they leave the plant we must know two things…

  1. Are the warning labels attached properly
  2. Are the voltage outputs within a specific range

We are going to assume you have an item setup for the battery, let’s call it BATTERY123

Now, there are three critical elements we are going to define.

1. Collection Characteristics

Oracle - Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the Cloud
Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the Cloud

Explore key considerations, integrating the cloud with legacy applications and challenges of current cloud implementations.

Get the Guide

Collection Characteristics are the specific points of data you want to collect.

We will define two of them for our example:

  • Warning Label Attached 
  • Voltage Output

We will dive a bit deeper into the details of Collection Characteristics in Part – 3 (in development!)

2. Collection Plans

Think of the Collection Plan as the place we store all of Collection Characteristics for a specific product.

Let’s call it….BATTERY123_QA

As you can see below we have a Collection Plan with characteristics on it.

3. The Inspection Point

At what point in the supply chain do you want this data collected?

The competition of manufacturing makes sense for our example.

That way it never makes it into a box OR out the door if it doesn’t meet the standards!

Tying it all together

In summary, we have built a Collection Plan, with multiple Collection Characteristics, that is required to be acted upon once the manufacturing process is complete! All stored and required by Oracle Cloud Quality!

That is a pretty big improvement from the old file folder that only a few long term employees know about and remember to use!

Next time we are going to take a look at the flexibility of Collection Characteristics and how they can work for any business, including your’s.

To learn about other way Oracle Cloud can help your business make sure to grab your free guide below!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Follow Us