Wednesday, May 4, 2011

Garment’s process warning list

In a garment several processes runs in the same time. So if you make software for them, you should show some alert to run their all process successfully. Here is the list in which situation your software should show alert to the management.

 

  1. High price: If yarn price is too high. Check from previous record. We have to ask them about yarn price variation. For example we can decide that it vary from 5 to 15 taka.
  2. Low stock: If any yarn stock become too less. We have to ask them what the exact figure of their minimum yarn stock is. For example we can take not less than lbs2000. after every transaction system will check the yarn stock.
  3. More yarn use: If daily transaction of yarn is too much. We have to find it from their previous record.
  4. No yarn report: if no yarn report inserted in day. We have to ask them, do they do daily transaction of yarn? Right now we assume that they do daily transaction.
  5. Without plan: if any yarn sends for any order without planning. Except continuous production.
  6. Too long plan: if we found any plan which has been taken too long time (comparing by historical data).
  7. Too short plan: if we found that the planning time is too short according the production (from historical data we can say we didn't complete production is this short time before).
  8. not cover all items: if plan don't cover all items of a particular order (when any plan will be added, system will check all item of that order, weather the plan created for all items of order or not).
  9. Production isn't going on plan: system will check every day, weather production going on according to plan or behind the plan. if it is 2 weeks behind (we have to ask, do they need alert if 2 weeks behind schedule or more/less than that) then will send alert.
  10. Order without plan: if any order keep in database with out plan for 3 week (we have to clarify the time).
  11. Missing transaction report: if in any stage we found more production than allocated yarn, then there must be some transaction report missing.
  12. No transaction report: if no yarn transaction report inserted in day (except holidays). We have to ask them, do they do daily transaction of yarn? Right now we assume that they do daily transaction.
  13. Huge transaction: if the transaction is very high. System will check this with the historical data.
  14. No production in factory: if there no production report in the factory (except holidays).
  15. Less production in factory: if production level is very low in any factory (except in holidays). We have to ask them, what their minimum production level is. Or we can take it from historical table.
  16. High production in factory: if we find production more than their capacity (when system will give any production report, it will check with its capacity). We should find it out, did they give us wrong production report or they give wrong capacity report.
  17. More/less chemical consumption in dyeing: if dyeing stage consume too much or too less chemical (except holidays). We have to check it from historical data.
  18. Too much wastage in any stage: from historical data we will check all wastage report, weather it is too much or not.
  19. Too less wastage: if wastage report shows 0 or less than that in any stage.
  20. Too much time in any stage: from historical data we will also check the production timing. If they take too much time then it will send a warning.
  21. Shipment delay: if shipment fail in due time.
  22. No shipment: after completion of production from finishing department, if there no shipment for 1 month. We have to ask them is it the warning level for their shipment or not.
  23. No sell: if their no sell of continuous production for one month after completion from finishing department. We have to ask them is it the warning level or not.
  24. Cheap sell: if the price of continuous production is less than its production cost.
  25. No order: if no new order added within one month. We have to ask them is it their warning level or not.
  26. More cost: if expenses become higher than profit.
  27. No data entry: if there no data entry (except holidays).
  28. Loom stopped: if any loom stop for more than 1 day. We have to ask them, is it their warning level or not.
  29. Yarn shortage in loom: if there is no sufficient yarn supply for loom will be within 2 days. We have to be confirmed about 2 days that do they transact yarn before 2days for loom or not.
  30. Too many B category products: from griege section if we find too many b or c category products or less a category product. We have to check it after every griege report and compare it with historical data.
  31. No transaction to griege: after complete production in related stages, if they make more than 2days delay to send product to griege section. We have to know how many days should we wait to send warning.
  32. No action for category b or c: if they don't take any action for b or c category product for 1 week. We have to know is it the right timing for this kind of warning or not.
  33. Delay product transaction: in every internal stage, after completing that stage production, product should be send to next stage within 2 days. Other wise it will show warning. 2 days is our estimated time. We have to ensure about this timing.

 

 

 

NOTE: we should ask them, in their production process, when they need alerts or warnings?

 
Shahana Shafiuddin

Post a Comment