Finite capacity Loading - Investigation Processing - Columns

Assured Systems

Finite capacity Loading - Investigation Processing-
Columns - Input Spreadsheet

you can get going with just three columns...

A B C >>> optional columns . . .

1 Batch
(the first row in each column can be any text you wish to use, eg you could put run, lot, job, here if you want, or leave it blank) Resource Hours . . . .

2 103-1 Cut 2 . . . .

3 103-1 Form 4 . . . .

A. The processor assumes the workload is divided up into runs, batches, lots or jobs. Each run or batch must have a unique number. If you want the processor to generate run numbers, leave this column blank. (but then you have to provide information in optional columns for the processor to use to calculate run times and quantities) B. The resource identification. One or more of the resources in this column will be flagged as the bottleneck. Bottleneck resources are assumed to have finite (limited) capacity. Every cell in this column should have an entry. C. The length of time (in hours and decimals of hours) the resource is used for this run. This column is required, or if you leave it blank, make sure that information is provided in optional columns so that the time can be calculated. . . . .

to get a more accurate view you can provide more data in optional columns.
If you are providing a specific optional column, then all the columns before it must exist, but they can be blank if you wish.

. . <<< required columns D E F >>> more optional columns . . .

1 . . . Operation Started Due . . . .

2 . . . 010 1 . . . . .

3 . . . 020 . 4 March . . . .

D. Optional. Processing step code. If more than one resource is needed at a processing step, make sure the step codes are the same. E. Optional. Started code. If the operation step is already started on the resource, put 1 in this column. F. Optional. Due date. Date (and time if desired) that the run, job lot or batch is to be finished. . . . .

for more information:--

info@assuredsystems.com.au

home

	A	B	C	>>> optional columns	.	.	.
1	Batch (the first row in each column can be any text you wish to use, eg you could put run, lot, job, here if you want, or leave it blank)	Resource	Hours	.	.	.	.
2	103-1	Cut	2	.	.	.	.
3	103-1	Form	4	.	.	.	.
	A. The processor assumes the workload is divided up into runs, batches, lots or jobs. Each run or batch must have a unique number. If you want the processor to generate run numbers, leave this column blank. (but then you have to provide information in optional columns for the processor to use to calculate run times and quantities)	B. The resource identification. One or more of the resources in this column will be flagged as the bottleneck. Bottleneck resources are assumed to have finite (limited) capacity. Every cell in this column should have an entry.	C. The length of time (in hours and decimals of hours) the resource is used for this run. This column is required, or if you leave it blank, make sure that information is provided in optional columns so that the time can be calculated.	.	.	.	.

	.	.	<<< required columns	D	E	F	>>> more optional columns	.	.	.
1	.	.	.	Operation	Started	Due	.	.	.	.
2	.	.	.	010	1	.	.	.	.	.
3	.	.	.	020	.	4 March	.	.	.	.
				D. Optional. Processing step code. If more than one resource is needed at a processing step, make sure the step codes are the same.	E. Optional. Started code. If the operation step is already started on the resource, put 1 in this column.	F. Optional. Due date. Date (and time if desired) that the run, job lot or batch is to be finished.	.	.	.	.