operator's UI and OEE #234
Closed
coolnanye-ship-it
started this conversation in
General
Replies: 2 comments
|
Hi @coolnanye-ship-it, we will discuss about this with team and we will comeback. Thanks for start this discussion |
0 replies
|
@coolnanye-ship-it take a look for new release v0.20.0 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
OenMES is a great project, and I'm working hard to understand and evaluate openmes' functionality and possible usage scenarios.
One of the current problems is that I find the operator interface very confusing. Similar interfaces switch between each other, making it difficult to figure out what function is being expressed. I hope this area can be redesigned more clearly. Many of the first-line operators are not very high quality, and it is best to have a fool-like operation interface.
Regarding OEE, I saw that the workstation itself is not associated with some actual production equipment, but maps some tags directly from the data source to the workstation. However, in actual production, workstations usually correspond to physical machines. A work station is also likely to be composed of several machines. Of course, the existence of purely manual work stations is not ruled out. I hope to add a layer of physical machines below the workstation, and labels can also be bound to these physical machines, so that it can undertake more functions, such as the OEE indicator of a certain device. The real-time operating status of a certain device and the operation and maintenance status of a certain device.
One benefit of adding the physical machine equipment layer is that it makes the system hierarchy of openmes more consistent with the real production environment and easier to understand and use.
Here are some of my suggestions.
All reactions