Topic > Automatic Medicine Sorter - 667

Project Title: Automatic Medicine Sorter Preparation Date: 01/12/2013 Process Description: Medicine sorting process is very useful in all pharmaceutical companies as it is the part most essential of the entire cycle medicine production. Therefore, in several enterprises at once in Pakistan, the operation is conducted manually, so the level of hygiene is quite low. So, at the end of this whole chain of processes, we will get an automatic system that can classify different types of medicines based on color, weight and size and this will happen automatically without any human interruption. The main phases of this project would be: Information Gathering  Information Verification  Design  Testing  Calibration Process Metrics: • Each process is designed to reliably produce one or more outputs, so when deciding which metrics to develop, we focus always first and foremost on the outputs of the process, not on the activities. The metrics should measure whether the process not only produces the outputs but also that all appropriate expectations are met each time the process runs. • In early metrics development, we focus on what to measure, not how the measurement will occur. There are several reasons for this: First, the decision whether to create a certain metric is initially more important than determining exactly how the data might be tracked, reported, stored, and so on. While measurement can be expensive and sometimes not worth the effort, we've seen some teams give up on a potentially valuable metric just because they weren't exactly sure how to collect the data to begin with. Usually, you have the option to choose what to collect and report – for example, perhaps focus only on exceptions or only on quarterly reporting – which can reduce half the paper so that it is clear which actions support each objective. The columns are defined as follows: Primary Objective and Intermediate Objectives: This column indicates the primary and intermediate objectives of the improvement project. Each intermediate goal in the action plan is based on a problem statement. For example, the problem statement “Evolving Requirements” can be rewritten as the intermediate objective “Manage Evolving Requirements.” The intermediate goal is a statement of the desired outcome when the problem has been solved. Goal Purpose: This column reminds you why you achieved this goal. The reason is determined by asking yourself: why do I want to achieve this goal? What advantage does it offer? Always complete this column. It will keep you focused and guide you in the moments when you are ready to give up. Attach a flowchart of the current process and planned future processes.