Anyone here deal with production line planning and monitoring apps?
-
Your Hungarian link takes me to the disambiguation for Hungarian, with no mention of an alorithm.
Fixed, seems there is a problem when I paste an address like: http://en.wikipedia.org/wiki/Hungarian\_\_algorithm CP sometimes only gets: http://en.wikipedia.org/wiki/Hungarian\_
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS Whenever methodologies become productized, objectivity is removed from the equation. -- Mike Myatt
-
It's grading doesn't matter, I'm sure I would lap it up. I studied one year of quantitative management in an attempt to upgrade my CS diploma into a BSc, but dropped out after not giving stats enough attention, and back in my late 20's it was all or nothing; no getting by on 51%; rather get back to real life work, play, drugs, and making money.
:laugh: At least you've got your priorities right! :-D
Will Rogers never met me.
-
I have embarked on a project to build and app for planning and reporting on throughput on small to medium production lines. Initially we will target those used in the plastics moulding industries. I've always wanted to so something like this, and I have no end of assumptions w.r.t. values input and sampled, but I would really like some pointers for some high level research. What apps can I look at? If you have worked on such an app, what techs did you use? If you use such apps, what do you like and dislike etc.
You are looking at what is known as a Manufacturing Execution System (MES). Any manufacturing software would have an application module called MES. This used to be known as a Shop Floor Control System. The fundamental concept is that any work-order to produce a product flows through a series of work centers. At each work center, a certain quantity X enters the work center to be worked on and a quantity Y is the output. The difference, X-Y, is the amount that is scrapped because it is damaged. some portion of (X-Y) may be recovered thru re-work but the rest is just thrown on to the waste heap. At each work center, you also want to note down Time of Entry and Time of Exit so that you know how much time was spent. You may also add additional raw material at some work centers. The time spent, the number of workers at the work center, the raw materials added, the semi-worked products brought in, etc., are all used to determine the cost-addition at each work center. Depending on the type of factory, the work center equipment may produce some of these information and maybe interfaced to the data collection equipment. In many instances, at least some information may have to be manually input by the operator. You may want to read up on Shop Floor Control System.
-
I have embarked on a project to build and app for planning and reporting on throughput on small to medium production lines. Initially we will target those used in the plastics moulding industries. I've always wanted to so something like this, and I have no end of assumptions w.r.t. values input and sampled, but I would really like some pointers for some high level research. What apps can I look at? If you have worked on such an app, what techs did you use? If you use such apps, what do you like and dislike etc.
If you are recording large amounts of potential data, I would suggest you think about implementing a swinging door compression algorithim with user definable exception and deviation and mandatory interval settings on a per point basis. Search google there are quite a number of good articles explaining these. For front end views, search on sites like Emerson (DeltaV), OSISoft PI (Processbook), Wonderware (Intouch), ABB (System 800) and look at product demos and tutorials on these sites and youtube, for ideas on what the systems can provide, the look and feel, user options etc. Even a glance at some of these can be inspiration on what you want to add. Don't copy though, or Apple might sue you :rolleyes:
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
You are looking at what is known as a Manufacturing Execution System (MES). Any manufacturing software would have an application module called MES. This used to be known as a Shop Floor Control System. The fundamental concept is that any work-order to produce a product flows through a series of work centers. At each work center, a certain quantity X enters the work center to be worked on and a quantity Y is the output. The difference, X-Y, is the amount that is scrapped because it is damaged. some portion of (X-Y) may be recovered thru re-work but the rest is just thrown on to the waste heap. At each work center, you also want to note down Time of Entry and Time of Exit so that you know how much time was spent. You may also add additional raw material at some work centers. The time spent, the number of workers at the work center, the raw materials added, the semi-worked products brought in, etc., are all used to determine the cost-addition at each work center. Depending on the type of factory, the work center equipment may produce some of these information and maybe interfaced to the data collection equipment. In many instances, at least some information may have to be manually input by the operator. You may want to read up on Shop Floor Control System.
You, Sir, win the first prize for intuiting what I am doing and want. If I could kiss you.... and I don't normally kiss guys!
-
If you are recording large amounts of potential data, I would suggest you think about implementing a swinging door compression algorithim with user definable exception and deviation and mandatory interval settings on a per point basis. Search google there are quite a number of good articles explaining these. For front end views, search on sites like Emerson (DeltaV), OSISoft PI (Processbook), Wonderware (Intouch), ABB (System 800) and look at product demos and tutorials on these sites and youtube, for ideas on what the systems can provide, the look and feel, user options etc. Even a glance at some of these can be inspiration on what you want to add. Don't copy though, or Apple might sue you :rolleyes:
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Interesting stuff to look at, thanks Dave, but we are targeting SME's and initially only operator captured data at most. We don't yet look to competing with big boy manufacturing systems, but rather offer differentiate by being small and affordable enough for the lower side of SME type businesses.
-
Interesting stuff to look at, thanks Dave, but we are targeting SME's and initially only operator captured data at most. We don't yet look to competing with big boy manufacturing systems, but rather offer differentiate by being small and affordable enough for the lower side of SME type businesses.
Unless you have a few hundred million dollars i wouldn't expect you to compete with the Big Boys or even the medium level systems. It is amazing though the things that can pop into your head for ideas when you look at these systems, particularly the videos. Nothing more frustrating than sitting with a blank sheet of paper (or whiteboard) pondering what to do, and just need that initial ideas to kickstart the brain.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
Unless you have a few hundred million dollars i wouldn't expect you to compete with the Big Boys or even the medium level systems. It is amazing though the things that can pop into your head for ideas when you look at these systems, particularly the videos. Nothing more frustrating than sitting with a blank sheet of paper (or whiteboard) pondering what to do, and just need that initial ideas to kickstart the brain.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
DaveAuld wrote:
It is amazing though the things that can pop into your head for ideas when you look at these systems, particularly the videos.
The ideas that pop into my head without watching anything are pretty impressive.
-
You are looking at what is known as a Manufacturing Execution System (MES). Any manufacturing software would have an application module called MES. This used to be known as a Shop Floor Control System. The fundamental concept is that any work-order to produce a product flows through a series of work centers. At each work center, a certain quantity X enters the work center to be worked on and a quantity Y is the output. The difference, X-Y, is the amount that is scrapped because it is damaged. some portion of (X-Y) may be recovered thru re-work but the rest is just thrown on to the waste heap. At each work center, you also want to note down Time of Entry and Time of Exit so that you know how much time was spent. You may also add additional raw material at some work centers. The time spent, the number of workers at the work center, the raw materials added, the semi-worked products brought in, etc., are all used to determine the cost-addition at each work center. Depending on the type of factory, the work center equipment may produce some of these information and maybe interfaced to the data collection equipment. In many instances, at least some information may have to be manually input by the operator. You may want to read up on Shop Floor Control System.
I'm reading alight, and loving it, thanks, but a quick one. What is the term for the process whereby a work centre executes all work orders for the same output item? E.g. a work order is for x plastic bottles, but the parameters that describe how a work centre produces 'plastic bottles' are what? A 'work centre process'?
-
I'm reading alight, and loving it, thanks, but a quick one. What is the term for the process whereby a work centre executes all work orders for the same output item? E.g. a work order is for x plastic bottles, but the parameters that describe how a work centre produces 'plastic bottles' are what? A 'work centre process'?
Why not call it "Activity"? During cost analysis, you do Activity Based Costing (ABC) based on the activity performed at each work center.
-
Why not call it "Activity"? During cost analysis, you do Activity Based Costing (ABC) based on the activity performed at each work center.
Ah yes, this thread has brought me so many reminders of when I worked on SAP. Yes, so an activity is performed at a work centre in accordance with a work order? BTW, the guy who proposes this project broke it to me (haha, 'broke') that they don't want to pay me for it, so all future discussion is purely academic and we are 100% safe from falling into a programming question. :) They are offering me 15% of profits while I do dev for them, but nothing for the months and maybe years before we have proper profit, and no share in the IP! :mad: