Friday, October 24, 2008

Technical Economizing III (Capacity 4)

To complete the technical economizing process, the final list of assumptions is shown along with the rationale for the decision made:

1. Investigate possible alternatives
2. Identify minimum standard of acceptability
3. Choose alternative that at a minimum meets the minimum standard of acceptability
4. Define rationale for choice of selected alternative
5. Examine effectiveness of selected alternative (future)

Here is the final list of assumptions that will be used to provide capacity guidance for the system:
Assumption
1. PXI runs 24 hours a day and 7 days a week.
2. PXI processes one command at a time.
3. PXI has no down time.
4. Technicians available 24 hours a day 7 days a week.
5. Technicians insert carriers prior to first command of test.
6. Technicians remove carriers within one hour following test.
7. Technicians provide system notifications of carrier insertions and removals.
8. Scheduling provides at least one hour until test start following reservation.
9. Scheduling considers only docking stations in open state.
10. Scheduling considers carriers without regard for group.
11. Scheduling considers actions in one second increments.
12. Recipe’s length is approximately 86 hours.
13. Recipe’s longest command is 30 seconds.
14. Recipe defines time tolerances for command execution.
15. Recipe contains 30 minutes between scheduled start times of each command.
16. Calibration and maintenance not considered.
17. Error detection and correction not considered.
18. Displaying test progress and results not considered.

The assumption which the entire system is dependent is the time it takes the system to execute it’s longest (slowest) command. For no matter how efficient the other components of the system are made, the capacity of the system will be dependent on it’s longest (slowest) command. No matter how cleverly scheduling is designed, no matter how the deftly the recipe is crafted, or how optimal operations are set up, the capacity of the system will ultimately be dependent on it’s longest (slowest) command. For the purpose of modeling simplicity, these assumptions reflect the fact that with the exception of the longest command execution, the other components of the system will not impact system performance significantly enough to be realistically considered.

No comments: