Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Roadmap] Extend MES Functionality #4826

Open
SchrodingersGat opened this issue May 16, 2023 · 13 comments
Open

[Roadmap] Extend MES Functionality #4826

SchrodingersGat opened this issue May 16, 2023 · 13 comments
Labels
Fund This issue can be specifically funded for development inactive Indicates lack of activity roadmap This is a roadmap feature with no immediate plans for implementation
Milestone

Comments

@SchrodingersGat
Copy link
Member

SchrodingersGat commented May 16, 2023

There are some disparate PRs in the works which tend towards more fully-featured MES functionality. Collecting them here for further discussion. I'd like to have a well-considered plan towards MES functionality:

References

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@SchrodingersGat SchrodingersGat added the roadmap This is a roadmap feature with no immediate plans for implementation label May 16, 2023
@matmair
Copy link
Member

matmair commented May 16, 2023

@SchrodingersGat With the roadmap label I can assume you support us moving into a MES direction?

@SchrodingersGat
Copy link
Member Author

Yes, I'm scope creeping! My company and a number of others I know of already use inventree for MES practices. Mostly through build orders and plugins.

Some ideas of what we could add in:

  • communication with shop floor machines
  • build process instructions/ steps which integrates with commission tests
  • improved tracking of complex build processes

Any other ideas?

Keep in mind that these additions should be "optional" for users - the current simplifie workflow should not be forced to change significantly.

@matmair
Copy link
Member

matmair commented May 16, 2023

I already have (bad) plugins for instructions and communications; Both are very much possible - a good UI for them is the real issue.

@github-actions
Copy link
Contributor

This issue seems stale. Please react to show this is still important.

@github-actions github-actions bot added the inactive Indicates lack of activity label Jul 22, 2023
@wolflu05
Copy link
Contributor

Still in work

@github-actions
Copy link
Contributor

This issue seems stale. Please react to show this is still important.

@github-actions github-actions bot added the inactive Indicates lack of activity label Sep 21, 2023
@SchrodingersGat
Copy link
Member Author

No, not stale

@github-actions github-actions bot removed the inactive Indicates lack of activity label Sep 22, 2023
Copy link
Contributor

This issue seems stale. Please react to show this is still important.

@github-actions github-actions bot added the inactive Indicates lack of activity label Nov 22, 2023
@SchrodingersGat
Copy link
Member Author

Not stale

@github-actions github-actions bot removed the inactive Indicates lack of activity label Nov 23, 2023
@SchrodingersGat SchrodingersGat added the Fund This issue can be specifically funded for development label Jan 13, 2024
@SergeoLacruz
Copy link
Contributor

Some thoughts from my side. We use Build Orders to control HWbuilds, mainly PCB assembly. I wrote something that allows to add additional data to the BO

https://github.com/SergeoLacruz/build_plugin

Using this and the report system we can create documents like request for quotation more or less automatically based on data in the system. Just an idea.
An additional thing I am thinking about: the change part request. I happens quite often that a BOM code needs to be changes in the very last minute based on engineering request or material shortage. Or the designer wants to build 20 boards but 5 with one component changed, just to try something. the function in Inventree is substitutes. But substitutes influence the BOM not the build. The BOM shall not be changed. This is advanced. :-) Actually we just write a change document and add it to the attachments. OK for now.
Finally, uploading a BOM does not allow to update. Just add or delete all. In latter case all allocations are gone. Some day soon we will write plugin for BOM import to fix this.
Michael

Copy link
Contributor

This issue seems stale. Please react to show this is still important.

@github-actions github-actions bot added the inactive Indicates lack of activity label Mar 16, 2024
@matmair
Copy link
Member

matmair commented Mar 16, 2024

This is beeing worked on in plugins. Not sure if this is still a goal for core @SchrodingersGat?

@SchrodingersGat SchrodingersGat added this to the horizon milestone Mar 16, 2024
@SchrodingersGat
Copy link
Member Author

Still need to work out the framework for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fund This issue can be specifically funded for development inactive Indicates lack of activity roadmap This is a roadmap feature with no immediate plans for implementation
Projects
None yet
Development

No branches or pull requests

4 participants