Tuesday, December 2, 2008

Template creation in visual studio 2008

Visual studio templates are extremely useful tools which can be used to share commonalities across projects. Application functions that are commonly included at the project level include security, configuration, logging, error handling, navigation and reports. To create a template from any project from visual studio:

1. -->Tools-->Customize-->Commands-->File and drag the Export Template... button to any menu in the menu bar.
2. -->Export Template... select Project template -->Next. Enter a name and description for the template to be created.

Visual studio will by default export the to the visual studio 2008\my exported templates\ directory.

3. Add the to the visual studio template directory. (This directory can be found at -->Tools-->Options-->Projects and Solutions-->General : User project templates location. Also, make sure the "Save new projects when created " checkbox is selected as templates created in temporary projects directories can have unpredictable results.

4. Create a new project and select the newly created template as the project type.

Creating a template with commonly used base functions is a great way to get a jump start on any project.

Friday, November 14, 2008

Logging to a database with enterprise library 4.0

Because I had a hard time tracking these down online, I thought it would be prudent to blog some simple steps which may be followed to implement database logging using enterprise library.

1. To create a logging database, run the LoggingDatabase.sql script which by default is installed at C:\EntLib4Src\Blocks\Logging\Src\DatabaseTraceListener\Scripts. This script will create a table with logging capabilities.


2. Create a project


3. Add references to:
Microsoft.Practices.EnterpriseLibrary.Common.dll
Microsoft.Practices.EnterpriseLibrary.Logging.Database.dll
Microsoft.Practices.EnterpriseLibrary.Logging.dll


4. Add a config file to the project


5. Update the config file using VS or EE config manager including:
Data Access connection string to db
Database trace listener
Reference to database trace listener in general log category
Reference to Data access connection in database trace listener

6. Within the entry point of the project project (using button click below) add:

Imports Microsoft.Practices.EnterpriseLibrary.Logging

Public Class Form1

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim log As New LogEntry
log.EventId = 1
log.AppDomainName = Me.Name
log.Title = "messageType"
log.Categories.Add("General")
log.Priority = 1
log.Message = "Test Message"
Logger.Write(log)
End Sub

End Class

Following these steps will result in a log to the database.
Filters may be applied to categorize logged messages.

Friday, October 24, 2008

Optimal Scheduling Algorithm

_

There have recently been discussions regarding the maximum number of docking stations that can be reserved. The maximum number of docking stations that can be reserved is a result of several factors including the scheduling algorithm. The manner in which the recipe is scheduled has a direct impact on the maximum number of docking stations that may be reserved. A clear example of scheduling being used to maximize the number of docking stations that can be run simultaneously can be seen when staggering the start time of a recipe running on multiple docking stations:

Definitions:

Scheduling: is the process by which actions are assigned to a particular docking stations based on the timing defined in a particular recipe.
Total recipe Time (TT), the time from recipe start to completion, is defined in terms of the time when actions are executing (XT) and time when they are not (rest time) (RT). TT = XT + RT. For a recipe to be successfully scheduled there must be a window of execution available for each action in the recipe. At all times, the rest time between actions must be consistent with that defined in the recipe.
Earliest Time available (ET), is the first time within the scheduling window where a recipe may be scheduled. For example, if a docking station is on test for the next 10 hours and after 10 hours there are no scheduled actions, ET = 10 hours.
Future Window (FW), is the maximum amount of time (window) into the future that a recipe may be scheduled. Any recipe may be scheduled against any number of docking stations if the future window is set to a large enough value. To schedule a recipe against a particular docking station, ET + TT must be less than or equal to FW. ET + TT <= FW. For example, if a recipe takes 100 hours to complete and the earliest time a scheduling window is available is at hour 20, then the future window must be at least 120 hours.
Reservation Slot (RS), is the sum of all XT slots within FW that make up a single recipe.
Maximum Docking stations reserved (MaxDS), can be defined as the number of available RSs where a docking station may be reserved within FW. As FW becomes grows, so too does capacity.

The recipe in this example contains a structure similar to the familiar 86 hour recipe that has been run for LiI SAT. It is assumed that the recipe includes two commands, a slow running command and a fast running command. The fast command, BkgMeasurement executes in 30 seconds, while the slow command, ChangeLoad executes in 45 seconds. The time between commands is 1800 seconds (30 minutes).
XT(BkgMeasurement) = 30 seconds
XT(ChangeLoad) = 45 seconds
RT = 1800 seconds (30 minutes).

So, the number of commands that may execute within one block of 1800 minutes is:
n(BkgMeasurement) * XT(BkgMeasurement) + n(ChangeLoad) * XT(ChangeLoad) < 1800

In the worst case, if the recipe is reserved such that all docking stations run the change load command in the same 1800 seconds (setting n(BkgMeasurement) = 0 in the equation above), the maximum number of docking stations that could be reserved (MaxDS) is limited by the execution time (XT) of the slow running command, in this case ChangeLoad.

MaxDS = RT / XT(ChangeLoad)
MaxDS = 1800 / 45
MaxDS = 40.

No more than 40 docking stations could ever be scheduled at once, as all change loads would have to execute in the same block of 1800 minutes.

The best case would be if somehow there were no change loads in the recipe, (setting n(ChangeLoad) = 0 in the equation).

MaxDS = RT / XT(BkgMeasurement)
MaxDS = 1800 / 30
MaxDS = 60.

No matter how the recipe is scheduled, there could never be more than 60 docking stations on test.

From above, the minimum MaxDS = 40 and the maximum MaxDS = 60.
Staggering:
A stagger can be defined as delaying the start of a recipe on a number of docking stations in an effort to maximize the number of docking stations that are placed on test. For example, if a recipe is being run on 40 docking stations, using 0 staggers, then all docking stations would start in the first block of time. If 1 stagger was used, 20 docking stations would start in the first block and 20 docking stations would start in the second block. If 2 staggers were used, 13 docking stations would start in first, second and third block. By staggering the start of recipes, the long running commands are separated from each other and more docking stations may be reserved.
Simple Example with 42 docking stations and recipe with 3 commands (Bkg,Change,Bkg):



So, as groups are staggered, the long running commands become separated from each other (1:40, 2:21, 3:17).
Below is a set of data, based on 86 hour test parameters, which records the number of staggers, total docking stations reserved, and time added on to the tests end.
XT(BkgMeasurement) = 30 seconds
XT(ChangeLoad) = 45 seconds
RT = 1800 seconds (30 minutes).






As the number of staggers increases, the number of maximum number of docking stations (MaxDS) that may be placed on test increases from min(MaxDS) (40) to max(MaxDS) (60).



The benefit of staggering diminishes with each stagger. While the first stagger increases maxDS by 8, the second only increases maxDS by 3, and with each additional stagger the gain becomes less.


At first, a single block of ½ hour may be added to the test to MaxDS. However, as the number of staggers increases, it becomes more expensive to place more docking stations on test.
So there is a direct relationship between recipe length, total test time and capacity. In the case of the 86 hour recipe, if the total test time is increased from 86 to 86 ½ hours, then capacity increases by 20% (40à48).
It may be beneficial to investigate staggering recipe starts at the time of reservation.



Group Dynamics

_

This fall I had the privilege to participate and study the facilitation of group dynamics. The course offered numerous insights into challenges faced by leaders on a daily basis including managing different personality types, meeting management, effective decision making, and building teams. I found the material and demonstrations to be practical and enjoyed applying what I learned in class at work and in life.

One topic discussed in class was personality types. In particular, classification of type according to the Briggs-Meyers type indication system was used to identify common patterns of personality. By identifying my own personality type and the personality type of others, I was able to become a more effective communicator. Briggs-Meyers is based on four pairs of contrasting preferences: Extraversion versus Introversion, Sensing versus Intuiting, Thinking versus Feeling and Judging versus Perceiving.

First, the difference between extraversion and introversion reveals a preference for a person’s attitude about their behavior. Extroverts draw their energy from action, external stimuli, and the people around them. They are at their best when active and when inactive their level of energy and motivation tends to decline. Introverts draw their energy from reflection, concepts and ideas. They are at their best when given time to reflect and assess a situation. In assessing myself I found that I had a preference for Introversion (I).

Secondly, the difference between Sensing and Intuition reveals a preference for a person’s ability to interpret the information around them. Sensors prefer information that is taken in through their five senses. They like making decisions based on facts and dislike making decisions based on feelings or their gut. Intuitors tend to prefer relying on intuition, hunches and associating current information with that of a larger pattern. They prefer working with theories and abstractions more than hard figures. In assessing myself, I found that I had a preference for Sensing (S).

Thirdly, the difference between Thinking and Feeling reveals a preference for a person’s ability to make decisions. Thinkers prefer to be more rational when making a decision. They prefer using logical, consistent, systematic methods of making decisions and like to do so without letting their judgment be swayed by sentimentality. Feelers prefer to make decisions considering from the point of view of how their decision will affect other people. In assessing myself, I found that I had a preference for Thinking (T).

Lastly, the difference between Judging and Perceiving reveals a preference for personal closure. Judgers prefer to have matters settled while perceivers prefer life to be more flexible and open. For example a judger would prefer to have upcoming appointments scheduled well in advance while a perceiver would prefer to delay until the last possible moment before making a commitment. In assessing myself, I found that I had a preference for Judging (J).

I found learning about personality types to be particularly useful for managing the relationship with my superiors at work. My immediate boss is an introverted, sensing, thinking type. He prefers to keep conversation not regarding work to a minimum and prefers to receive reports in a direct and to the point fashion. He also avoids providing feedback until the time of annual reviews and does not provide much feedback in general. At first I found this laid back attitude and lack of feedback unnerving. However, recognizing my boss’s personality type really helped me to understand where he is coming from and what to expect from him. I now know that his silence is a reflection of who he is and not a reflection of his perception of my work.

Another concept covered in class was meeting management. At work, I have been placed on a project where all of the members on the team are required to attend a weekly meeting. Each week I would inwardly groan as the time of the meeting would draw close because often times the meeting would end up being three hours of unproductive discussion between two or three individuals without any targets, closure or measure of progress being made. The notion of setting up an agenda for the meeting really helped the group to focus and made time spent in the meeting much more focused and productive. As each agenda item is completed, the associated follow up task is crossed off the list so as the group continues to meet, progress may be measured and accounted for. Also target completion dates are included for each item. This gives the group a sense of when they can expect the item to be completed and helps to encourage work to be done with a sense of urgency. Here is a portion of the agenda that is sent out prior to each of our weekly meetings:
Item
Status
Follow-up
Target Completion Date
1. Performance Test (PT) for CPC timing
· IT & DG to discuss test intent and tests
· Will meet w/Ken D. and finalize protocol
· Ken has given the responsibility to Mark M. Mark’s time on other activities may impact this deliverable
· No start date or document as of 9/26
Target 9/22
Revised 10/6
2. Cal Calibration Equipment
· Need to send out equipment for calibration
· Turnover equipment to Dave Daniels
· Will be sent out no earlier than 9/24
· Equipment should be sent out for cal.
Target 9/26

Target 10/3
3. Calibration Procedure
· Process/procedure now in the ownership of Calibration.
· Dave to submit procedure to become official GB procedure
· Dave will modify as needed
· Dave presented with problems when conducting first cal. Dave will work with VSI to resolve.
· Calibration complete. Dave will work with VSI to review audit files

Actual 10/1

In addition to the agenda, minutes are kept and action items are sent out following the conclusion of each meeting. An example of a portion of the action item list that is sent out is as follows:
Task
Deliverable(s)
Assigned To
Completion Date(s)
1. LiI SAT Burn-in Analysis
§ Complete original SAT document assessment for SAT RER after final analysis is completed in item #2.
Andrea Smith
Dave Smith
10/24
2. LiI SAT Burn-in Analysis – Follow-up Analysis of 9918
§ Complete assessment of raw data from 9918 burn-ins. Assist with data summaries as needed.
Monica Smith
10/10
3. Execute Pulse SAT Tests
§ Execute burn-in portion of SAT
Chris Dasaro
Electrical Test


These action items clearly delegate responsibility, and provide a sense of progress and closure when they are completed. Historically, I have a tendency not to perform well in a meeting setting. My performance could be as a result of my introverted personality or as a result of poor meeting structure. By studying the fundamental building blocks that may be used to make meetings more productive, and gaining the ability to organize and attack meetings in a more systematic manner, I believe that whatever team I am a part of in the future will benefit.
Effective group decision making was another topic of interest that was discussed in class. In a workplace setting, I feel that all too often I have partaken in group meetings where no real progress is made and decisions are forced just for the sake of bringing the meeting to an end. In class we discussed six possible options groups can use to make decisions. Spontaneous agreement, one person decides, compromise, multi-voting, majority voting, and consensus building are all options available to groups when making decisions. I found it interesting to learn about each option and the benefits and disadvantages they have to offer.

The option that I found to be the most applicable to my job on a daily basis was that of consensus. This option involves clearly identifying the issue at hand to all parties involved and coming to an optimal decision based on the options available. In the industry which I work, that of medical technology, correctness and the best solution are often preferred over getting a solution done quickly. As a result, coming to a consensus by exploring all options available and getting support from the individuals involved in making the decision as well as those who will be affected by the decision has proven to be extremely beneficial. In particular taking extra time to make good decisions early on in the design process are well worth it as there is a direct correlation between when an error is uncovered and the cost of resolution to the business. Almost universally, errors that are detected later on in the design process cost more to resolve than those discovered earlier because error correction often involves repeating the processes that resulted in the error occurring in the first place.

Recently, I was able to apply the group decision making by consensus process to a problem I faced at work. The problem involved our team performing electrical tests on a particular group of batteries. The original process, which involved a technician entering test configuration data, an engineering verifying that the configuration was done correctly, and a project manager to verify that the verification was done correctly was longer than it needed to be, cumbersome, and prone to error. By holding a cross functional group meeting which included representation from the quality team, operations, technicians, engineers and management, everyone felt as though they had a stake in the new process. Furthermore everyone actively participated and made suggestions to improve the process that was currently in place. The end result of the meeting was a simple form that the technician could complete that contained all necessary configuration data for the entire test. This form (which had been reviewed by each group) could then quickly be reviewed and approved the test engineer and project manager. By meeting and coming to a consensus, a great deal of synergetic idea generation took place and everyone was comfortable and supportive of the new process.

Teams are an integral part of every modern business. When a team is formed, it should be done with a clearly defined purpose. Teams are comprised of individuals, each with their own personality. The combination of all individual personalities together makes up the group’s personality on the whole. Special care should be taken when selecting individuals to be included in a particular group as the dynamic between individuals has a direct effect on the personality of the group as a whole. The personality of the group should be crafted with a specific task in mind, so as best to achieve the desired result. There are numerous external factors that can inhibit the progress of a group both at the individual and group level. These factors should be identified as early as possible and dealt with as the longer a particular limiting factor influences the group, the greater the amount of negative impact the factor will have upon the group. Each person brings unique talents and abilities to a group. It is the responsibility of the leader or facilitator to place each individual in a role that maximizes the probability that he or she will help the group to achieve its purpose. Most importantly, it is worth recognizing that groups are composed of real people with real feelings and the success of any group rests largely upon the way in which individuals respect each other and work together to maximize their own potential.

Compression in .NET

I am currently working on several projects which require managing large sets of data. Commonly, compression is used as part of the solution. The .NET framework offers compression libraries that compress files up to 99% of their decompressed size. Below is a function written in VB that reports a comparison of the decompressed version of a file with the compressed version of the same file in a message box.

Details of the compression algorithm used can be found at http://www.gzip.org/algorithm.txt .

Reports a comparison of the decompressed version of a file with the compressed version of the same file in a message box.

Private Sub CompressAndDecompressFile(ByVal filename As String)
Dim infile As FileStream
Try
' Open the file as a FileStream object.
infile = New FileStream(filename, FileMode.Open, FileAccess.Read, FileShare.Read)
Dim buffer(infile.Length - 1) As Byte
' Read the file to ensure it is readable.
Dim count As Integer = infile.Read(buffer, 0, buffer.Length)
If count <> buffer.Length Then
infile.Close()
msg = "Test Failed: Unable to read data from file"
MsgBox(msg)
Return
End If
infile.Close()
Dim ms As New MemoryStream()
' Use the newly created memory stream for the compressed data.
Dim compressedzipStream As New GZipStream(ms, CompressionMode.Compress, True)
compressedzipStream.Write(buffer, 0, buffer.Length)
' Close the stream.
compressedzipStream.Close()

msg = "Original size: " & buffer.Length & ", Compressed size: " & ms.Length
MsgBox(msg)

' Reset the memory stream position to begin decompression.
ms.Position = 0
Dim zipStream As New GZipStream(ms, CompressionMode.Decompress)
Dim decompressedBuffer(buffer.Length + buffer_size) As Byte
' Use the ReadAllBytesFromStream to read the stream.
Dim totalCount As Integer = ReadAllBytesFromStream(zipStream, decompressedBuffer)
msg = "Decompressed " & totalCount & " bytes"
MsgBox(msg)

zipStream.Close()
Catch ex As Exception
msg = "Error: The file being read contains invalid data."
MsgBox(msg)
End Try
End Sub

Public Shared Function ReadAllBytesFromStream(ByVal stream As Stream, ByVal buffer() As Byte) As Integer
' Use this method is used to read all bytes from a stream.
Dim offset As Integer = 0
Dim totalCount As Integer = 0
While True
Dim bytesRead As Integer = stream.Read(buffer, offset, buffer_size)
If bytesRead = 0 Then
Exit While
End If
offset += bytesRead
totalCount += bytesRead
End While
Return totalCount
End Function 'ReadAllBytesFromStream

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.

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.

Wednesday, October 22, 2008

Technical Economizing I (Capacity 2)

_

When working on technical projects it is often times necessary to economize based on the available alternatives, that is, as a result of scarcity, resources must be allocated in such a fashion that a minimum acceptable standard is met. The process by which economizing generally takes place is as follows:

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

Once again, the project capacity presents an excellent opportunity to showcase the issue at hand, technical economizing. The first step in the technical economizing process is to investigate alternatives for generating capacity requirements. The diagram below displays the high level component breakdown of ETS:






The technical economizing process will be applied to each component in the system and low level assumptions will be generated as a result:
Assumptions about assumptions: These are the assumptions from which all others will be based.
ASSUMPTION 1: Assumptions are generated based on the best case alternative. While best case alternative may not always be the most likely, it does provide the simplest model from which to work and from which to generate a working model.
ASSUMPTION 2: Best case alternatives will be updated as information becomes available. It is understood that in many instances the best case alternative cannot realistically be selected for the final system. Cases in which the decision to select an alternative based on best case logic are denoted as part of the alternative definition.
INVESTIGATE ALTERNATIVES
1. Operations – The operational component layer is defined by the operational limitations imposed on the system including:
a. Availability of technicians to work the system
i. Known – No limitations regarding technician availability or required expertise have been specified.
ii. Alternatives
1. ETS Technicians will never be available – Starting with this assumption gets nowhere fast…
2. ETS Technicians will always be available – This is the best case alternative and a good point of start from which to work.
3. ETS Technicians will be available during normal work hours – While this is a possible alternative, the case of constant availability is simpler just to assume technicians will be available.
4. ETS Technicians will not be qualified to run the system – This is probably a safe assumption as technicians will not know how to use the system to start with.
5. As Technicians will not be qualified to start with, training will be necessary
6. There is a minimum amount of education \ experience required to operate the ETS system.
7. ETS operator should be selected based on their education and experience.
iii. Assumptions:
1. ETS Technicians will always be available to operate the system - even if the system should require operating at odd hours of the day and night.
2. ETS Technicians will be qualified to run the system.
3. ETS Technicians will be available for training as needed.
4. ETS Technicians will not be qualified to run the system initially.
5. ETS Technicians will require training.
iv. Questions:
1. When will technicians be available to operate system?
2. How many technicians will be available?
3. How much training will technicians require?
4. How much education \ experience will be required of ETS technicians?
b. Execution time for technician to process each test operation
i. Load Carrier
1. Physical load of carrier:
a. Known – Currently, the system provides the technicians one hour to load a carrier.
b. Alternatives:
i. Technicians will load carriers as soon as required by the scheduler.
ii. Some amount of time must be allocated by the scheduler to provide for carrier insertion by technicians.
iii. Technicians will load carriers immediately; no time is required – although best case, not a realistic alternative.
iv. Scheduling will take place before physical carrier insertion – So technician knows where to place carrier.
v. The technician will be allowed one hour to insert carriers following scheduling and prior to first command of test. Some amount of time is required. Why one hour? Because it’s the way we do it now and why not?
vi. The technicians will be both physically fit enough and cognitively developed enough to handle the insertion of carriers into the system.
vii. 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.

c. Assumptions:
1. Scheduling will take place before physical carrier insertion.
2. The technician will be allowed one hour to insert carriers following scheduling and prior to first command of test.
3. Some amount of time must be allocated by the scheduler to provide for carrier insertion by technicians.
4. The technicians will be both physically fit enough and cognitively developed enough to handle the insertion of carriers into the system.
5. 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.

d. Questions:
1. Does scheduling need to take place prior to carrier insertion?
2. How long should the technician be given to insert a carrier?
3. Does the time given to a technician need to be the same across recipes?
4. What are the physical and intellectual requirements of making a carrier insertion?
2. Virtual load of carrier
a. Known – Depending on the type of system, the current system requires a carrier insert to be clicked following carrier insertion.
b. Alternatives:
i. Technicians must work with in conjunction with the system to provide system notifications of carrier insertions.
ii. Iodine PXI’s do not send out a carrier insert message upon carrier insertion.
iii. Pulse PXI’s send out a carrier insertion upon carrier insertion.
iv. Technicians will be required to take action to produce carrier insertions when working with Iodine systems.
v. Technicians will not be required to take action to produce carrier insertions when working with Pulse systems.

c. Assumptions:
1. The technician should not have to click a button following physical insertion of the carrier.
2. Iodine PXI’s do not send out a carrier insert message upon carrier insertion.
3. Pulse PXI’s send out a carrier insertion upon carrier insertion.
4. Technicians must work with in conjunction with the system to provide system notifications of carrier insertions.
5. Iodine PXI’s do not send out a carrier insert message upon carrier insertion.
6. Pulse PXI’s send out a carrier insertion upon carrier insertion.
7. Technicians will be required to take action to produce carrier insertions when working with Iodine systems.
8. Technicians will not be required to take action to produce carrier insertions when working with Pulse systems.

d. Questions:
1. Is it necessary to mandate clicking a button following carrier insert?
2. Why is there a difference between PXI behaviors based on type?

ii. Remove Carrier
1. Physical removal of carrier
a. Known – Currently, the system provides the technicians one hour to remove a carrier.
b. Alternatives:
i. Technicians will remove carriers as required by the scheduler. But right now there are no scheduled remove requirements.
ii. Some amount of time must be allocated by the scheduler to provide for carrier removal by technicians.
iii. Technicians will remove carriers immediately; no time is required – although best case, not a realistic alternative.
iv. The technician will be allowed one hour to remove carriers following scheduling and prior to first command of test. Some amount of time is required.
v. The technicians will be both physically fit enough and cognitively developed enough to handle the removal of carriers into the system.
vi. 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.

c. Assumptions:
1. The technician will be allowed one hour to remove carriers following scheduling and prior to first command of test.
2. Some amount of time must be allocated by the scheduler to provide for carrier removal by technicians.
3. The technicians will be both physically fit enough and cognitively developed enough to handle the removal of carriers into the system.
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 removal.

d. Questions:
1. Will scheduling be dependent on carrier removal within one hour?
2. How long should the technician be given to insert a carrier?
3. Does the time given to a technician need to remove a carrier need to be the same across recipes?
4. What are the physical and intellectual requirements of making a carrier removal?

2. Virtual removal of carrier
a. Known – Depending on the type of system, the current system requires a carrier remove to be clicked following carrier insertion.
b. Alternatives:
i. Technicians must work with in conjunction with the system to provide system notifications of carrier removals.
ii. Iodine PXI’s do not send out a carrier remove message upon carrier insertion.
iii. Pulse PXI’s send out a carrier remove upon carrier removal.
iv. Technicians will be required to take action to produce carrier removed when working with Iodine systems.
v. Technicians will not be required to take action to produce carrier removals when working with Pulse systems.

c. Assumptions:
1. The technician should not have to click a button following physical removal of a carrier.
2. Iodine PXI’s do not send out a carrier remove message upon carrier removal.
3. Pulse PXI’s send out a carrier remove upon carrier removal.
4. Technicians must work with in conjunction with the system to provide system notifications of carrier removals.
5. Iodine PXI’s do not send out a carrier insert message upon carrier removal.
6. Pulse PXI’s send out a carrier remove upon carrier removal.
7. Technicians will be required to take action to produce carrier removed when working with Iodine systems.
8. Technicians will not be required to take action to produce carrier removed when working with Pulse systems.

d. Questions:
1. Is it necessary to mandate clicking a button following carrier removal?
2. Why is there a difference between PXI behaviors based on type?

c. Timing of required system (PXI) maintenance \ Calibration
a. Known – The PXI will require maintenance
b. Alternatives:
i. There will be a fixed period of time down for maintenance.
ii. There will be no maintenance. Chosen for simplicity of working model.
iii. There will be no calibration. Chosen for simplicity of working model.
iv. There will be continuous maintenance.
v. The system will be required to take docking stations offline for maintenance.
vi. The system will be required to take PXIs offline for maintenance.
vii. The PXI will always be up and running 24 hours a day and 7 days a week.
viii. The PXI will be in a continuous state of maintenance.
ix. The PXI will be in a continuous state of calibration.
x. There will exist a calibration recipe.

c. Assumptions:
1. There will be one 24 hour maintenance window each month dedicated to maintenance and calibration.
2. The system will be required to take docking stations offline for maintenance.
3. The system will be required to take PXIs offline for maintenance.
4. The system will be required to take the CPC offline for maintenance.
5. The system will be required to take PXIs offline for calibration.
6. The PXI will always be up and running 24 hours a day and 7 days a week.
d. Questions:
1. What are the requirements for maintenance and calibration?

d. Network timing and availability
a. Known – The will be a server used to facilitate testing of the PXI. The server will require a network connection and maintenance. There will also be a database used to maintain system state and store test results.
b. Alternatives:
i. The network will always be available.
ii. The network will never be available.
iii. The system will need an active connection to the database to start a test.
iv. The system will not need a connection to the database to complete a test once started.
v. The system will use Velocity technology to support the need to complete a test without a database.
vi. Network maintenance will not affect system performance. Best case assumption made for working model simplicity.
vii. The network will always be up and running 24 hours a day and 7 days a week. Best case assumption made for working model simplicity.
c. Assumptions:
1. The system will need an active connection to the database to start a test.
2. The system will not need a connection to the database to complete a test once started.
3. The system will use Velocity technology to support the need to complete a test without a database.
4. Network maintenance will not affect system performance.
5. The network will always be up and running 24 hours a day and 7 days a week.
d. Questions:
1. Is velocity the optimal solution to handling the requirement of no database?
2. What are the system requirements for calibration?
3. What are the system requirements for maintenance?
4. How does the current system handle maintenance and calibration?

e. PXI Operational Considerations
a. Known – The PXI box will be necessary to run a recipe.
b. Alternatives:
i. The PXI will run 24 hours a day and 7 days a week
ii. The CPC will be available during recipe execution
iii. The PXI will be available during recipe execution
c. Assumptions:
1. The PXI will run 24 hours a day and 7 days a week
2. The CPC will be available during recipe execution
3. The PXI will be available during recipe execution
d. Questions:

2. ETS Software – The ETS software layer is defined by the limitations imposed on the system by software run on the control PC (CPC) including:
a. Time to send each command in the recipe
a. Known – As part of the recipe, there will be a maximum amount of time for the system to process each command. Detecting and sending each test command is one portion of the total system processing time.
b. Alternatives:
i. The time it takes for the CPC to detect and send a command is one part of the whole time allowed by the CPC as part of total command processing time.
ii. The time it takes for the CPC to detect and send a command will be less than one second.
iii. 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.
c. Assumptions:
1. The time it takes for the CPC to detect and send a command will be less than one second.
2. 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.

d. Questions:
1. Is the time it takes the CPC to detect and send a command significant to consider as part of the general time estimation for the allowed time to process a command?

b. Time to store recipe results
a. Known – As part of the recipe, there will be a maximum amount of time for the system to process each command. Storing recipe results is one portion of the total system processing time.
b. Alternatives:
i. The time it takes for the CPC to store recipe results is one part of the whole time allowed by the CPC as part of total command processing time.
ii. The time it takes for the CPC to store background measurements will be less than one second.
iii. The time it takes for the CPC to store background measurements will have such a small value it will not be relevant to the general estimate for total command processing time.
iv. The storing of pulse train results will take place on a secondary thread so as not to effect total command processing time.

c. Assumptions:
1. The time it takes for the CPC to store background measurements will be less than one second.
2. 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.
3. The storing of pulse train results will take place on a secondary thread so as not to effect total command processing time.
d. Questions:
1. Is the time it takes the CPC store recipe results significant enough to consider as part of the general time estimation for the allowed time to process a command?

c. Time to display system status
a. Known – The system status display is used to issue carrier insert and carrier remove messages to the system.
b. Alternatives:
1. The technician will perform actions required to facilitate testing in a timely manner.
2. Interaction with the system status display will not affect capacity calculation.
c. Assumptions:
1. As directed by the status display screen, the technician will perform actions required to facilitate testing in a timely manner.
2. Interaction with the system status display will not affect capacity calculation.
d. Questions:
1. Does the system status display effect capacity?

d. Requirements associated with error detection and recovery
a. Known – The system will have some means of detecting a system error.
b. Alternatives:
i. System performance may be estimated using normal flow of execution.
ii. Error detection and correction will not affect system performance.
c. Assumptions:
1. System performance may be estimated using normal flow of execution.
2. Error detection and correction will not affect system performance.
d. Questions:
i. What kind of error correction and detection will the system support?

3. Scheduling - The scheduling layer is defined by the limitations imposed on the system by the scheduling algorithm run within ETS software including:
a. Acceptable time into the future the scheduling algorithm will look relative to the total test time
a. Known – The current software will look as far into the future as necessary to make a reservation.
b. Alternatives:
1. The software will be bound by a finite future reservation window.
2. The software will be bound by a finite present reservation window.
3. The software will not be bound and look as far into the future as necessary to make a reservation. Selected for simplicity.
4. The software will not be bound by start time and look as early into the present as necessary to make a reservation. Selected for simplicity.
c. Assumptions:
1. The software will not be bound by a future window and look as far into the future as necessary to make a reservation.
2. The software will not be bound by lower reservation bound and look as early into the present as necessary to make a reservation.
d. Questions:
1. Would it be worthwhile to define constraints associated with when a reservation may take place with respect to the current time?
2. Would it be worthwhile to maintain a grid of availability in the database? I personally think it would…

ii. Second level scheduling
a. Known – The system does not currently support layered scheduling. To be scheduled against, a docking station must be open and available for the duration of the test.
b. Alternatives:
i. The software will not support layered scheduling – scheduling against docking stations that are full or reserved. Best case selection.
ii. The software will support scheduling into the future, even against docking stations that are currently occupied or reserved.
c. Assumptions:
1. The software will not support layered scheduling – scheduling against docking stations that are full or reserved.
d. Questions:
1. Is there a need for the system to allow scheduling into the future?

b. Allowable start time of carriers within a group
a. Known – Carriers will be scheduled in groups.
b. Alternatives:
i. Carriers will be scheduled with no consideration for of what group they are a part
ii. The scheduled start time of carriers within the same group will be within one hour of each other
c. Assumptions:
1. Carriers will be scheduled with no consideration for of what group they are a part
d. Questions:
1. Are groups considered when scheduling a particular carrier for test?

4. Recipe - The recipe layer is defined by the limitations imposed on the system by the scheduling algorithm run within ETS software including:

a. Time between each command
a. Known – There may be a constant time between commands contained in the recipe.
b. Alternatives:
i. There will be 30 minutes between the scheduled start times of each command.
ii. There will be a variance between the scheduled start times of each command.
c. Assumptions:
1. There will be 30 minutes between the scheduled start times of each command.
d. Questions:
1. Will the time between commands be constant?

b. Total length of the recipe
a. Known – The PXI will run recipes to completion.
b. Alternatives:
i. Recipes run on the PXI will be of variable lengths.
ii. The total execution time of a recipe will not exceed 86 hours in length. Used for SAT recipe. Chosen for simplicity.

c. Assumptions:
1. The total execution time of a recipe will not exceed 86 hours in length.
d. Questions:


5. The PXI command execution layer is defined by the limitations imposed on the system by the time it takes commands to execute software including:
a. Maximum time allotted for apply load command to run
a. Known – The apply load command will be sent to the PXI as part of the recipe run.
b. Alternatives:
i. The total time to execute an apply load command will not exceed 20 seconds. Apply load contains 2 background measurements. Using 10 seconds for execution time of background measurement, 2 * (10) seconds = 20 seconds. Chosen for simplicity.
ii. There will be a variance between time allowed to execute an apply load command.
c. Assumptions:
1. The total time to execute an apply load command will not exceed 20 seconds.
d. Questions:

b. Maximum time allotted for remove load command to run
a. Known – The remove load command will be sent to the PXI as part of the recipe run.
b. Alternatives:
i. The total time to execute a remove load command will not exceed 20 seconds. Remove load contains 2 background measurements. Using 10 seconds for execution time of background measurement, 2 * (10) seconds = 20 seconds. Chosen for simplicity.
ii. There will be a variance between time allowed to execute an apply load command.

c. Assumptions:
1. The total time to execute a remove load command will not exceed 20 seconds.

d. Questions:

c. Maximum time allotted for change load command to run
a. Known – The change load command will be sent to the PXI as part of the recipe run.
b. Alternatives:
i. The total time to execute a change load command will not exceed 30 seconds. Change load contains 3 background measurements. Using 10 seconds for execution time of background measurement, 3 * (10) seconds = 30 seconds. Chosen for simplicity.
ii. There will be a variance between time allowed to execute an apply load command.
c.
d. Assumptions:
1. The total time to execute a change load command will not exceed 30 seconds.
e. Questions:

d. Maximum time allotted for background measurement command to run
a. Known – The background measurement command will be sent to the PXI as part of the recipe run.
b. Alternatives:
i. The total time to execute a background measurement command will not exceed 10 seconds. Chosen for simplicity.
ii. There will be a variance between time allowed to execute an apply load command.

c. Assumptions:
1. The total time to execute background measurement command will not exceed 10 seconds.

d. Questions:

e. Maximum time allotted for pulse command to run
a. Known – The pulse train command will be sent to the PXI as part of the recipe run.
b. Alternatives:
i. The total time to execute a pulse train command will not exceed 2 minutes. Chosen for simplicity.
ii. There will be a variance between times allowed to execute a pulse train command.

c. Assumptions:
1. The total time to execute a pulse train command will not exceed 2 minutes.
d. Questions:

f. Number of commands PXI can simultaneously process
a. Known – The PXI can process one command at a time.
b. Alternatives:
i. PXI can only process one command at a time
ii. PXI can process multiple commands at a time
c. Assumptions:
1. PXI can only process one command at a time
d. Questions:


The next step will be to explicitly define a minimum standard of acceptability, weigh assumptions against each other to eliminate redundancy effectively “normalizing” our list of assumptions and provide rationale for each assumption included in the final list.

Monday, October 20, 2008

Managing Complexity (Capacity 1)

_

There is perhaps no problem I encounter more frequently than that of managing complexity. When working with systems that operate on thousands if not millions of executions, there always exists complexity, both implicit and explicit, and for a system to succeed (meet user requirements) this complexity must be managed.

I was recently asked to determine the capacity of throughput for a certain system. To do so it was necessary to:
  1. Create a list of low level list of functions\assumptions\constraints\requirements (depending on who you're talking with the term will vary).
  2. Create a high level list of functions\assumptions\constraints\ requirements
  3. Create a series of tests to functions\assumptions\constraints\ requirements
  4. Execute tests to determine validity of functions\assumptions\constraints\ requirements
  5. Repeat as required
I thought this project was an excellent example of managing complexity. The process that was used in this case to answer a question about a system of complexity is quite typical, and the pattern can be applied to any system. The idea is to start with an entire system, identify manageable high level components of the system, and break down each high level component to a series of low level components. This cycle of breaking down can take place as many times as necessary until what was once a complicated system, is just finite number of simplicities.

ETS Capacity

For our purposes, capacity can be defined as the function of maximizing output (test data) from input (test procedure). The question then, in this case, is “how effective is our system at generating output?”. The answer can be found by compartmentalizing our system into manageable pieces and identifying how each piece behaves, both individually and with other pieces of the system, to effect the generation of test data. The diagram below displays the high level component breakdown of ETS:



The diagram reveals that the test procedure acts as an input to the system, which executes for the purpose of generating test data. Secondly, the diagram reveals that starting at the point of data generation (PXI command execution), each component is dependent on all of the components contained therein. For example, recipe definition is dependent on PXI command execution, scheduling is dependent on recipe definition and PXI command execution, and each component is dependent on the pieces contained within it. Finally, the diagram reveals that the entire system (input, components, and outputs) is time dependent. That is, time is the single most effective measure of how efficiently the system as a whole (and each of its components) is running. Thus, any investigation into the capacity or efficiency of the system should begin with defining the expected performance of each component with respect to time. Only after assumptions for each component are clearly defined can the assumptions for the system as a whole be realized.