This release is a pre-release and may not be stable for production use.
Mgmtsystem Nonconformities
This module enables you to manage the nonconformities of your management system: quality (ISO9001), environment (ISO14001) or security (ISO27001).
Configuration
Users must be added to the appropriate groups within openERP as follows:
Creators: Settings > Users > Groups > Management System / User
Responsible Persons: Settings > Users > Groups > Management System / Approving User
Usage
As a user, go to Management System > Nonconformities and 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
Filled in by: Originator of NC report
Origins: The source of the NC
Procedures: Against which procedure is the NC
Description: Evidence, reference to standards
Click on Save and then on Send for Analysis.
As an approving user, go to the newly created NC and fill in the following informationi in the tab named Causes and Analysis:
Causes: Add root causes
Analysis: Describe the result of the investigation
Severity: Select the severity among unfounded, minor and major
Immediate action: Create or select an immediate action if appropriate
Click on Approve and then on Send for Review.
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.
When the action plan is reviewed (comments) and approved, each action of the plan is opened.
When all actions of the plan are done, their effectiveness must be evaluated before closingi the NC.
Known issues / Roadmap
Bug Tracker
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.
Credits
Images
Odoo Community Association: Icon.
Contributors
Daniel Reis <dreis.pt@hotmail.com>
Glen Dromgoole <gdromgoole@tier1engineering.com>
Loic Lacroix <loic.lacroix@savoirfairelinux.com>
Sandy Carter <sandy.carter@savoirfairelinux.com>
Olivier de WITTE <olivier.dewitte@gmail.com>
Maintainer
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.
To contribute to this module, please visit https://odoo-community.org.
Metadata
Release files for odoo8-addon-mgmtsystem-nonconformity 8.0.1.2.0.99.dev16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo8_addon_mgmtsystem_nonconformity-8.0.1.2.0.99.dev16-py2-none-any.whl | Python 2 | none | any | Details for odoo8_addon_mgmtsystem_nonconformity-8.0.1.2.0.99.dev16-py2-none-any.whl |
Release files / odoo8_addon_mgmtsystem_nonconformity-8.0.1.2.0.99.dev16-py2-none-any.whl
| Download URL | odoo8_addon_mgmtsystem_nonconformity-8.0.1.2.0.99.dev16-py2-none-any.whl |
|---|---|
| Size | 96.2 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
bdc12320ba2dd21efc011bf4266afa31d3e76411c9d7db84662a510ba3d2f5dd
|
|
BLAKE2b-256 checksum How to use checksums |
0195d3da72fae80d6258342d283c086d2cc3a4455646378e74b769b2f29b0ff4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo8-addon-mgmtsystem-nonconformity 8.0.1.2.0.99.dev16
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.