Friday, October 24, 2008

Technical Economizing II (Capacity 3)

The next step in the process is filtering out assumptions based on a minimum standard. As the minimum standard evolves, so too will the assumptions.

Again, to generate assumptions, for each component:
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)

Minimum acceptable standard
1. Is the assumption directly related to capacity and is the assumption unique to this list?
a. 1 = Yes
b. 1.5 = Yes but combine with another assumption
c. 2 = Not Sure
d. 3 = No

Initial List of assumptions

Assumption
Rating
1. ETS Technicians will always be available and able to operate the system - even if the system should require operating at odd hours of the day and night.
1
2. ETS Technicians will be qualified to run the system.
3
3. ETS Technicians will be available for training as needed.
3
4. ETS Technicians will not be qualified to run the system initially.
3
5. ETS Technicians will require training.
3
6. Scheduling will take place before physical carrier insertion.
1
7. The technician will be allowed one hour to insert carriers following scheduling and prior to first command of test.
1
8. Some amount of time must be allocated by the scheduler to provide for carrier insertion by technicians.
3
9. The technicians will be both physically fit enough and cognitively developed enough to handle the insertion of carriers into the system.
3
10. The docking station and carrier will be designed in such a fashion that a trained technician who is sharp of mind and sound of body will be able to make the insertion.
2
11. The technician should not have to click a button following physical insertion of the carrier.
2
12. Iodine PXI’s do not send out a carrier insert message upon carrier insertion.
1
13. Pulse PXI’s send out a carrier insertion upon carrier insertion.
1
14. Technicians must work with in conjunction with the system to provide system notifications of carrier insertions.
1.5
15. Iodine PXI’s do not send out a carrier insert message upon carrier insertion.
1
16. Pulse PXI’s send out a carrier insertion upon carrier insertion.
1
17. Technicians will be required to take action to produce carrier insertions when working with Iodine systems.
3
18. Technicians will not be required to take action to produce carrier insertions when working with Pulse systems.
3
19. The technician will be allowed one hour to remove carriers following scheduling and prior to first command of test.
1
20. Some amount of time must be allocated by the scheduler to provide for carrier removal by technicians.
3
21. The technicians will be both physically fit enough and cognitively developed enough to handle the removal of carriers into the system.
3
22. The docking station and carrier will be designed in such a fashion that a trained technician who is sharp of mind and sound of body will be able to make the removal.
2
23. The technician should not have to click a button following physical removal of a carrier.
2
24. Iodine PXI’s do not send out a carrier remove message upon carrier removal.
1
25. Pulse PXI’s send out a carrier remove upon carrier removal.
1
26. Technicians must work with in conjunction with the system to provide system notifications of carrier removals.
1.5
27. Iodine PXI’s do not send out a carrier insert message upon carrier removal.
1
28. Pulse PXI’s send out a carrier remove upon carrier removal.
1
29. Technicians will be required to take action to produce carrier removed when working with Iodine systems.
3
30. Technicians will not be required to take action to produce carrier removed when working with Pulse systems.
3
31. There will be one 24 hour maintenance window each month dedicated to maintenance and calibration.
2
32. The system will be required to take docking stations offline for maintenance.
2
33. The system will be required to take PXIs offline for maintenance.
2
34. The system will be required to take the CPC offline for maintenance.
2
35. The system will be required to take PXIs offline for calibration.
2
36. The PXI will always be up and running 24 hours a day and 7 days a week.
2
37. The system will need an active connection to the database to start a test.
3
38. The system will not need a connection to the database to complete a test once started.
3
39. The system will use Velocity technology to support the need to complete a test without a database.
3
40. Network maintenance will not affect system performance.
1
41. The network will always be up and running 24 hours a day and 7 days a week.
1
42. The PXI will run 24 hours a day and 7 days a week
1
43. The CPC will be available during recipe execution
1
44. The PXI will be available during recipe execution
1
45. The time it takes for the CPC to detect and send a command will be less than one second.
3
46. The time it takes for the CPC to detect and send a command will have such a small value it will not be relevant to the general estimate for total command processing time.
1
47. The time it takes for the CPC to store background measurements will be less than one second.
3
48. The time it takes for the CPC to store background measurements will have such a small value it will not be relevant to the estimate for total command processing time.
1
49. The storing of pulse train results will take place on a secondary thread so as not to effect total command processing time.
1
50. As directed by the status display screen, the technician will perform actions required to facilitate testing in a timely manner.
3
51. Interaction with the system status display will not affect capacity calculation.
1
52. System performance may be estimated using normal flow of execution.
1
53. Error detection and correction will not affect system performance.
1
54. The software will not be bound by a future window and look as far into the future as necessary to make a reservation.
1
55. The software will not be bound by lower reservation bound and look as early into the present as necessary to make a reservation.
1
56. The software will not support layered scheduling – scheduling against docking stations that are full or reserved.
1
57. Carriers will be scheduled with no consideration for of what group they are a part
1
58. There will be 30 minutes between the scheduled start times of each command.
1
59. The total execution time of a recipe will not exceed 86 hours in length.
1
60. The total time to execute an apply load command will not exceed 20 seconds.
1
61. The total time to execute a remove load command will not exceed 20 seconds.
1
62. The total time to execute a change load command will not exceed 30 seconds.
1
63. The total time to execute background measurement command will not exceed 10 seconds.
1
64. The total time to execute a pulse train command will not exceed 2 minutes.
1
65. PXI can only process one command at a time
1

