Getting Started with FabSim.dll

In this introduction you will find a short description of the FabSim simulation examples coming
with FabSimDemo.exe. Many more details on the commands and models of FabSim are described in
FabSimStart.hlp.

To run a simulation with FabSim, at least three input files are required. The first file contains
data  on the tool sets (collections of semiconductor fabrication equipment) which make up the
factory. The second file describes the lots to be started during simulation (process, start time,
product, number of wafers and others). The third file contains a process run sheet (of course you
may use many more process sequences in additional run sheet files).

Start the superviser program FabStart5.exe (demo version). Press the "Run Batch" button. The 
simulations defined in fab_start.bat will start immediately. All output files are saved to 
the /out directory.

In the first two lines of fab_start.bat the directories for input and output files are set by
setting the corresponding environmental variables.

In the first example FabSim is called with only one (compound) command line parameter
(-trace 4). -trace 4 allows tracking of the toolset no. 4. It's output goes into four files
*.buf, *.occ, *.tra, *.wip which may be viewed with suitably programmed EXCEL sheets. Because
there are no other command line parameters, FabSim now looks for its input files as preset in
the program (located in the directories set above). Toolset data are expected in mach_dat.mset, the lots
to be started in processes.strt. Three run sheets are needed as determined in processes.strt and
depending on the lots listed there: 1000.proc, 2000.proc, 2009.proc, plus an additional rework
run sheet 1000002.proc (rework in process 1000, toolset no. 002). After reading all these files
the simulation starts for an equivalent 200.000 minutes (as is preset internally). The preset output
files are fab_sim.out (all lots processed correctly), fab_sim.scp (lots scrapped during processing),
fab_sim.use (toolset and machine usage), fab_sim.exo (lot cycle time, to be displayed with MS
EXCEL, just start the VB macro driven EVAL_exo.XLS.). As set in fab_start.bat, you will find all
console output in run1.log.

The second example adds some more command line parameters.  -t 250000 will set the
simulatiuon time to 250.000 minutes, -out new will set the name for output files (new.out,
new.exo, new.use).   -wip 20 limits the WIP (work in progress) to 20 lots,  -use 50000 allows to
start collection of usage data (new.use) only after a stabilization time of 50.000 minutes. -d 2
creates a new file with detailed lot processing information of toolset no. 2 (new.log).

In the third example the simulation time is 150.000 minutes (-t 150000) the output files are
named newp1.* (-out newp1), toolset monitoring is extended to all toolsets (-d, this may result
in a large log file), a super hot lot will be started (tools are reserved for this lot), if priority
is set to 1 in processes.strt (-p1).

In the fourth example the simulation runs for 100.000 minutes (-t 100000), another lot start file
proc_single.strt is used (-in_strt proc_single.strt), as well as another toolset input file
mach_dat2.mset (-in_mset mach_dat2.mset). Outputs go to new2.* ( -out new2), all toolsets
are monitored (-d). Only five lots are started here, so you may follow up each lot easily, as it
moves through the factory (see new2.log). The new toolset file is necessary, because the batch
rule has to be adapted to the low lot count: The minimum batch load (min_ba of toolset no. 1)
is set to one lot to prevent lots from waiting forever in front of the batch machine.
