04.03.2013 Views

BULETINUL INSTITUTULUI POLITEHNIC DIN IAŞI - Universitatea ...

BULETINUL INSTITUTULUI POLITEHNIC DIN IAŞI - Universitatea ...

BULETINUL INSTITUTULUI POLITEHNIC DIN IAŞI - Universitatea ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Customer<br />

(online configurator)<br />

Sales<br />

(configurator, ERP,...)<br />

custom<br />

request<br />

Design<br />

(CAD, FEM, ERP, PDM, MBS,...)<br />

Part Design (e.g. Hydraulic)<br />

(CAD, FEM, calculation, PDM,...)<br />

Purchasing<br />

(ERP,...)<br />

Production<br />

(CAM, NX-Daten,...)<br />

record<br />

request<br />

Legend:<br />

Bul. Inst. Polit. Iaşi, t. LVI (LX), f. 2, 2010 229<br />

request<br />

response<br />

analyze<br />

characteristic<br />

request<br />

curves<br />

request response<br />

design<br />

part<br />

consultation<br />

request response<br />

Department<br />

(used software)<br />

clarification<br />

timeline<br />

preliminary offering<br />

schedule<br />

delivery<br />

date<br />

document action<br />

Fig. 1 – Sequence diagram of the standard processes<br />

for the generation of a customized offer.<br />

offering<br />

order<br />

placed<br />

decide<br />

Currently the customer describes to the sales department the requirements<br />

for the desired product. The sales department interprets the customer<br />

requirements and communicates them further to the design department. There is<br />

normally no sufficient common platform for communication and therefore<br />

unnecessary iteration cycles are done. This can be improved through direct<br />

interfaces between the customer and the two departments, by using a common<br />

configuration tool, which generates department specific product information<br />

and documentation. This solution will be discussed further in the next section.<br />

Another common problem that occurs in the processes described in Fig. 1 is<br />

that generally the project information and awareness remain only in a small<br />

group of specialists. They are not reused for later following projects and are<br />

unavailable for new employees. The company specific knowledge base would<br />

help in solving this problem, by documenting existent intellectual property of<br />

the employees into the pre-structured product specific knowledge.<br />

A good example of a holistic knowledge framework to design and<br />

implement a knowledge based organization is presented by B i n n e r in [4]. This<br />

paper concentrates on the early design phases and can be seen as a methodology<br />

for the previous steps taken in knowledge frameworks systems.<br />

It is therefore not necessary to consider the entire company’s knowledge<br />

base, but rather only the product specific knowledge used in early design phases<br />

to generate a correct first offer. Such comprehensive and integrated knowledge<br />

management solutions are currently almost absent in practice.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!