Management System - Nonconformityby Savoir-faire Linux https://github.com/OCA/management-system , Odoo Community Association (OCA) https://github.com/OCA/management-system
• Document Management - Wiki - Procedures (47 lines of code)
• Management System - Action (667 lines of code)
• Document Management - Wiki - Work Instructions (46 lines of code)
• Document Page (744 lines of code)
• Management System (424 lines of code)
• Knowledge Management System (187 lines of code)
|Lines of code||3027|
|Also available in version||v 9.0 v 13.0 v 7.0 v 12.0 v 10.0 v 8.0|
Management System - Nonconformity
This module enables you to manage the nonconformities of your management systems:
- Quality (ISO 9001)
- Environment (ISO 14001)
- Information Security (ISO 27001)
- Health and Safety (ISO 45001)
- IT Services (ISO 20000)
- Other custom management system
Table of contents
To use this module:
- Go to Management System > Nonconformities
- Click on Create to enter the following information:
- Partner : Customer, supplier or internal personnel
- Related to: Any reference pointing to the NC (order id, project id, task id, etc.)
- Responsible: Person responsible for the NC
- Manager : Person managing the department or owner of the procedure
- Filled in by: Originator of NC report
- Origins: The source of the NC, how was it discover
- Procedures: Against which procedure is the NC
- Description: Evidence, reference to the standards
- Click on Save button and then on “Analysis” on stage sequence in the top right corner.
Go to the newly created NC and fill in the following information in the tab named Causes and Analysis:
- Causes: Add root causes
- Analysis: Describe the results of the investigation
- Severity: Select the severity among unfounded, minor and major
- Immediate action: Create or select an immediate action if appropriate
Click on the Save button and then on “Action Plan” on stage sequence in the top right corner.
In the Actions tab, select or create new actions by entering the following items:
- Subject: What must be done - Return to Supplier, Use As Is, Scrap, Rework, Re-grade, Repair
- Deadline: Date by which the action must be completed
- Responsible: Person in charge for implementing the action
- Type: Immediate, corrective or preventive actions or improvement opportunity
- Description: Details of the action
When the action is created, a notification is sent to the person responsible for the action.
Enter comments into the input field below the “Plan Review” section, those comments are required to reach the next stage.
To begin the work on the planned Actions change the stage of the NC to open by clicking on “In Progress” on stage sequence in the top right corner.
When all actions of the plan are done, their effectiveness must be evaluated before closing the NC clicking on the “Closed” on stage sequence in the top right corner
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- Daniel Reis <email@example.com>
- Glen Dromgoole <firstname.lastname@example.org>
- Loic Lacroix <email@example.com>
- Sandy Carter <firstname.lastname@example.org>
- Gervais Naoussi <email@example.com>
- Eugen Don <firstname.lastname@example.org>
- Jose Maria Alzaga <email@example.com>
- Jaime Arroyo <firstname.lastname@example.org>
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/management-system project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.