The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page
Google
  Web Elsmar.com
*Please be aware that SOME RECENT forum threads may not yet be indexed by Google.

View Full Version : Industrial Engineering department hierarchy


Osman
9th April 2008, 07:35 AM
Industrial engineering department

Recently I joined socks manufacturing company, I appointed as junior Asst manager in Industrial engineering department. I.E department goes under Production (knitting & seaming) manager, production manager wants to restructure I.E department as follows.

1. training
a) technical training
b) general training

2. layout designing and relocation

3. work study
a) method study
b) work measurement

4. planning costing and capacity calculation ( recently this function done by Product planning & development department)

5. changeover and WIP (this one also done by PPD department)

Changeover includes
a) programming the machines
b) machine setting
c) yarn feeding
d) removing old yarn

Work in process (WIP)
The main function of WIP section is to monitor and control socks handling from dept to another and count socks quantity (accountability).

We have 4 stations for WIP, between departments e.g. 1 station b/w knitting and seaming, 1 b/w seaming and dying and 2 b/w dying and finishing department

The manager when preparing the Hierarchy, he put change over and WIP in one box, and he make 10 sub-boxes under this section (please see excel attached file)
My question is that what are the possible designations/ positions can come under (change over and WIP) Hierarchy ????

I.E dept orgonogram is attached

Waiting your valuable suggestions

Regards

Randy
9th April 2008, 09:13 AM
You really want to know the truth? It doesn't really matter what anyone is called as long as they understand their responsibilities and have the competence to meet them.

Organization charts and fancy titles count for next to nothing. Colin Powell

ScottK
9th April 2008, 09:16 AM
How many people total? I can't tell if that's a heirarchy of functions or if there is a person occupying each box.

SteelMaiden
9th April 2008, 09:28 AM
I agree with Randy, it doesn't matter what Job Titles you use, as long as personnel understand what their function is. My advice is to use generic or broad stroke titles. Inspector, vs. Inspector of toe seams, Inspector of ankle cuffs, etc. (OK, they were just examples, nobody said I actually knew anything about sock production:tg:)

Welcome to the Cove!:bigwave:

Jim Wynne
9th April 2008, 10:22 AM
Inspector of toe seams, Inspector of ankle cuffs, etc. (OK, they were just examples, nobody said I actually knew anything about sock production:tg:)


Let's not forget about verification of the mechanism that causes one sock from each pair to disappear when doing the laundry.:tg:

ScottK
9th April 2008, 10:30 AM
I agree with Randy, it doesn't matter what Job Titles you use, as long as personnel understand what their function is. My advice is to use generic or broad stroke titles. Inspector, vs. Inspector of toe seams, Inspector of ankle cuffs, etc. (OK, they were just examples, nobody said I actually knew anything about sock production:tg:)

Welcome to the Cove!:bigwave:

My most recent QC Inspector hire was a sock inspector in a prior job.
No BS.

BradM
9th April 2008, 10:38 AM
Osman, we appreciate you coming to the site to ask questions:yes:. I am interested in your question. Is it significant in your organization what titles people have? Kind of in the same vein as the other responses, on the surface it does not seem important what titles people have.

As far as the layout of the department, it seems on the surface that it is organized according to function. Have you considered a process layout? A cellular layout of your stations and the IE department, you would appear to gain better understanding of the process. With a functional design, it's possible that each group will get different numbers, use different approaches, etc. With everyone process-oriented, you will be able to develop much more accurate queues as an example.

Osman
12th April 2008, 04:31 AM
Thanks all for welcome me in the cove

dear SteelMaiden check out the attached file :tg:
i spent 2 moths here, but still cant memorize all parts and defects of sock

Osman
12th April 2008, 04:45 AM
dear Randy BradM & ScottK
I will consider your advice, and am revising the chart now. :cool:

Osman
12th April 2008, 04:48 AM
Let's not forget about verification of the mechanism that causes one sock from each pair to disappear when doing the laundry.:tg:

:lol: ...........