Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 140
    • Merge requests 140
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !2046

Merged
Created Jan 16, 2025 by Xiaowu Zhang@xiaowu.zhangDeveloper

Manufacturing Execution Quality control

  • Overview 5
  • Commits 6
  • Pipelines 30
  • Changes 497+

Context

When do a Manufacturing execution of a product, sometimes, it should pass a list of control before delivering

if needed, we need also record the information of products used for this product

Propose

In This MR, we mainly add a Quality Assurance Module, which mainly contains: Quality Control, Gate, Traceability, SMON, ACOM

Workflow

The Quality Element has a Quality Assurance Workflow workflow described as blow

Draft -> Creation State

Queued -> Document is planned, wait to show to the user

Expected -> Document is shown to the user for it to be completed

Pending Update -> A version of this document has been posted that doesn't satisfy Quality Assurance. A New version is needed. (useful for Quality Operation that needs to be redone). Document is shown to the user for it to be completed.

Posted -> Document has been completed by the user.

Archived -> A new version of the document has been posted, the old one become archived

it has also a Quality Assurance Interaction Workflow which is used to show next /archive previous quality element

Quality Element

Quality Control: Present a quality control, such as validate document

Gate: when a gate is posted, the quality element which's int index is greater than this one and smaller than next gate will change to Expected state

Traceability: used to record the informations of products used

SMON: it's like a Gate, when validate, the product is off of fabrication line

ACOM: all controls are finished, manufacturing execution is finished

Edited Feb 05, 2025 by Xiaowu Zhang
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: feature
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7