Our company started with a MSAccess based system for reporting labor time and displaying a schedule of jobs to build.
Now we have created an intranet based schedule that displays the production schedule, short materials, maintenance schedule, feeder maintenance etc.
The production schedule is broken down by line, then assembly versus inspection. It also then links to a production report.
We have a talented programmer here on our IT staff who whips up anything we asks. I usually do the report/querry in MSAccess then he dumps the SQL into ASP.
The system is not tied into our MRP system directly..the jobs are manually entered by the stockroom when the get the released WO. But the schedule can then pul up BOM, inventory values etc. by looking into MRP database tables. The MRP system doesn't provide the custom reports I designed for my operators.
The schedule has a priority field for each job..at first they have the priority #20..so then the due date is the second field for prioritization. As I "pull" the jobs from the que I give them a lower priority number..I may move one job ahead of another based on back order sales reports, butI'm usually ahead of the game so the due dates rule.
BUT...the one thing that is fixed is priority #1 (on the machine) & #2 (setup offline waiting)..once a job enters this stage, they are not changed come hell or high water. #3 is kitted and sitting in a bin waiting..if a new kit can be made in time then it might get moved ahead of the previous kit waiting.
This message was posted the
Electronics Forum @
reply »