250 likes | 353 Views
Seminario su Swarm 2001-2002 Pietro Terna pietro.terna@unito.it web.econ.unito.it/terna. Secondo semestre mercoledì 27.3 mercoledì 10.4 mercoledì 24.4 martedì 7.5. sempre dalle 17.15 alle 19, aula 12. “nostro” sito a http://eco83.econ.unito.it/swarm/
E N D
Seminario su Swarm 2001-2002 Pietro Terna pietro.terna@unito.it web.econ.unito.it/terna Seminario Swarm 2001 2002
Secondo semestre mercoledì 27.3 mercoledì 10.4 mercoledì 24.4 martedì 7.5 sempre dalle 17.15 alle 19, aula 12 Seminario Swarm 2001 2002
“nostro” sito a http://eco83.econ.unito.it/swarm/ iscriversi alla mailing list seminarioswarm (vedi sopra per le istruzioni) inoltre è utile http://eco83.econ.unito.it/swarm/materiale/ questo file ppt e i successivi sono/saranno in linea a http://web.econ.unito.it/terna/swarm/ e a http://eco83.econ.unito.it/swarm/materiale/pptDelSeminario01-02/ questo è seminarioSwarm01-02-20020327.ppt Seminario Swarm 2001 2002
jVE – Java Virtual Enterprise Presentazione per SwarmFest 2002 a web.econ.unito.it/terna/jve/jVE SwarmFest 2002.zip Seminario Swarm 2001 2002
A dictionary dictionary unit = a productive structure within or outside our enterprise; a unit is able to perform one or more of the steps required to accomplish an order order = the object representing a good to be produced; an order contains technical information (the recipe describing the production steps) and accounting data recipe = a sequence of steps to be executed to produce a good Seminario Swarm 2001 2002
recipes and units Recipes and units A system of enterprises and micro productive units (a swarm) market Enterprise front end 1-2 2-13 28-7-27-7 ... recipes units FE 7 our jVE enterprise (a sub-swarm of units) FE 28 27 Seminario Swarm 2001 2002
WD WD WD: What to Do Seminario Swarm 2001 2002
basic recipe Basic recipe WD The basic recipe in an order is: step in recipe time quantity measured in days, hours, seconds n1 ts m1 n2 ts m2 n3 ts m3 n4 ts m4 . . . time specification: days, hours, seconds Seminario Swarm 2001 2002
batch production Batch production WD a unit is making a batch production if in a given time interval it repeats b times the production of the same step of the recipes of b orders step in recipe time quantity measured in days, hours, seconds n1 ts m1 n2 ts m2 n3 ts m3 / b3 time specification: days, hours, seconds the slash is followed by the number of production steps to be repeated in the given time interval: in a batch production of b pieces, the time necessary for the production of each piece is measured by the fraction m/b Seminario Swarm 2001 2002
Procurements or component parts produced by ourselves procurement and component parts WD Procurements: we order outside the components coded cx (here c1, c2, c3); our management has to deal with the time necessary to have the order performed, to make the transport, etc. (in the third line, n2 can be a transport step) e stays for end n1 ts m1 e c1 n1 ts m1 / b1 e c2 n1 ts m1 / b1 n2 ts m2 / b2 e c3 We can explore the details of these recipes considering other jVEs=swarms and so using swarm of swarms n1 ts m1 n2 ts m2 n3 ts m3 e c4 Component parts produced internally: we produce inside the components coded cx (here c4, c5, c6); our management has to deal with the time necessary to have these internal order performed n1 ts m1 e c5 n1 ts m1 / b1 e c6 Seminario Swarm 2001 2002
steps using component parts Using component parts (mainly, in assembly steps) WD p stays for procurement step in recipe n1 ts m1 p k c1 c2 . . . ck n2 ts m2 . . . after step n1 we have here a procurement phase (internal or external), looking for k components coded c1, c2, . . ., ck the unit performing the successive step asks to a special object ‘procurementAssembler’ to check if the internal or external units can send the components; if not, the unit waits the ability of a unit to call a special object to have special tasks performed, increases widely the degrees of freedom of the jVE structure Seminario Swarm 2001 2002
multiple paths Multiple paths in recipes WD after each step we can have multiple paths in our recipes, but only one of them is followed at a specific time n1 ts m1 n2 ts m2 n3 ts m3 n4 ts m4 or n22 ts m22 end we use here a C-like formalism (|| = or) n1 ts m1 || 1 n2 ts m2 n3 ts m3 || 2 n22 ts m22 || 0 n4 ts m4 where || 0 stays for the conclusion of the multiple paths Seminario Swarm 2001 2002
parallel paths Parallel paths in recipes WD after each step we can have also parallel paths in our recipes, all to be simultaneously executed at a specific time n1 ts m1 n2 ts m2 n3 ts m3 n4 ts m4 and n22 ts m22 end we use here a C-like formalism (&& = and) n1 ts m1 && 1 n2 ts m2 n3 ts m3 && 2 n22 ts m22 && 0 n4 ts m4 where && 0 stays for the conclusion of the multiple paths Seminario Swarm 2001 2002
An intricate example (i) an intricate example (i) WD p 4 c1 c2 c3 c4 n1 ts m1 n2 ts m2 n3 ts m3 n4 ts m4 or p 2 c1 c2 n5 ts m5 n6 ts m6 and p 2 c3 c4 n7 ts m7 gives ||1 p 4 c1 c2 c3 c4 n1 ts m1 ||2&&1 p 2 c1 c2 n5 ts m5 &&2 p 2 c3 c4 n7 ts m7 &&0n6 ts m6 ||0 n2 ts m2 n3 ts m3 n4 ts m4 Seminario Swarm 2001 2002
An intricate example (ii) an intricate example (ii) WD We can represent the same example as a supply chain; so the second path of the or choice becomes … p 2 c1 c2 n5 ts m5 e c1001 p 2 c3 c4 n7 ts m7e c1002 and, summarizing, p 4 c1 c2 c3 c4 n1 ts m1 n2 ts m2 n3 ts m3 n4 ts m4 or p 2 c1001 c1002 n6 ts m6 Seminario Swarm 2001 2002
a closer look to inventories WD A closer look to inventories Seminario Swarm 2001 2002
Warehouses and inventories: stand alone productions warehouses 28-7-27-7 WD units ? FE 7 FE 28 7 27 ? ? ? ? … how to decide? Seminario Swarm 2001 2002
Procurement procurement 28-7-27-7 WD units FE 7 121 34 28 ... 73 Exploding recipes to consider deeply sub–procurement problems 28-121-34-…-73-7-27-7 Seminario Swarm 2001 2002
Inventories in supply chains inventories in supply chains n1 n2 . . . n10 e 121 n11 n12 . . . n15 e 341 n21 n22 . . . n25 e 342 p 2 341 342 31 e 34 WD virtual or actual units keeping the completed procurement components in a list (in a warehouse) Seminario Swarm 2001 2002
DW DW DW:whichisDoingWhat Seminario Swarm 2001 2002
simple units Simple unit data are reported in a text file DW unit_#__useWarehouse____prod.phase_#____fixed_costs_____variable_costs 1 1 11 12 1 2 1 0 0 0 3 1 3 15 2 4 1 0 0 0 5 1 51 12 2 6 1 6 11 20 7 1 12 23 1 8 1 8 22 11 9 1 13 7 12 10 1 18 40 7 11 1 11 5 1 Seminario Swarm 2001 2002
complex units 1 DW Complex units are able to perform more than one (unique) production step We read their data from a sheet in a spreadsheet (Excel like, produced via Office or StarOffice or OpenOffice or . . . To access spreadsheet data from a Java environment we use the ExcelReader.java class, written by Michele Sonnessa (sonnessa@di.unito.it) and based upon the Andy Khan's excelread library (http://www.andykhan.com/excelread/) Seminario Swarm 2001 2002
The general scheme (to be used as a remark page) complex units 2 DW Seminario Swarm 2001 2002
A specific complex unit complex units 3 DW Seminario Swarm 2001 2002
Scaricare jVE da http://web.econ.unito.it/terna/jve/ usando jVEfileProvvisoriPerSeminario.zip oppure la versione 0.60 non appena disponibile Iniziamo a studiare il modello da VEFrameModelSwarm.java UnitParameters.java Unit.java Seminario Swarm 2001 2002