Control Plan

A group of Characteristics tied to a single Item Number.

Universal Control Plan

A group of Characteristics tied to more than one item number.

Characteristic

An individual test.  Characteristics are either attribute or variable.  When a characteristic is tied to an item through a control plan, values specific to that item can be specified.  For example:  The same characteristic (Weight) could be tied to two different items (ItemA - Brick and ItemB - Feather).  Creating a control plan for ItemA - Brick allows me to add the characteristic "WEIGHT" and assign values specific to that item.  If the same characteristic "WEIGHT" is assigned to ItemB-Feather through the creation of a control plan specific to ItemB, I can have a different expected value.

Attribute Characteristic

Pass/Fail test (a.k.a.: Go/NoGo, Good/Bad, etc.) 

Variable Characteristic

Value based test.  A variable characteristic has an expected value (known as a target value).  Optionally, they can have control and specification limits.  Variable tests can be used to measure something. (machine speed, temperatures, diameters,  etc.) 

Defect Code

A code that can optionally be required to further define why an individual attribute test result (Pass/Fail test) failed. 

Skip Lot Testing

A testing methodology that monitors vendor quality and adjusts the testing frequency based on current readings.  A vendor who delivers very good quality may only be tested every 5 shipments.  A vendor who regularly delivers questionable quality items may have every one of their shipments tested.

Non-Conformance Codes

A user defined code file that can be linked to a test sample group that further defines the type of non-conformances that were observed.  Non-Conformance codes are very similar to defect codes with one major difference:  A defect code is specific to a single attribute result.  Example:  If 5 pieces out of a group of 100 failed an attribute test, each piece could be associated with one or more defect codes.  A non conformance code would be assigned at the group level

Trends

A statistically significant event. Trends can be as obvious (such as a FAIL test result on an attribute test) or much harder to see (such as 15 points alternating on each side of the target value on a variable test).  In both cases, trends indicate results that are statistically significant.  Monitoring trends can help users identify and resolve a potential problem before it results in a quality issue.

Alerts

An automatic notification by the software when a trend is identified.  Alerts can be manually defined.  Examples of alerts include lighting up a stack light, auto creation of an NCR, sending an e-mail to someone to notify them that the trend occurred etc.

Non-Conformance Report
(NCR)

Non-Conformance Report.  A document that can be created manually or automatically that alerts the users to quality issues as well as gives them a place to track such issues as cause codes, disposition/deviations, corrective actions etc.

Serial Tracking

Detailed tracking (set at the item level) that links individual results to a unique item/serial number combination.  The test results are stored in the historical database down to the individual item/serial number they were entered for.

Lot Tracking

A broader form of tracking (set at the item level) that links an individual result to a group of items from the same lot.  The test results are stored in the historical database down to the item/lot they were entered for.  (Assumes more than one item)

Electronic Signatures

An electronic signature means of "signing off" on test or group of tests.  Electronic signatures force the users to enter a valid badge number/password number prior to or after entering tests (based on setup).  This electronic signature information is stored in the historical record and is intended to provide proof of tester identity.  Passwords related to the electronic signature can be tailored in such a way as to require the users to change them on a regular basis.

Gauges

A gauge is a piece of testing equipment.  It can be generic and refer to a group of individual pieces or it can be serial tracked to a specific piece of equipment.

Gauge Tracking

If a gauge is identified at the serial level, gauge tracking can be turned on.  Gauge tracking will automatically keep track of the usage of that serialized piece of equipment. Prior to use at test entry, the gauge serial id will be prompted for and edited (checked for valid status).  The serialized ID will be stored in the results history file and the # of readings will be automatically updated in the gauge file every time that gauge is used.  This assists in gauge tracking and calibration tracking.  In addition, if a specific gauge is every found to be out of calibration, the detailed results history will enable the company in impact analysis by easily identifying the items tested with that gauge. 

Quality Bulletins

Quality bulletins are free form rich text format documents (Microsoft Word, Adobe Acrobat are rich text applications.  They allow you to insert text, pictures, videos, links in a single document)  Quality bulletins are manually "Enabled" for a specific time period.  They are intended to alert users that something has changed with regards to the Control Plan.