Assumptions after first normalization:
Assumption
Rating
1. ETS Technicians will always be available and able to operate the system - even if the system should require operating at odd hours of the day and night.
1
2. Scheduling will take place before physical carrier insertion.
1
3. The technician will be allowed one hour to insert carriers following scheduling and prior to first command of test.
1
4. The docking station and carrier will be designed in such a fashion that a trained technician who is sharp of mind and sound of body will be able to make the insertion.
2
5. The technician should not have to click a button following physical insertion or removal of the carrier.
2
6. Iodine PXI’s do not send out a carrier insert message upon carrier insertion.
1
7. Pulse PXI’s send out a carrier insertion upon carrier insertion.
1
8. Technicians must work with in conjunction with the system to provide system notifications of carrier insertions and removals.
1
9. The technician will be allowed one hour to remove carriers following scheduling and prior to first command of test.
1
10. The docking station and carrier will be designed in such a fashion that a trained technician who is sharp of mind and sound of body will be able to make the removal.
2
11. The technician should not have to click a button following physical removal of a carrier.
2
12. Pulse PXI’s send out a system message upon carrier removal.
1
13. Iodine PXI’s do not send out a system message upon carrier removal.
1
14. The PXI will run 24 hours a day and 7 days a week.
1
15. The CPC will be available during recipe execution.
1
16. The PXI will be available during recipe execution.
1
17. The time it takes for the CPC to detect and send a command will have such a small value it will not be relevant to the general estimate for total command processing time.
1
18. The time it takes for the CPC to store background measurements will have such a small value it will not be relevant to the estimate for total command processing time.
1
19. The storing of pulse train results will take place on a secondary thread so as not to effect total command processing time.
1
20. Interaction with the system status display will not affect capacity calculation.
1
21. System performance may be estimated using normal flow of execution.
1
22. Error detection and correction will not affect system performance.
1
23. The software will not be bound by a future window and look as far into the future as necessary to make a reservation.
1
24. The software will not be bound by lower reservation bound and look as early into the present as necessary to make a reservation.
1
25. The software will not support layered scheduling – scheduling against docking stations that are full or reserved.
1
26. Carriers will be scheduled with no consideration for of what group they are a part.
1
27. There will be 30 minutes between the scheduled start times of each command.
1
28. The total execution time of a recipe will not exceed 86 hours in length.
1
29. The total time to execute an apply load command will not exceed 20 seconds.
1
30. The total time to execute a remove load command will not exceed 20 seconds.
1
31. The total time to execute a change load command will not exceed 30 seconds.
1
32. The total time to execute background measurement command will not exceed 10 seconds.
1
33. The total time to execute a pulse train command will not exceed 2 minutes.
1
34. PXI can only process one command at a time.
1
35. The PXI will have no down time.
2
36. Time for Calibration and Maintenance are not considered.
1
37. Docking Stations are available for scheduling one hour after carrier is removed (reword?).
3
38. Power will not fail during recipe execution.
3
39. Must check Z meter every 30 minutes.
3
40. Load Plug check performed outside the rack.
3
41. The recipe chosen for scheduling will define time tolerances for the allowable execution time of each command.
2
42. The recipe chosen for scheduling will define the time between the scheduled start time of each command.
2
43. PXI will not send error messages.
1
44. Actions are scheduled in one second increments.
1
45. The software will need an active database connection to start a test.
3
46. The software will not need an active database connection to complete a test that has been started.
1
47. Only docking stations in an open state will be considered for scheduling
1
48. Docking stations will be scheduled as they become available with no consideration for what group they are a part of.
1
49. Displaying of test results will not affect system performance.
1

Met with team and determined minimum standard should be:
a. Directly related to iodine system capacity?
b. Unique to this list (not covered by other assumptions)?
c. Using active voice?

Produced the following assumptions:

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.

No comments: