-->


.
T h e     Business Control System   S o l u t i o n . . .

LAMAR Software Home
About LAMAR Software, Inc.
General System Functions




.
Quality Assurance Management
Quality Assurance Management is made up of three different functions. They are:

1. The ability to define the quality parameters for every part, assembly or service you are working with. This is done via the assignment of testable attributes to inventory items or services. The testable attributes can be used in both the receiving inspection area for purchased items or on the shop floor for manufactured items.

2. Each of the testable attributes produces an objective definition of an acceptable unit. All of the results are stored in the database.

3. In addition to testable attribute results, the system also provides other feedback features useful in maintaining and tracking of product quality.


Whitepapers covering these subjects are listed at the bottom of this page.
Placing your cursor over any of the features listed below, will give you more information about the subject.

Define Inspection Specifications by ItemTo provide inspection criteria for purchased items following receipt, any number of quantitative specifications (attributes) can by created for an individual item. (These items do not have to be part numbers or inventory items). The results of these tests will be maintained in the system and may be queried or listed by item designation, by vendor or by test code.

Quality parameters and testing is also available in the production environment, where the inspection criteria are defined at the part number routing operation level. The results of this type of test will also be maintained by the system.


Reporting of Receiving Quality by ItemReports and queries are available to list the results, by part/item ID, of tests performed in receiving inspection. The reports will list all items and part numbers, or if requested a selected group of items or part numbers. The query will show the test results for specific user specified items between two dates.

Reporting of Receiving Quality by VendorReports and queries are available that will show the results of tests performed between two user specified dates on received items in receiving inspection. The report will list all vendors or, if requested, a selected group of vendors. The query will list the tests performed for a single specified vendor.

Reporting of Production Quality by ItemReports and queries are available that will list the results of tests performed on all production items, on selected production items and on specific production operations, between user specified dates.

Reporting of Production Quality by Production OperationAs each operation in a production routing has an operation class code, reports and queries are available that will list test results in production orders for the entered operation code (or in the case of reports, for all operation codes) between two user specified dates.

Reporting of Production Quality by Inspection TestAs each production test has its own unique code, reports and queries are available that list by test code, the results of all tests using the test code between two user specified dates.

An example of a test code might be a code defining a temperature test in a specific environment using specified limits, or a code defining a visual cosmetic check with a yes / no result.


Reporting of Production Quality by Production OrderBoth queries and reports are available to list the results of test performed on work orders or repetitive schedules. The quality assurance report will list all production orders if requested, but the query requires the selection of a specific order code.

Discrepant Material Locations / Control (DMR)Specific Inventory locations can be defined as discrepant material locations (This is the classic MRB type of location) – or are never available for discrepant material. If the DMR system is in use, at least one location is required that is defined as acceptable for discrepant material.

Any of the material movement programs that move units out of an inventory location can be used to move correctly authorized units out of a DMR location to another stores location if the units are being accepted ‘as is’.

They also could be moved into a non-standard job that will be used to rework the units.

The system’s ‘Return to Vendor (RTV)’ routine could be used to return the discrepant units to a vendor - or the units could be moved out to a scrap G/L account.


Discrepant Material Reporting / Approval / ReleaseINFO.NET has the ability to track rejected material with specialized documentation (termed DMRs – Discrepant Material Reports). This level of documentation permits users to record specific information concerning the entire history of the discrepant lot, including the terms and / or description of the resolution of the discrepancy. Included in the resolution can be up to six required approvals.

Following DMR resolutions, the DMR data is retained as DMR history. The DMR data will only removed through the manual data purge routine based on the user specified age of DMR resolutions (using the system’s data purge routine).


Discrepant Material (DMR) Email AlertsUsers have the ability to create proactive alerts to warn them of unresolved discrepant Material reports (DMRs). The alert will send an email message to the user listing the DMRs and the items that have been unresolved for more than the number of days specified by the user in their alert request.

Quality Attribute Data TypeEach attribute Data Type (ADT) contains a specific type of data, which can be used for a variety of tests or controls. There is no limit on the number of attributes that can be assigned to a item.

1. Numeric Integer Values Or Range. The user will be asked for a minimum value, a nominal value and a maximum value. When this type of attribute is assigned to specific items, the parameters for each item being inspected must fall within these numeric boundaries.
2. Numeric Fractional Values/Range. Functions in the same manner as “Numeric Integer Values Or Range.”
3. Cost Tracking. Upper and lower limits will not be requested for cost tracking, but this function enables you to track the specific cost of an item in inventory.
4. Alpha Values/Range. If specific alpha values were required (as would be the case of trying to track an attribute such as ‘color’), grading would be used.
5. Date Range. The user will be asked for a lower range date, a nominal date and an upper range date.
6. Predefined Grades. If specific values (either numeric or alpha) are required, grade definitions can be used for explicit values.
7. Yes / No. The Yes/No type of attribute would be of obvious use in many test situations where no numeric results are available but the determination of whether the unit(s) passed the test is available.



Whitepapers are available to further explain the capabilities of Info.Net.

Quality Assurance Module
Warranty Control
Service Requests
Discrepant Material (DMR) Control
Business Process Control
Alerts

 
© 2013 LAMAR Software, Inc.
  
info@lamarsoftware.com
 

Home | About LAMAR | Info.Net Functions | Support | Cloud Access
| More Info | Contact