Programmer's ROM - The Computer Language Library

home *** CD-ROM | disk | FTP | other *** search

/ Programmer's ROM - The Computer Language Library / programmersrom.iso / ada / manage / pplanner.doc < prev next >

Wrap

Text File | 1988-05-03 | 141.2 KB | 4,731 lines

User Manual for Project Planning Tools (Tool 38) Prepared for: NAVAL OCEAN SYSTEMS CENTER (NOSC) United States Navy San Diego, CA 92152 Contract number: N66001-85-C-0040 Date: May 31, 1985 Ford Aerospace and Communications Corp. Western Development Laboratories Division 3939 Fabian Way Palo Alto, CA 94303 1. Introduction The purpose of this user's manual is to describe the operation of the planning tools portion of Tool 38, General Management Tools. The manual explains the types and formats of user inputs, how to invoke the various functions provided by the planning tools, and the output produced. To fully appreciate the functions provided, it is helpful to have some knowledge about PERT (Program Evaluation and Review Technique) and how the uncertainty about activity durations may be handled mathematically. Appendix A provides some useful information about these topics. It is also helpful to have some understanding about how project networks are constructed, particularly the activity-on- arc type of network, and the need for dummy activities to model required precedence relationships. Appendix B provides information about these topics. To reduce the discussions in these two appendices to practical uses, Appendix C provides a methodology for the project manager to construct an appropriate network for his particular project. Appendix D has actual examples of screen output. Appendix E contains a detailed list of the correct compilation order. Generally the end user need not worry about this since the source code has already been positioned in the correct order and should be compiled and linked according to the operating instructions described in Section 9 of this user manual. However, this list is valuable for maintenance purposes. 2. Notification of Future Enhancements From time to time Ford Aerospace will enhance this management planning tool. User's wishing to receive notification of such enhancements should send their name and address to: Division Software Technology and Support Ford Aerospace and Communications Corp. Western Development Laboratories Division 3939 Fabian Way Palo Alto, CA 94303 ATTN: Ada[TM] Tools Group Item 0038 Ford Aerospace & May 1985 1 Communications Corporation Project Planning Tools 3. Computer Program System Capabilities 1. Purpose: The purpose of these tools is to provide the project manager with the ability to produce the following types of reports regarding the project: o+ Stochastic critical path, expected schedule and standard deviation. o+ Probability of completion for a given (input) schedule. o+ Schedule for a given probability of completion. o+ Effort in man-days or man-weeks. o+ Average manload; peak manload and time. o+ Direct labor and non-labor costs. o+ Average cost per man-hour for total project labor. o+ Manpower profile data. o+ Network summary metrics for comparing various plans. o+ Gantt Chart graphics. o+ Activity slack metrics. o+ Activity and milestone criticality index. The main input required of the project manager is a description of the project network, in which activity information is associated with arcs of the project network. Detailed descriptions of the required inputs and an explanation of the outputs is given below in the description of the simpert function. __________ TM Ada is a registered trademark of the U.S. Government, Ada Joint Program Office Item 0038 Ford Aerospace & May 1985 2 Communications Corporation Project Planning Tools 2. General Description: There is a top level menu which is invoked according to the operating system on which this tool resides. On the Rolm ADE, for example, it is invoked by the command "x schedule". The top level menu gives the user the choice of four functions, or the option to exit from the top level menu. If the user selects one of the four functions, that function is executed, and control is returned to the top level menu. 3. Functions Performed: The four functions are: o+ create a new file containing project network information; o+ modify a file containing project network information; o+ run the simpert program on a file containing project network information; o+ run a gantt program to produce a gantt chart (horizontal bar chart) based on the output of the simpert program. The gantt program can also be run on a file that was produced directly by the user, via a text editor, provided that the file is in the format expected by the gantt program. The user should be aware of the difference between this simpert (simulation of pert) program and classical pert programs. In the latter case, only a single critical path is dealt with; in this simpert tool, all paths are treated as being potentially critical (or near-critical) and appropriate statistics produced. Appendix A provides more detail about this. 4. Overall Comment Regarding the Four Functions The Rolm compiler on the ADE does not provide a backspace capability to the user during execution of a program in which user inputs from the terminal are to be provided. This is a serious omission from the compiler; the workaround that has been provided in this set of tools is to simulate a backspace by using the back-slash character [\]. There is no way to "escape" the [\], so if the user needs to enter the back-slash character as part of the input line, a different symbol must be chosen to simulate the back space. This can be accomplished easily by changing the value of the variable back_space in package SCREEN_IO to whatever symbol is desired to Item 0038 Ford Aerospace & May 1985 3 Communications Corporation Project Planning Tools simulate a back space. There is also a great deal of error checking and on-line guidance regarding user-supplied inputs. For example, if the user is prompted for the number of a month and types in 13, he will be notified that the correct range is an integer between 1 and 12. On the other hand, this set of tools does not provide deep semantic knowledge regarding dates. The date (dd/mm/yy) 31/02/85 will be treated as March 3, 1985. Ada, unlike Fortran for example, normally requires floating point numbers to be entered with one or more numerals preceding the decimal point. Thus, it is illegal in Ada to enter ".0" as a floating point value of zero. The user should instead enter "0.0". However, to provide a more convenient user interface, this tool provides software that allows the user freedom in entering numerical values for floating point numbers. A floating point zero may be entered as 0, 0., .0, or 0.0 (in addition to 0.00, etc.). This same type of free format holds, of course, for any floating point value. There is also extensive error checking regarding the names of files that the user keys in from the terminal. Appropriate messages are given if required files do not exist, or if existing files are about to be overwritten. In all cases, the user is given the option to respecify the name of the file, or to terminate the program at that point so that given files will not be overwritten. In the event that an unhandled exception is encountered during execution, the tools provide the user with the name of the unit in which the exception was raised. The message urges the user to "notify your system manager" about the error; such a step should not be taken until the user is assured that he has specified all his files correctly, and taken as many steps as possible to provide valid inputs. 5. Function Description of Creating a New File 1. Title of Function: Create. 2. Description of Create: a. Purpose and Use of Create: Create a file containing project activity network information for subsequent use by the simpert program. b. Description of System inputs: The user is prompted for time units (d or w, for days or weeks), the name Item 0038 Ford Aerospace & May 1985 4 Communications Corporation Project Planning Tools of the new file to be created, and a project start date. If the file does not exist it will be created. If the file already exists, the user is warned that it will be overwritten, and is given the opportunity to specify a different file if so desired. Once the user has determined a satisfactory name for the file, the main loop of the program executes. At each iteration the user is prompted for information about a single project activity. The information includes o+ Activity title (maximum of 32 characters) o+ WBS/Activity code (maximum of 8 characters) o+ tail node (integer range 1..9999) o+ head node (integer range 1..9999) o+ optimistic time estimate for activity duration (float) o+ most likely time estimate for activity duration (float) o+ pessimistic time estimate for activity duration (float). The relationship optimistic <= most likely <= pessimistic must be true for the values entered, or the information will be rejected by the tool, and user will be reprompted to enter the information again for that activity. o+ average number of equivalent full-time personnel (float) o+ average cost per man unit of time (day or week) If the activity title is "dummy" (in any configuration of upper or lower case letters), then the user is prompted only for the tail node and the head node. All the other fields are automatically zeroed out. Note that if there is an activity from node 1 to node 2, then 1 is the tail node and 2 is the head node. Prior to invoking the create function, it will be necessary for the user to have some idea of what the project network looks like. As a trivial example, suppose we have a project with two Item 0038 Ford Aerospace & May 1985 5 Communications Corporation Project Planning Tools activities, a1 and a2 which must be done in that order. The user might have represented this information on a piece of paper as a node-arc picture, with three nodes and two arcs. Let us say the three nodes are numbered 5, 10, and 200, and that arc 1 (corresponding to a1) connects node 5 to node 10, and that arc 2 (corresponding to a2) connects node 10 to node 200. The tail node for arc 1 would then be 5, and the head node would be 10. Similarly, the tail node for arc 2 would be 10 and its head node would be 200. The user has freedom in specifying the project network. Notice first that it is not necessary to number the nodes sequentially (i.e., 1,2,3). The user may select any integer values to name the nodes (up to a limit of 9999). Further, the nodes do not have to be labeled in increasing order. It is perfectly acceptable to label the first node of the project network 2000, the next node 100, etc. In addition the user may enter the arc (ie, activity) information into the create program in any order desired; that is, there is no necessity for the user to be concerned with entering the arcs into the create program according to the logical precedence contained in the project network. These freedoms allow the user to choose a labeling method tailored to a specific project. For example, nodes 1 through 999 might be used to contain arcs corresponding to project activities up to the Systems Requirements Review, nodes 1000 through 1999 for project activities up to System Design Review, etc. After the user has entered information for a specific activity (arc) into the create program, he is prompted as to whether he would like to reenter the information for that activity, enter information for the next activity, or exit from the create program. c. Description of Expected Output A file is created, with the name specified by the user, containing the project network information entered by the user. d. Relationship to Other Functions The file is used as input by the simpert function. Item 0038 Ford Aerospace & May 1985 6 Communications Corporation Project Planning Tools 3. Other Usage Instructions for Create The following limitations/restrictions exist in the create program. the maximum number of nodes is 3400; the maximum number of arcs (activities) is 4000; the maximum number of incoming or outgoing arcs to any node is 25; note that the limitation to 3400 nodes does not restrict the user from naming these nodes with any value between 1 and 9999. 6. Function Description of Modify 1. Title of Function - Modify 2. Description of Modify Modify allows the user to add or delete activities to a file already created by the create function. The first prompt is to find out whether the user wishes to add or delete activities. Addition or deletion of activities is the only change that the modify function allows. This is not a serious limitation, since the user is given the option to change the project start date during execution of simpert. The user is then prompted for the name of the file to be modified, and is given a suitable warning message if the file does not exist. If the file does exist, the user is warned it will be overwritten and is given the opportunity to exit from the modify program. After the user has given a satisfactory file name, the modify function goes into add or delete mode as appropriate. If the user wishes to add, he is prompted for the number of activities to be added, and then is prompted for the information about each activity in the same fashion as for the create program. To delete activities, the user is presented with the entire file as it exists, with 12 activities written to the terminal at a time. The user is asked if he wishes to delete any of the 12 activities currently listed at the terminal, and if so, how many. The user then indicates which activities are to be deleted; following this, the next set of 12 activities is written to the screen, and this logic continues until the entire file has been presented to the user. Suppose the user accidentally types 8 rather than 3 activities to be deleted from among a set of 12 activities currently listed on the screen. There is no readily available way to move on to the next set of 12 activities until the user has specified which 8 are to be deleted. However, the user can "trick" the program by reiterating Item 0038 Ford Aerospace & May 1985 7 Communications Corporation Project Planning Tools the same activity to be deleted multiple times until the program determines that 8 activities have been specified for deletion. After the user has completed adding or deleting activities from a given file, he is given the choice of exiting from the modify program, or applying the modify program to a different file. Thus the user can modify multiple files within the same invocation of modify. 7. Function Description of Simpert 1. Purpose and uses of Simpert Read in the file containing project network information that was created by the create or modify program, store the project network internally, and perform multiple traversals of the network to compute the desired output statistics. 2. Description of system inputs: The user is prompted for the following information. a. Number of iterations desired. The answer must be in the range 2..5000, with the default being 1000. The validity of the output data increases with the number of iterations. Hint: As the simpert program executes, the user is kept informed of each iteration by means of an asterisk printing at the terminal. It might be wise to specify a small number of iterations first (eg, 20) to get a feeling for how long each iteration takes. Then rerun the program with an appropriate larger number of iterations. b. The desired probability for output. This number represents the probability that the project will be completed by the ending date computed by the program. The higher the probability, the further out the ending date. The range is 0.05..0.95. c. Name of the file containing activity information (that was created by the create or modify program). d. Name of the file containing holidays for this particular organization. e. The number of workdays per week. The only acceptable answers are 5, 6 or 7, with 5 being the default. Item 0038 Ford Aerospace & May 1985 8 Communications Corporation Project Planning Tools f. The last event for critical path to be returned. An event is equivalent to a node in the project network. The user can specify any specific node number, and one of the output reports will contain the critical path from the starting node to the specified node. The default is the sink node for the project. If the user types a nonexistent node number, the program will default to the sink node. g. Title for output reports. The user may specify a title, which then appears as header information in all the output reports. h. Whether the user wishes to change the project start date that was read in from the activity file. If so, the user is prompted for the new start date. i. Required completion date. The user is prompted as to whether the project must complete by a certain date; if the user types "yes", he is further prompted for the exact date by which the project must complete. j. Whether the user wishes to see part of the network summary. If the user types "yes", a subset of the output reports that have been generated is displayed to the screen. Generally only those reports that fit on a dumb terminal screen without wraparound will be so displayed. 3. Description of expected outputs and results. The output files created by Simpert are explained below in this section. The user is warned at the beginning of the program whether files with these names already exist; if they do exist, they will be overwritten by simpert. However, the user is given the option as part of the warning message to abort the simpert program prior to overwriting these files. This tool also utilizes a random number generator, and therefore the results of two different runs may vary even if they have the identical input files. If the user requires a given input to produce the same output all the time, and not be dependent upon the random number generator, then the program should be modified to read random numbers from a file. There are only two place in the tool which utilize the random number generator. Both of them occur in function TRIANGULAR_DISTRIBUTION, which occurs in the declaration part of procedure PROCESS. Both occurrences are of the form NUMERIC_PRIMITIVES.RAN. Item 0038 Ford Aerospace & May 1985 9 Communications Corporation Project Planning Tools a. act.tem The output file act.tem provides information about each activity. The "Days Strt" column represents the project start day for that activity without taking weekends or holidays into account. For example, an entry of 3 in this column means that the activity begins on the third available workday into the project. The "Start Date" column, however, does take into account weekends and holidays. The "Days Span" column represents the number of days in which the activity is occurring, ie, if an activity takes 3.4 days, it will span 4 project days. Labor hours is always a multiple of 8. The "Totl Slck" and "Free Slck" columns have the following meanings: Total slack is the maximum number of working days a given activity may be delayed without affecting project completion. Free slack is the maximum number of working days a given activity may be delayed without affecting any other activity, whether or not project completion is affected. The "Crit Indx" column represents the probability that the activity was on a critical path over all the iterations. The "Rem" column is the number of time units of the activity span that are left to complete the activity counting from the "Date Today" printed in the upper right hand corner. b. node.tem The node.tem file presents the information associated with each node of the network. The "Expected" column represents the expected (50% probability) duration for all the input activities to complete. The "Criticality Index" is the probability of the node being on the critical path. The column labeled with the user-supplied probability, eg, "90%", represents the given probability of completing all the input activities to that node by the time indicated. If the user supplies a probability of 50%, this column will be identical to the "Expected" column. c. barin.tem The barin.tem file presents all the non-dummy activities, with their associated project start and stop days (not counting weekends or holidays) and an indication of whether the activity is critical or Item 0038 Ford Aerospace & May 1985 10 Communications Corporation Project Planning Tools not. This file is the standard input file to the gantt function. d. tout.tem The output file tout.tem contains the simpert global report. On the first page is a list of the critical path activities and the cumulative time/date of the completion, based on a given probability. The second page of tout.tem contains a summary of the total schedule as a random variable. The most useful result is the probability of completing the project by the required date (user input). The project effort and cost estimates are also summarized. The final page is a summary of network metrics. These metrics are useful in comparing one network plan with another. Most of the metrics are straightforward however a few need some explanation: i. Network Complexity is a measure of network cross-connectedness. It is calculated using (#arcs - #nodes)/#arcs, and falls between 0 and 1 when #arcs is greater than #nodes. ii. Stochastic Complexity is another measure of network complexity, measuring the degree of occurrence of near critical paths. This number falls between 0 and 1, where 0 represents the simple network with no near critical paths and 1 represents the network with the maximum cross-connectedness (that is, Network Complexity approaching 1) with all paths critical. In a comparison of two plans, the lower complexity factor is more desirable. The assumption is that there is lower risk with lower complexity. iii. Stochastic Density is a summary measure of the lack of slack in a project schedule. It is calculated using A/(A+B), where A is the sum of all expected durations and B is the sum of all free slack, and falls between 0 and 1. 0 represents no duration (infinite slack) and 1 represents no project slack. When comparing two or more plans, the lower the density, the easier it is for management to shorten project schedules or level manpower. Item 0038 Ford Aerospace & May 1985 11 Communications Corporation Project Planning Tools iv. manpower.tem The manpower data is the x,y ordered pairs where x = days, and y = average staff (equivalent heads). e. Relationship to other functions. The activity file (input) was created by the create or modify program. The barin.tem output report is used as input by gantt to produce a bar chart. f. Summary of simpert operation: First the activity file is read and stored internally. The project network is then checked for consistency, meaning that it must not contain any cycles, and that there is exactly one starting node and exactly one ending node. If these consistency conditions are not met, the user is given a message explaining which conditions are not met, and the program is then terminated (bringing the user back to the top level menu program). If the project network is consistent, simpert then runs through a single deterministic traversal of the project graph to compute deterministic starting and ending times of the activities. The length of each activity is simply the mean of the three point estimate for the deterministic run. The next step is to perform N iterations of a stochastic traversal of the project network, where N is the number of iterations supplied by the user. At each iteration, the duration of each activity is computed by drawing randomly from a triangular distribution based on the three point estimate. The next step is to compute needed statistics, such as slack time, based on the full set of traversals of the project network. The final step is printing out the reports. 4. Usage Instructions for Simpert The same limitations for the project network size apply to simpert as to create and to modify, namely: the maximum number of nodes is 3400; the maximum number of arcs (activities) is 4000; the maximum number of incoming or outgoing arcs to any node is 25; note that the limitation Item 0038 Ford Aerospace & May 1985 12 Communications Corporation Project Planning Tools to 3400 nodes does not restrict the user from naming these nodes with any value between 1 and 9999. The holiday file must be in the format dd/mm/yy with one entry to a line, starting in column 1. The dates must be in increasing order. There is a limitation that only the first 100 entries of the holiday file will be read in. Therefore it is in the user's interest to prune down the holiday file to only those holidays that span the duration of the project. The slash symbol "/" separating the days, months, and years may be replace by any other separator symbol, including blank. 8. Function Description of Gantt 1. Purpose of Gantt: Produce a bar chart based on the file barin.tem that was produced by pert. Gantt can also operate on a file that was created directly by the user (or a barin.tem file that was modified by the user with a text editor). If the user wishes to use gantt on a file other than barin.tem, the following points are important. The number of activities on line 10 of the file is the driver regarding how many activities are read. The user will recognize the correct line in the file since there is a comment on the right side of the line saying "Number of activities". In particular, if the number is too small, then not all the activities will be read, and if it is too big, then the program will attempt to read past the end of file and abort. It is suggested that if the user wishes to apply gantt to user- created files, he should first create a barin.tem file and use its format as a guideline. There are comments in the barin.tem file that will help the user. 2. Inputs to Gantt: First the user is prompted for a title for the output report. This title will appear as header information in all the output pages produced. Next the user is prompted for the names of the input file (eg, barin.tem), the holiday file, and the name of the output file to be produced by Gantt. Warning: if the user specifies existing files for the input or holiday file which are not in the correct format, then the program will abort with a large number of error messages. Item 0038 Ford Aerospace & May 1985 13 Communications Corporation Project Planning Tools Since Gantt may produce multiple pages of output, the user is also given the option to limit the amount of printout to a specified calendar interval. This option is presented during execution of gantt as a prompt to the user; the four choices are to leave the start and stop dates alone (ie, use those from the input file), to modify the start date, to modify the stop date, or to modify both the start and stop dates. If the user indicates that one or both dates is to be modified, he is then prompted for the new date. A new start date earlier than the project start date will not affect the project start date for printout purposes. Likewise a project stop date beyond the normal project stop date will not affect the project stop date for printout purposes. However, if a new project start date earlier than the normal project start date is specified by the user, and the user also specifies a new project stop date, then the interval of the printout will be the time period between the newly specified start and stop dates. If the user does limit the amount of printout, then the same data will be printed on the pages that are produced as would have been printed on those pages without any limitation on the amount of printout. 3. Expected outputs and results of Gantt: An output file is created containing the bar chart version of the data in the input file. The following symbols are used in the bar chart. "H" represents a holiday. "^" represents the start or end date of an activity. "-" represents the days in which a noncritical activity is proceeding. "=" represents the days in which a critical activity is proceeding. "*" represents days during the very first week of the project which are available, but not used. For example, if a project begins on Wednesday, and the preceding two days are not holidays, then there will be "*" in the Monday and Tuesday positions of the first week. Calendar data (day, month, year) is printed at the top of every output page, for each of the 13 one week time periods on that page. This calendar data corresponds to the Monday of the given week. 4. Relationship to other functions. Gantt is used essentially in stand-alone mode, although the barin.tem file created by simpert might be thought of as the standard input. Item 0038 Ford Aerospace & May 1985 14 Communications Corporation Project Planning Tools 5. Summary of function operation: The first step is to read in the activity file and the holiday file. Next the project start and stop dates are determined, either from the activity file or from user supplied inputs from the terminal. If the desired project start date falls on a weekend or holiday, gantt automatically bumps the start date to the first available workday. The main loop of the program is to cycle over all time periods, with 13 weeks (91 days) printed per time period. Each activity is checked to see if it overlaps with the current time period, and if so, to print it appropriately, If there is no overlap, the activity name is printed, but no other output symbols are printed for that time period. 6. Usage instructions for Gantt: The format and restrictions on the holiday file given above for simpert also apply to Gantt. There is a restriction on the number of activities to 500. This can be changed easily by the user by changing the declaration of the variable MAX_NUM_ACTIVITIES in procedure out_gantt to the desired value and recompiling. The output of Gantt is always in units of days. If the time unit of days was specified in the barin.tem file, then Gantt output will be accurate to the day. If the time unit of weeks was specified, then Gantt output will be accurate to the week. There is a restriction to 999 working days for a given project. This limit can be increased by the user by changing the declarations of PROJECT_DAYS_FOOTER and PROJECT_DAYS in the procedure out_gantt. Gantt relies on the assumption that holidays never fall on "weekends". The notion of weekend depends on whether the number of days worked per week is 5, 6, or 7. If 7, then there is no such thing as a weekend, and holidays may occur at any time. If 6, then Sunday is the weekend day. If 5, then Saturday and Sunday are the weekend days. 9. Operating Instructions The following instructions may be utilized to compile, link, and execute the tools described above. Item 0038 Ford Aerospace & May 1985 15 Communications Corporation Project Planning Tools ada sim_util ada/main schedule ada newfile ada modify ada simpert ada out_gantt adalink/multi_task/mtop=250/main_stack_size=40000/root_stack_size=500000 schedule To execute the tools, type "x schedule", which will bring the user to the top level menu, from which the four tools may be invoked. Item 0038 Ford Aerospace & May 1985 16 Communications Corporation Project Planning Tools 10. Appendix A - Motivation and Background for PERT Tools As the aerospace industry continues to improve productivity by Building more sophistication into software based tools, one finds several areas overlooked. One of the more important, in terms of being a significant driver of cost and schedule, is project management. For example, in software development it has been shown that`poor management can increase software costs more rapidly than any other factor' Boehm. This can occur for a number of reasons, but the list usually includes: o+ Poor cost/schedule estimation o+ Lack of effective planning o+ Poor resource allocation o+ Little or no risk analysis o+ Lack of project control o+ Ineffective use of overtime o+ No historical data from which to learn PERT (Program Evaluation and Review Technique) was developed in the 1950s and is typically used today to help management with some of the above problems. The technique is to organize the project activities, on the basis of their precedent relationship, in a network (see Figure 1.1). Each arc of the network represents a project activity and is assigned a duration. Each node represents the event in time when (1) all inbound activities are completed and (2) all outbound activities can be started. The concept is simply that an activity can not start until all predecessor activities are completed. In other words, the time associated with any node is the maximum of the cumulative times of all paths into that node. A triple of the form (i,j,name) represents an arc from node i to node j representing the activity "name". (1,14,Manager/clerk) (1,19,CM) (1,28,Req) (1,4,Dev Env) __________ 1. Boehm, B.W., `Software Engineering Economics', Englewood Cliffs, Prentice-Hall, New Jersey 07632, 1981. Item 0038 Ford Aerospace & May 1985 17 Communications Corporation Project Planning Tools (1,14,QA) (28,19,Outline Manual) (28,29,Baseline) (29,19,ADL) (19,4,Review 1) (4,16,Test plan) (4,16,Code/test) (4,5,Draft manual) (5,16,dummy) (5,15,troff manual) (16,15,Int/test) (15,14,Tech Rep) (15,21,Review 2) (21,14,Install) Figure 1.1 Because aerospace projects are based on new technologies, the estimation of an activity duration is subject to a significant degree of uncertainty. To include this uncertainty in the network model, each activity duration is represented as a continuous random variable. The density function for the random variable is assumed to be one of many standard unimodal functions (i.e., triangular, beta, etc.) that is fitted by a three point time estimate. The expected value and variance of the activity duration are computed by an exact or approximation formula. One method for computing the total project schedule as a random variable is the classical PERT approach. This method initially represents each activity duration by its expected value. Equating time and length, the critical path is simply the longest deterministic path through the network. Then the duration of each activity on this path is considered as an independent random variable. The expected value of the project schedule is approximated by the longest path. The variance in the total schedule is approximated by the sum of the activity variances on the critical path. As the sum of independent random variables, this total project schedule is assumed to be normally distributed. The main drawback of this classical technique is that it ignores all activities not on the critical path and the associated stochastic nature of their completion times. This is of no great concern if the critical path is much longer than all sub-critical paths. Unfortunately, this is usually not the case. From an optimal resource allocation or minimum schedule strategy, a network plan with only a single long critical path is Item 0038 Ford Aerospace & May 1985 18 Communications Corporation Project Planning Tools undesirable. Current management strategies stress not only the idea of increasing activity parallelism, but also the scheduling (or procrastinating) of activities (by their slack) to begin later than their earliest start time. These strategies increase the likelihood that sub-critical paths become near-critical. Because of the stochastic properties of these durations, the total project schedule increases. One simple and accurate method for measuring the stochastic effect of all network activities on the total project schedule is the Monte Carlo simulation. The basic concept is to randomly draw a time from each of the activity distributions, generate a total project time as in a deterministic model, and repeat the process a sufficiently large number of times in order to compute a reliable sample mean and variance. Item 0038 Ford Aerospace & May 1985 19 Communications Corporation Project Planning Tools 11. Appendix B - Activity-on-Arc Project Networks The central concept of SIMPERT is the arrow or network diagram used to represent a project schedule as in Figure 1.1. In order to produce the network diagram, a list of project activities that is as complete as possible must be available to work from. Putting the activity information in network form forces the identification of the precedent relationships between the activities. Each arc of a network diagram represents a project activity or partial activity, and each node represents the completion of the incoming activities and the earliest start of the outgoing activities. Each arc has a set of input parameters (activity duration, staffing,...) associated with it. Implicit in the network is the precedent relationship between activities; these can be identified by asking the following questions for a given activity, say A: 1. What activities must be completed immediately before A can start? 2. What activities cannot start until A is completed? The following example from [Whitehouse 1983] illustrates representing activities that have various precedent relationships with a network diagram. Consider a project for which the analysis has resulted in the definition of five activities A, B, C, D, and E with the following precedent relationships between the activities: 1. A and B can be started simultaneously. 2. C can be started only when A is completed. 3. D can be started only when B is completed. 4. Both C and D must be complete before E may be started. The following network diagram represents the five-activity project with the above precedent relationships. (1,2,A) (1,3,B) (2,4,C) (3,4,D) (4,5,E) Item 0038 Ford Aerospace & May 1985 20 Communications Corporation Project Planning Tools Figure 2.1 Suppose the precedent relationships of the above example are modified to: 1. A and B can be started simultaneously. 2. C can be started only when A is completed. 3. D can be started only when A and B are completed. (*) 4. Both C and D must be complete before E may be started. The network shown in Figure 2.1 is no longer appropriate, it violates the restriction that activity D be dependent upon activity A. We might consider redrawing the network as shown in Figure 2.2, but this is incorrect. The Figure 2.2 network implies that activity C is dependent upon activity B which is not the case. Item 0038 Ford Aerospace & May 1985 21 Communications Corporation Project Planning Tools (1,2,A) (1,2,B) (2,3,C) (2,3,D) (3,4,E) Figure 2.2 To display the relationship introduced in (*), it will be necessary to introduce another type of activity called a dummy activity. A dummy activity has a duration and staff of zero. If we introduce a dummy as shown in Figure 2.3, the new precedent relationship can be modeled. __________ 2. Gary E. Whitehouse, Systems Analysis and Design Using Network Techniques (Englewood Cliffs, N.J.: Prentice- Hall, Inc.), pp. 32-33. Item 0038 Ford Aerospace & May 1985 22 Communications Corporation Project Planning Tools (1,2,A) (1,3,B) (2,3,dummy) (2,4,C) (3,4,D) (4,5,E) Figure 2.3 The Figure 2.3 network indicates that activity D cannot start until both the dummy activity and activity B are completed. But the dummy must wait for activity A to be completed, so activity D is dependent on activities A and B. Sometimes it is useful to represent an activity by more than one arc. For example, suppose an activity, A, can start when another, B, is partially completed. Activity B can be represented by two arcs, B1 and B2, where completion of B1 is sufficient to start activity A. The network can be drawn as in Figure 2.4. Item 0038 Ford Aerospace & May 1985 23 Communications Corporation Project Planning Tools (1,2,B1) (2,3,B2) (2,4,A) Figure 2.4 Another case when an activity can be divided into multiple arcs is when there is a difference in any of the input parameters. For example, suppose activity B needs only 2 people for the first half of its schedule and 10 people for the second half. As before, B could be divided into B1 and B2 with each having its own set of input parameters. Item 0038 Ford Aerospace & May 1985 24 Communications Corporation Project Planning Tools 12. Appendix C - Methodology for Creating Project Network The following are the steps typically used in preparing for and executing simpert: o+ Create a list of activities at the upper level, (e.g., Design XXX CPCI). o+ Interview experts or responsible manager/engineer for estimates of 3 point duration, staff, and average labor rate for each activity. o+ Sketch activity-on-arc network. Assign node numbers at each node. Recommend using a range of numbers for various phases (e.g., 1000-1999 for Design phase) o+ Tabulate network activity parameters on input form (Appendix D) o+ Enter data into system with file generator routines. o+ Execute simpert and debug input data. o+ Break down activities into more detail (i.e., sub- networks). o+ Final run should include (1) a 50% probability schedule for internal tasking, and (2) a 90-95% probability schedule for customer interface. Item 0038 Ford Aerospace & May 1985 25 Communications Corporation Project Planning Tools 13. Appendix D - Sample Executions of the Ada Tools (Recall that the back-slash character, "\", represents a backspace). S D 14 1 85 CODE ACTIVITY TITLE TAIL HEAD OPTM M.L. PESS STAF $RATE/ODC XXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXX XXXX XXX.X XXX.X XXX.X XX.X XXXXXXX.X B907QAAA QA 1 14 1.0 1.0 1.0 0.2 185.0 B907E8PA Draft manual 4 5 13.0 15.0 30.0 1.0 185.0 B907E8TA Test plan 4 16 15.0 20.0 28.0 1.0 120.0 B907E8PA troff manual 5 15 5.0 8.0 10.0 1.0 120.0 DUMMY 5 16 0.0 0.0 0.0 0.0 0.0 B907E8PA Review 1 19 4 1.0 2.0 3.0 3.5 185.0 B907E8PA Review 2 15 21 1.0 2.0 3.0 3.5 185.0 B907QACM CM 1 19 12.0 18.0 24.0 1.0 120.0 B907IDAA Dev env 1 4 8.0 10.0 12.0 1.0 150.0 B907QASA Tech Rep 15 14 5.0 5.0 8.0 1.0 240.0 B907AAAA Admin 1 14 1.0 1.0 1.0 0.1 220.0 B907E8RA Req 1 28 2.0 2.0 3.0 1.5 220.0 B907E8FA Baseline 28 29 4.0 6.0 10.0 1.0 185.0 B907E8DA ADL 29 19 25.0 34.0 45.0 1.2 160.0 B907E8CA Code and test 4 16 20.0 22.0 35.0 1.0 130.0 B907E8TA Int and test 16 15 5.0 8.0 15.0 1.0 120.0 B907E8PA Outline manual 28 19 2.0 3.0 4.0 1.0 185.0 B907IAAA Install 21 14 5.0 8.0 10.0 1.5 185.0 Item 0038 Ford Aerospace May 1985 26 Communications Corporation Project Scheduling Tools ACTIVITY REPORT SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 30 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 Labor Cost Days Days Sd Totl Free Crit Start Finish WBS Code Activity Title Tail Head Staf Hours ($100) Strt Span Dv Slck Slck Indx Date Rem Date ________ ________________________________ ____ ____ ____ _____ ______ ____ ____ __ ____ ____ ____ _________ ___ _________ Data sorted on ---> Expected Finish Date B907QAAA QA 1 14 0.2 0 1 1 2 1 89 89 0.00 14 JAN 85 0 15 JAN 85 B907AAAA Admin 1 14 0.1 0 0 1 2 1 89 89 0.00 14 JAN 85 0 15 JAN 85 B907E8RA Req 1 28 1.5 48 10 1 3 1 0 0 1.00 14 JAN 85 0 16 JAN 85 B907E8PA Outline manual 28 19 1.0 24 6 4 3 1 38 38 0.00 17 JAN 85 0 21 JAN 85 B907E8FA Baseline 28 29 1.0 48 11 4 6 2 0 0 1.00 17 JAN 85 0 24 JAN 85 B907IDAA Dev env 1 4 1.0 88 17 1 11 1 36 36 0.00 14 JAN 85 0 28 JAN 85 B907QACM CM 1 19 1.0 152 23 1 19 3 26 26 0.00 14 JAN 85 0 7 FEB 85 B907E8DA ADL 29 19 1.2 272 65 10 34 5 0 0 1.00 25 JAN 85 0 13 MAR 85 B907E8PA Review 1 19 4 3.5 64 13 44 2 1 0 0 1.00 14 MAR 85 0 15 MAR 85 B907E8PA Draft manual 4 5 1.0 160 37 46 20 4 6 0 0.37 18 MAR 85 0 15 APR 85 B907E8TA Test plan 4 16 1.0 168 25 46 21 3 5 5 0.18 18 MAR 85 0 16 APR 85 B907E8CA Code and test 4 16 1.0 200 33 46 25 4 0 0 0.45 18 MAR 85 0 22 APR 85 B907E8PA troff manual 5 15 1.0 64 10 66 8 2 8 8 0.10 16 APR 85 0 25 APR 85 B907E8TA Int and test 16 15 1.0 88 13 71 11 3 0 0 0.90 23 APR 85 0 7 MAY 85 B907E8PA Review 2 15 21 3.5 64 13 82 2 1 0 0 1.00 8 MAY 85 0 9 MAY 85 B907QASA Tech Rep 15 14 1.0 48 14 82 6 1 4 4 0.00 8 MAY 85 0 15 MAY 85 B907IAAA Install 21 14 1.5 112 19 84 7 2 0 0 1.00 10 MAY 85 0 20 MAY 85 Item 0038 Ford Aerospace & May 1985 27 Communications Corporation Project Scheduling Tools Item 0038 Ford Aerospace May 1985 28 Communications Corporation Project Scheduling Tools ACTIVITY REPORT SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 30 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 Labor Cost Days Days Sd Totl Free Crit Start Finish WBS Code Activity Title Tail Head Staf Hours ($100) Strt Span Dv Slck Slck Indx Date Rem Date ________ ________________________________ ____ ____ ____ _____ ______ ____ ____ __ ____ ____ ____ _________ ___ _________ Data sorted on ---> Expected Finish Date B907QAAA QA 1 14 0.2 0 1 1 2 1 89 89 0.00 14 JAN 85 0 15 JAN 85 B907AAAA Admin 1 14 0.1 0 0 1 2 1 89 89 0.00 14 JAN 85 0 15 JAN 85 B907E8RA Req 1 28 1.5 48 10 1 3 1 0 0 1.00 14 JAN 85 0 16 JAN 85 B907E8PA Outline manual 28 19 1.0 24 6 4 3 1 38 38 0.00 17 JAN 85 0 21 JAN 85 B907E8FA Baseline 28 29 1.0 48 11 4 6 2 0 0 1.00 17 JAN 85 0 24 JAN 85 B907IDAA Dev env 1 4 1.0 88 17 1 11 1 36 36 0.00 14 JAN 85 0 28 JAN 85 B907QACM CM 1 19 1.0 152 23 1 19 3 26 26 0.00 14 JAN 85 0 7 FEB 85 B907E8DA ADL 29 19 1.2 272 65 10 34 5 0 0 1.00 25 JAN 85 0 13 MAR 85 B907E8PA Review 1 19 4 3.5 64 13 44 2 1 0 0 1.00 14 MAR 85 0 15 MAR 85 B907E8PA Draft manual 4 5 1.0 160 37 46 20 4 6 0 0.37 18 MAR 85 0 15 APR 85 B907E8TA Test plan 4 16 1.0 168 25 46 21 3 5 5 0.18 18 MAR 85 0 16 APR 85 B907E8CA Code and test 4 16 1.0 200 33 46 25 4 0 0 0.45 18 MAR 85 0 22 APR 85 B907E8PA troff manual 5 15 1.0 64 10 66 8 2 8 8 0.10 16 APR 85 0 25 APR 85 B907E8TA Int and test 16 15 1.0 88 13 71 11 3 0 0 0.90 23 APR 85 0 7 MAY 85 B907E8PA Review 2 15 21 3.5 64 13 82 2 1 0 0 1.00 8 MAY 85 0 9 MAY 85 B907QASA Tech Rep 15 14 1.0 48 14 82 6 1 4 4 0.00 8 MAY 85 0 15 MAY 85 B907IAAA Install 21 14 1.5 112 19 84 7 2 0 0 1.00 10 MAY 85 0 20 MAY 85 Item 0038 Ford Aerospace & May 1985 29 Communications Corporation Project Scheduling Tools GANTT INPUT FILE SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 34 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 Project2 Title input.data SIMPERT input file 17 Number of activities 89.63 Total project schedule D 5 D = days, W = weeks, # = days/weeks 0.50 Probability for time 14 1 85 Project Start date {dd/mm/yy} WBS Code Activity Title Crit Tail Head Staff Start Stop ________ ________________________________ ____ ____ ____ _____ _____ ____ Data sorted on ---> Finish Time B907QAAA QA 1 14 0 1 2 B907AAAA Admin 1 14 0 1 2 B907E8RA Req C 1 28 2 1 3 B907E8PA Outline manual 28 19 1 4 6 B907E8FA Baseline C 28 29 1 4 9 B907IDAA Dev env 1 4 1 1 11 B907QACM CM 1 19 1 1 19 B907E8DA ADL C 29 19 1 10 43 B907E8PA Review 1 C 19 4 4 44 45 B907E8PA Draft manual C 4 5 1 46 65 B907E8TA Test plan 4 16 1 46 66 B907E8CA Code and test C 4 16 1 46 70 B907E8PA troff manual 5 15 1 66 73 B907E8TA Int and test C 16 15 1 71 81 B907E8PA Review 2 C 15 21 4 82 83 B907QASA Tech Rep 15 14 1 82 87 B907IAAA Install C 21 14 2 84 90 Item 0038 Ford Aerospace May 1985 30 Communications Corporation Project Scheduling Tools SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 39 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 Working Days Manpower ------------ -------- 1 3.80 2 3.80 3 3.50 4 4.00 5 4.00 6 4.00 7 3.00 8 3.00 9 3.00 10 3.20 11 3.20 12 2.20 13 2.20 14 2.20 15 2.20 16 2.20 17 2.20 18 2.20 19 2.20 20 1.20 21 1.20 22 1.20 23 1.20 24 1.20 25 1.20 26 1.20 27 1.20 28 1.20 29 1.20 30 1.20 31 1.20 32 1.20 33 1.20 Item 0038 Ford Aerospace & May 1985 31 Communications Corporation Project Scheduling Tools 34 1.20 35 1.20 36 1.20 37 1.20 38 1.20 39 1.20 40 1.20 41 1.20 42 1.20 43 1.20 44 3.50 45 3.50 46 3.00 47 3.00 48 3.00 49 3.00 50 3.00 51 3.00 52 3.00 53 3.00 54 3.00 55 3.00 56 3.00 57 3.00 58 3.00 59 3.00 60 3.00 61 3.00 62 3.00 63 3.00 64 3.00 65 3.00 66 3.00 67 2.00 68 2.00 69 2.00 70 2.00 71 2.00 72 2.00 73 2.00 74 1.00 75 1.00 76 1.00 77 1.00 78 1.00 79 1.00 80 1.00 81 1.00 82 4.50 83 4.50 84 2.50 Item 0038 Ford Aerospace May 1985 32 Communications Corporation Project Scheduling Tools 85 2.50 86 2.50 87 2.50 88 1.50 89 1.50 90 1.50 Item 0038 Ford Aerospace & May 1985 33 Communications Corporation Project Scheduling Tools NODE_REPORT SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 27 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 Number of Nodes: 10 Node Expected Time/Date Standard Dev. 50% Time/Date Criticality Index ---- -------- --------- ------------- ------ --------- ----------------- Data sorted on ---> network topology 1 0.00 14 JAN 85 0.00 0.00 14 JAN 85 1.00 28 2.34 16 JAN 85 0.19 2.34 16 JAN 85 1.00 29 8.49 24 JAN 85 1.03 8.49 24 JAN 85 1.00 19 42.65 13 MAR 85 3.72 42.65 13 MAR 85 1.00 4 44.57 15 MAR 85 3.72 44.57 15 MAR 85 1.00 5 64.72 15 APR 85 4.62 64.72 15 APR 85 0.37 16 69.83 22 APR 85 5.43 69.83 22 APR 85 0.90 15 80.00 7 MAY 85 5.42 80.00 7 MAY 85 1.00 21 82.04 9 MAY 85 5.54 82.04 9 MAY 85 1.00 14 89.63 20 MAY 85 5.51 89.63 20 MAY 85 1.00 Item 0038 Ford Aerospace May 1985 34 Communications Corporation Project Scheduling Tools SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 36 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 STOCHASTIC CRITICAL PATH: WBS Code Activity Title Tail Head Finish Time Finish Date ________________________________________________________________________________ B907IAAA Install 21 14 89.63 20 MAY 85 B907E8PA Review 2 15 21 82.04 9 MAY 85 B907E8TA Int and test 16 15 80.00 7 MAY 85 B907E8CA Code and test 4 16 69.83 22 APR 85 B907E8PA Review 1 19 4 44.57 15 MAR 85 B907E8DA ADL 29 19 42.65 13 MAR 85 B907E8FA Baseline 28 29 8.49 24 JAN 85 B907E8RA Req 1 28 2.34 16 JAN 85 Item 0038 Ford Aerospace & May 1985 35 Communications Corporation Project Scheduling Tools SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 37 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 TOTAL SCHEDULE AND ASSOCIATED RISK ---------------------------------- 50% Probability Completion Time/Date = 89.63 20 MAY 85 Optimistic Completion Time/Date = 73.10 26 APR 85 Expected Completion Time/Date = 89.63 20 MAY 85 Pessimistic Completion Time/Date = 106.16 13 JUN 85 Standard Deviation = 5.51 Required Schedule with probability of completion by scheduled date = 0.53 20 MAY 85 EFFORT/MANPOWER ESTIMATES ------------------------- Total Effort (in man_days) = 200.40 Average Manload = 2.24 Peak Manload Time/Date = 82.00 8 MAY 85 Peak Manload = 4.50 COST ESTIMATES -------------- Direct Labor Cost (in K $) = 30.95 Other Direct Cost (in K $) = 0.00 Item 0038 Ford Aerospace May 1985 36 Communications Corporation Project Scheduling Tools Total Cost (in K $) = 30.95 Average Cost per Man-Hour(in $) = 19.31 Item 0038 Ford Aerospace & May 1985 37 Communications Corporation Project Scheduling Tools SIMPERT Version 1.0 Date Today: 17 JUN 85 Time: 16: 25: 38 Title : Project2 Estimate file : input.data Date Project Start: 14 JAN 85 Probability : 50% Iterations : 10 Conf Interval : 2.9 NETWORK SUMMARY METRICS ----------------------- Number of ARCS [excludes dummies] = 17 Number of NODES = 10 MAX Number of ARCS in any path [includes dummies] = 9 MAX Number of Parallel Paths = 5 MAX occurs first on 14 JAN 85 Network Complexity = 0.44 Stochastic Complexity = 0.00 Total Stochastic Free Slack = 294.67 Sum of all activity durations = 182.00 MAX arc : ADL MAX duration = 34.00 Average Duration [no dummies] = 10.71 Stochastic Density = 0.38 Average Time Width = 2.03 Note: (1) SIMPERT global report found in file -----------------> tout.tem (2) Activity report -------------------------------------> act.tem (3) Node report -----------------------------------------> node.tem (4) Data points for manpower curve temporarily in file --> manpower.tem Item 0038 Ford Aerospace May 1985 38 Communications Corporation Project Scheduling Tools (5) Input data for Gantt Chart are found in file --------> barin.tem (6) RENAME any of the files.tem if you want to save them Item 0038 Ford Aerospace May 1985 39 Communications Corporation Project Scheduling Tools GANTT CHART Page# : 1 Input File : barin.tem Date Today : 17 JUN 1985 Project Start Date (dd/mm/yy) : 14 1 85 Probability of Completion: : 0.50 Project Title : Gantt chart for Project2 Legend : H --> holiday - --> non-critical activity = --> critical activity ^ --> project start or stop * --> day(s) of first week not used +---------------------------------------------------------------------------------------------------------------------------+ ! MONTH ! 1 85 ! 2 ! 3 ! 4 ! ! DATE !14 !21 !28 ! 4 !11 !18 !25 ! 4 !11 !18 !25 ! 1 ! 8 ! +--------------------------------!------!------!------!------!------!------!------!------!------!------!------!------!------+ !QA !^^ !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Admin !^^ !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Req !^=^ !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Outline manual ! ^-!!^ !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Baseline ! ^=!!===^ !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Dev env !^----!!-----!!^ !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !CM !^----!!-----!!-----!!---^ !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !ADL ! !! ^!!=====!!=====!!=====!!=====!!=====!!=====!!==^ !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Review 1 ! !! !! !! !! !! !! !! !! ^^!! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Draft manual ! !! !! !! !! !! !! !! !! !!^====!!=====!!====H!!=====!! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Test plan ! !! !! !! !! !! !! !! !! !!^----!!-----!!----H!!-----!! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Code and test ! !! !! !! !! !! !! !! !! !!^====!!=====!!====H!!=====!! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !troff manual ! !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Int and test ! !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Review 2 ! !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Tech Rep ! !! !! !! !! !! !! !! !! !! !! !! H!! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Install ! !! !! !! !! !! !! !! !! !! !! !! H!! !! +--------------------------------!------!------!------!------!------!------!------!------!------!------!------!------!------+ ! WORK DAYS INTO EFFORT ! 1 ! 6 ! 11 ! 16 ! 21 ! 26 ! 31 ! 36 ! 41 ! 46 ! 51 ! 56 ! 60 ! +---------------------------------------------------------------------------------------------------------------------------+ Item 0038 Ford Aerospace & May 1985 40 Communications Corporation Project Scheduling Tools GANTT CHART Page# : 2 Input File : barin.tem Date Today : 17 JUN 1985 Project Start Date (dd/mm/yy) : 14 1 85 Probability of Completion: : 0.50 Project Title : Gantt chart for Project2 Legend : H --> holiday - --> non-critical activity = --> critical activity ^ --> project start or stop * --> day(s) of first week not used +---------------------------------------------------------------------------------------------------------------------------+ ! MONTH ! 4 85 ! 5 ! 6 ! 7 ! ! DATE !15 !22 !29 ! 6 !13 !20 !27 ! 3 !10 !17 !24 ! 1 ! 8 ! +--------------------------------!------!------!------!------!------!------!------!------!------!------!------!------!------+ !QA ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Admin ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Req ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Outline manual ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Baseline ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Dev env ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !CM ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !ADL ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Review 1 ! !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Draft manual !^ !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Test plan !-^ !! !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Code and test !=====!!^ !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !troff manual ! ^---!!---^ !! !! !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Int and test ! !! ^===!!=====!!=^ !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Review 2 ! !! !! !! ^^ !! !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Tech Rep ! !! !! !! ^--!!--^ !! !!H !! !! !! !! !! H !! !! ! ! !! !! !! !! !! !! !! !! !! !! !! !! !! !Install ! !! !! !! ^!!=====!!^ !!H !! !! !! !! !! H !! !! +--------------------------------!------!------!------!------!------!------!------!------!------!------!------!------!------+ ! WORK DAYS INTO EFFORT ! 65 ! 70 ! 75 ! 80 ! 85 ! 90 ! 95 ! 99 !104 !109 !114 !119 !123 ! +---------------------------------------------------------------------------------------------------------------------------+ Item 0038 Ford Aerospace May 1985 41 Communications Corporation Project Scheduling Tools Item 0038 Ford Aerospace & May 1985 42 Communications Corporation Project Scheduling Tools Welcome to the Project Planning Tools. Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 1 <cr> Item 0038 Ford Aerospace May 1985 43 Communications Corporation Project Scheduling Tools Welcome to NEWFILE Version 1.0 Network constraints for this version are: Max number of activities (arcs) = 4000 Max number of nodes = 3400 Max number of in/out arcs at any node = 25 Max number of arcs in critical path = 2000 Press RETURN to continue ..... <cr> d <cr> <-- ENTER time units (days = D, weeks = W) <-- ENTER name of newfile input.data <cr> WARNING!!! File input.data already exists and will be overwritten. Is it ok to continue? ENTER 'C' to continue program or 'S' to stop it --> c <cr> dd/mm/yy <-- ENTER Estimated Project start date 17/06/85 <cr> Item 0038 Ford Aerospace & May 1985 44 Communications Corporation Project Scheduling Tools Activity [arc] number 1 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX <-- ENTER name of activity QA <cr> XXXXXXXX <-- ENTER arc code [WBS] B907QAAA <cr> XXXX <--ENTER tail node 1 <cr> XXXX <--ENTER head node 14 <cr> ENTER following parameters for activity: QA XXX.X <--ENTER optimistic (1%) time estimate 1 <cr> XXX.X <--ENTER most likely (1%) time estimate 1 <cr> XXX.X <--ENTER pessimistic (1%) time estimate 1 <cr> XX.X <--ENTER average number of equivalent of full-time personnel .2 <cr> XXXXXXX.X <--ENTER average cost per man-time unit 185 <cr> ENTER [r] to RE_ENTER parameters for this activity, or [s] for STOP inputting, or press RETURN to continue ..... <cr> Item 0038 Ford Aerospace May 1985 45 Communications Corporation Project Scheduling Tools Activity [arc] number 2 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX <-- ENTER name of activity Draft manual <cr> XXXXXXXX <-- ENTER arc code [WBS] B907E8PA <cr> XXXX <--ENTER tail node 4 <cr> XXXX <--ENTER head node 5 <cr> ENTER following parameters for activity: Draft manual XXX.X <--ENTER optimistic (1%) time estimate 13.0 <cr> XXX.X <--ENTER most likely (1%) time estimate 15.0 <cr> XXX.X <--ENTER pessimistic (1%) time estimate 30.0 <cr> XX.X <--ENTER average number of equivalent of full-time personnel 1.0 <cr> XXXXXXX.X <--ENTER average cost per man-time unit 185.0 <cr> ENTER [r] to RE_ENTER parameters for this activity, or [s] for STOP inputting, or press RETURN to continue ..... s <cr> Item 0038 Ford Aerospace & May 1985 46 Communications Corporation Project Scheduling Tools Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 5 <cr> Thank you for using the Project Planning Tools. Item 0038 Ford Aerospace May 1985 47 Communications Corporation Project Scheduling Tools Welcome to the Project Planning Tools. Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 2 <cr> Item 0038 Ford Aerospace & May 1985 48 Communications Corporation Project Scheduling Tools Welcome to MODIFY Version 1.0 Network constraints for this version are: Max number of activities (arcs) = 4000 Max number of nodes = 3400 Max number of inbound arcs at any node = 25 Max number of arcs in critical path = 2000 Press RETURN to continue ..... <cr> Do you want to add or delete? ENTER: a or d --> a <cr> <-- ENTER name of input file input.data <cr> WARNING !!! [input.data] will be modified. Do you wish to RE-ENTER the name? (y/n) --> n <cr> <-- How many activities will be added? 1 <cr> Item 0038 Ford Aerospace May 1985 49 Communications Corporation Project Scheduling Tools Activity [arc] number 3 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX <-- ENTER name of activity Troff manual <cr> XXXXXXXX <-- ENTER arc code [WBS] B907E8PA <cr> XXXX <--ENTER tail node 5 <cr> XXXX <--ENTER head node 15 <cr> ENTER following parameters for activity: Troff manual XXX.X <--ENTER optimistic (1%) time estimate <cr> Please enter a float between 0.0000 and 999.89984 XXX.X <--ENTER optimistic (1%) time estimate 5 <cr> XXX.X <--ENTER most likely (1%) time estimate 8 <cr> XXX.X <--ENTER pessimistic (1%) time estimate 10 <cr> XX.X <--ENTER average number of equivalent of full-time personnel 1 <cr> XXXXXXX.X <--ENTER average cost per man-time unit 120 <cr> ENTER [r] to RE_ENTER parameters for this activity or press RETURN to continue .... <cr> Are you done modifying? (y/n) --> n <cr> Item 0038 Ford Aerospace & May 1985 50 Communications Corporation Project Scheduling Tools Welcome to MODIFY Version 1.0 Network constraints for this version are: Max number of activities (arcs) = 4000 Max number of nodes = 3400 Max number of inbound arcs at any node = 25 Max number of arcs in critical path = 2000 Press RETURN to continue ..... <cr> Do you want to add or delete? ENTER: a or d --> d <cr> <-- ENTER name of input file input.data <cr> WARNING !!! [input.data] will be modified. Do you wish to RE-ENTER the name? (y/n) --> n <cr> Item 0038 Ford Aerospace May 1985 51 Communications Corporation Project Scheduling Tools Option# Activity Name 1 QA 2 Draft manual 3 Troff manual Do you wish to delete any of above activities (y/n) --> y <cr> <-- How many activities will be deleted? 1 <cr> <-- Enter option# for one of the 1's unwanted activities 3 <cr> Are you done modifying? (y/n) --> y <cr> Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 5 <cr> Thank you for using the Project Planning Tools. Item 0038 Ford Aerospace & May 1985 52 Communications Corporation Project Scheduling Tools Welcome to the Project Planning Tools. Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 3 <cr> Item 0038 Ford Aerospace May 1985 53 Communications Corporation Project Scheduling Tools ENTER the number of workdays per week --> (default => 5 ) <cr> Using default value of => 5 ENTER the number of iterations in the PERT simulation (default => 1000 ) 10 <cr> ENTER the desired probability for output (default => 0.90 ) .5 <cr> Enter the name of the file containing Activity Information [32 characters or less]. --> input.data <cr> Enter the name of the file containing Holiday date [32 character or less]. --> holiday.fil <cr> WARNING !!! [tout.tem] will be overwritten. WARNING !!! [act.tem] will be overwritten. WARNING !!! [node.tem] will be overwritten. WARNING !!! [manpower.tem] will be overwritten. WARNING !!! [barin.tem] will be overwritten. Do you wish to CONTINUE? (y/n) --> y <cr> Item 0038 Ford Aerospace & May 1985 54 Communications Corporation Project Scheduling Tools Reading the Activity Info file, and checking for correct graph structure. Pert Simulation is now running, (star represents another iteration). ********** Performing calculations for Simpert results. ENTER the last event for the critical path to be returned (default => 14 ) <cr> Using default value of => 14 ENTER a Title for the output reports. [60 characters or less] --> Proh\ (NOTE: [\] character represents Project2 <cr> a back-space) Do you wish to change the project start date (currently 14 JAN 1985). ENTER [y/n] --> (default => N ) <cr> Using default value of => N Do you have a required completion date? ENTER [y/n] --> (default => N ) <cr> Using default value of => N Do you wish to see the [Network Summary] on your screen? ENTER [y/n] --> <cr> (default => N ) Using default value of => N Item 0038 Ford Aerospace May 1985 55 Communications Corporation Project Scheduling Tools Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 5 <cr> Thank you for using the Project Planning Tools. Item 0038 Ford Aerospace & May 1985 56 Communications Corporation Project Scheduling Tools Welcome to the Project Planning Tools. Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 4 <cr> Item 0038 Ford Aerospace May 1985 57 Communications Corporation Project Scheduling Tools ENTER a Title for the output report. [60 characters or less] --> Gantt chart for Project2 <cr> In what file is Gantt output data stored? [32 characters or less] --> --> barout.tem <cr> ENTER the name of the file containing Activity Information [32 characters or less]. --> barin.tem <cr> ENTER the name of the file containing Holiday date [32 character or less]. --> holiday.fil <cr> WARNING !!! [barout.tem] will be overwritten. Do you wish to CONTINUE? (y/n) --> y <cr> Item 0038 Ford Aerospace & May 1985 58 Communications Corporation Project Scheduling Tools Limit printout by specifying print start or stop date 1 HAPPY_WITH_START_STOP_DATES_IN_INPUT_FILE 2 WANT_TO_INPUT_NEW_PRINT_STARTING_DATE_ONLY 3 WANT_TO_INPUT_NEW_PRINT_STOPPING_DATE_ONLY 4 WANT_TO_INPUT_NEW_PRINT_START_STOP_DATES What is your choice? 1 <cr> Item 0038 Ford Aerospace May 1985 59 Communications Corporation Project Scheduling Tools Project Planning Tools - Top Level Menu 1 Create New Input File for Simpert 2 Modify Existing File for Simpert 3 Run Simpert 4 Run Gantt 5 Exit from Project Planning Tools. What is your choice? 5 <cr> Thank you for using the Project Planning Tools. Item 0038 Ford Aerospace & May 1985 60 Communications Corporation Project Scheduling Tools 14. Appendix E - Compilation Order and Cross Reference Listings **** AOS/VS REV 4.04.00.00 / BATCH OUTPUT FILE **** Command line parsed. Ada Compiler Rev. 05.241.00.00 6/28/85 at 12:22:33 Reading from :UDD1:NOSC:ADA:PERT:SIM_UTIL.ADA Compilation parsed Procedure body PRESS_RETURN_TO_CONTINUE has been added to the library. Procedure body FATAL has been added to the library. Package FLOATING_CHARACTERISTICS has been added to the library. Package body FLOATING_CHARACTERISTICS has been added to the library. Package NUMERIC_IO has been added to the library. Package body NUMERIC_IO has been added to the library. Package NUMERIC_PRIMITIVES has been added to the library. Package body NUMERIC_PRIMITIVES has been added to the library. Package CORE_FUNCTIONS has been added to the library. Package body CORE_FUNCTIONS has been added to the library. Package TRIG_FUNCTIONS has been added to the library. Package body TRIG_FUNCTIONS has been added to the library. Package SCREEN_IO has been added to the library. Package body SCREEN_IO has been added to the library. Package DATE_AND_TIME has been added to the library. Package body DATE_AND_TIME has been added to the library. Package STRING_UTILITIES has been added to the library. Package body STRING_UTILITIES has been added to the library. Package FILE_OPS has been added to the library. Package body FILE_OPS has been added to the library. Package MATH_FUNCTIONS has been added to the library. Package body MATH_FUNCTIONS has been added to the library. Generic package MENU has been added to the library. Package body MENU has been added to the library. Package MULTIPLE_CHOICE has been added to the library. Package body MULTIPLE_CHOICE has been added to the library. Generic package CHARTS has been added to the library. Package body CHARTS has been added to the library. Generic package GRAPHS has been added to the library. Package body GRAPHS has been added to the library. Package PERT_IO has been added to the library. Package body PERT_IO has been added to the library. Package FILE_HANDLER has been added to the library. Package body FILE_HANDLER has been added to the library. No semantic errors Generating code *** 2700 Unsupported representation spec *** 2717 Unsupported representation spec Used 0:17:52 in 0:54:21 Command line parsed. Ada Compiler Rev. 05.241.00.00 6/28/85 at 13:17:37 Reading from :UDD1:NOSC:ADA:PERT:SCHEDULE.ADA Compilation parsed Procedure body SCHEDULE has been added to the library. No semantic errors Item 0038 Ford Aerospace May 1985 61 Communications Corporation Project Scheduling Tools Generating code Used 0:00:56 in 0:03:13 Command line parsed. Ada Compiler Rev. 05.241.00.00 6/28/85 at 13:21:23 Reading from :UDD1:NOSC:ADA:PERT:NEWFILE.ADA Compilation parsed Procedure body SCHEDULE.NEWFILE has been added to the library. No semantic errors Generating code Used 0:02:56 in 0:10:22 Command line parsed. Ada Compiler Rev. 05.241.00.00 6/28/85 at 13:32:23 Reading from :UDD1:NOSC:ADA:PERT:MODIFY.ADA Compilation parsed Procedure body SCHEDULE.MODIFY has been added to the library. No semantic errors Generating code Used 0:04:26 in 0:15:25 Command line parsed. Ada Compiler Rev. 05.241.00.00 6/28/85 at 13:48:24 Reading from :UDD1:NOSC:ADA:PERT:PERT.ADA Compilation parsed Procedure body SCHEDULE.PERT has been added to the library. Function body SCHEDULE.PERT.PERT_NETWORK has been added to the library. Procedure body SCHEDULE.PERT.PROCESS has been added to the library. Procedure body SCHEDULE.PERT.IS_GOOD has been added to the library. Procedure body SCHEDULE.PERT.OVERALL_CALCS has been added to the library. Procedure body SCHEDULE.PERT.OUTPUT_VALUES has been added to the library. Procedure body SCHEDULE.PERT.OUTPUT_VALUES.ACTIVITY_REPORT has been added to the library. Procedure body SCHEDULE.PERT.OUTPUT_VALUES.GANTT_REPORT has been added to the library. Procedure body SCHEDULE.PERT.OUTPUT_VALUES.NODE_REPORT has been added to the library. Procedure body SCHEDULE.PERT.OUTPUT_VALUES.SUM_MAN has been added to the library. No semantic errors Generating code Used 0:13:12 in 0:50:19 Command line parsed. Ada Compiler Rev. 05.241.00.00 6/28/85 at 14:39:27 Reading from :UDD1:NOSC:ADA:PERT:OUT_GANTT.ADA Compilation parsed Procedure body SCHEDULE.OUT_GANTT has been added to the library. Procedure body SCHEDULE.OUT_GANTT.GANTT_INITIALIZE has been added to the library. Procedure body SCHEDULE.OUT_GANTT.LIMIT_PRINT has been added to the library. Procedure body SCHEDULE.OUT_GANTT.FILL_HOLIDAY_LINE has been added to the library. Procedure body SCHEDULE.OUT_GANTT.INIT_ACTIVITY_LINE has been added to the library. Procedure body SCHEDULE.OUT_GANTT.FILL_WORKDAYS_FOOTER has been added to the library. Procedure body SCHEDULE.OUT_GANTT.VIRTUAL_MAP has been added to the library. Procedure body SCHEDULE.OUT_GANTT.PRINT_HEADER has been added to the library. Procedure body SCHEDULE.OUT_GANTT.PRINT_FILLER has been added to the library. Procedure body SCHEDULE.OUT_GANTT.PRINT_ACTIVITY has been added to the library. Procedure body SCHEDULE.OUT_GANTT.PRINT_MONTH_DAY_HEADER has been added to the library. Item 0038 Ford Aerospace & May 1985 62 Communications Corporation Project Scheduling Tools Procedure body SCHEDULE.OUT_GANTT.PRINT_FOOTER has been added to the library. No semantic errors Generating code Used 0:06:06 in 0:23:47 Command line parsed. Ada Loader Rev. 05.24.00.00 6/28/85 at 15:03:49 Creating PR file :UDD1:NOSC:ADA:PERT:SCHEDULE -) exit Leaving the Rolm/DGC Ada Development Environment. Item 0038 Ford Aerospace May 1985 63 Communications Corporation Project Scheduling Tools Cross reference listing procedure PRESS_RETURN_TO_CONTINUE procedure FATAL package FLOATING_CHARACTERISTICS procedure DEFLOAT procedure REFLOAT function CONVERT_TO_FLOAT function CONVERT_TO_FLOAT function CONVERT_TO_FLOAT package body FLOATING_CHARACTERISTICS procedure DEFLOAT procedure REFLOAT function CONVERT_TO_FLOAT function CONVERT_TO_FLOAT function CONVERT_TO_FLOAT package NUMERIC_IO procedure GET procedure GET procedure GET procedure GET procedure PUT procedure PUT procedure PUT procedure PUT procedure PUT package body NUMERIC_IO procedure GET procedure GET procedure GET procedure GET procedure PUT procedure PUT procedure PUT procedure PUT procedure PUT package NUMERIC_PRIMITIVES function SIGN function MAX function TRUNCATE function ROUND function RAN package body NUMERIC_PRIMITIVES function SIGN function MAX function TRUNCATE function ROUND package KEY function RAN package CORE_FUNCTIONS function SQRT function CBRT function LOG function LOG10 function EXP function ** package body CORE_FUNCTIONS Item 0038 Ford Aerospace & May 1985 64 Communications Corporation Project Scheduling Tools function SQRT function CBRT function LOG function R function LOG10 function EXP function R function ** function REDUCE package TRIG_FUNCTIONS function SIN function COS function TAN function COT function ASIN function ACOS function ATAN function ATAN2 function SINH function COSH function TANH package body TRIG_FUNCTIONS function SIN function R function COS function R function TAN function R function COT function R function ASIN function R function ACOS function R function ATAN function R function ATAN2 function SINH function R function COSH function R function TANH function R package SCREEN_IO function RETURNED_INTEGER function RETURNED_FLOAT function RETURNED_STRING package body SCREEN_IO procedure ERROR function GET_THE_STRING function GO_AGAIN function RETURNED_INTEGER function RETURNED_ANSWER function RETURNED_FLOAT function CONVERT_TO_FLOAT function RETURNED_STRING Item 0038 Ford Aerospace May 1985 65 Communications Corporation Project Scheduling Tools function RETURNED_ENUMERATION function RETURNED_ANSWER package DATE_AND_TIME function CURRENT_DATE function CURRENT_TIME function DATE function TIME function DAY_OF_WEEK function NEAREST_PRECEDING_MONDAY function JULIAN_DATE function CALENDAR_DATE package body DATE_AND_TIME function CURRENT_DATE function CURRENT_TIME function DATE function TIME function DAY_OF_WEEK function NEAREST_PRECEDING_MONDAY function JULIAN_DATE function CALENDAR_DATE package STRING_UTILITIES function FIRST_NON_BLANK_CHARACTER_POSITION function LAST_NON_BLANK_CHARACTER_POSITION function REMOVE_LEADING_AND_TRAILING_BLANKS function LOWER_TO_UPPER package body STRING_UTILITIES function FIRST_NON_BLANK_CHARACTER_POSITION function LAST_NON_BLANK_CHARACTER_POSITION function REMOVE_LEADING_AND_TRAILING_BLANKS function LOWER_TO_UPPER function LOWER_TO_UPPER_CHAR package FILE_OPS function FILE_EXISTS procedure OPEN procedure CLOSE procedure DELETE procedure USER_OPEN package body FILE_OPS function FILE_EXISTS procedure OPEN procedure CLOSE procedure DELETE procedure USER_OPEN package MATH_FUNCTIONS function ** function EXP procedure GAUSSIAN_ELIMINATION function INVERSE_NORMAL_FUNCTION function LOG function LOG10 function NORMAL_FUNCTION function POLYNOMIAL function TRUNCATE function TRUNCATE function TRUNCATED_RAYLEIGH_DISTRIBUTION package body MATH_FUNCTIONS function ** function REDUCE function EXP function R Item 0038 Ford Aerospace & May 1985 66 Communications Corporation Project Scheduling Tools function LOG function R function LOG10 function TRUNCATED_RAYLEIGH_DISTRIBUTION function POLYNOMIAL procedure GAUSSIAN_ELIMINATION function TRUNCATE function TRUNCATE function INVERSE_NORMAL_FUNCTION function NORMAL_FUNCTION generic MENU procedure GET_MENU_VALUE function STRING_MENU package body MENU procedure GET_MENU_VALUE function ENUMERATION_MENU function SPACING_LENGTH function ITEM_NUMBER function STRING_MENU function SPACING_LENGTH function ITEM_NUMBER package MULTIPLE_CHOICE package body MULTIPLE_CHOICE procedure GET generic CHARTS procedure OUTPUT procedure CLEANUP procedure CLEANUP package body CHARTS procedure OUTPUT procedure OUTPUT_STRING procedure CLEANUP procedure CLEANUP generic GRAPHS procedure CREATE_ARC function NEW_NODE procedure CREATE procedure SET_END_NODE procedure SET_START_NODE procedure DELETE procedure DELETE function CURRENT_NUMBER_OF_INCOMING_ARCS function CURRENT_NUMBER_OF_OUTGOING_ARCS function MAXIMUM_NUMBER_OF_INCOMING_ARCS function MAXIMUM_NUMBER_OF_OUTGOING_ARCS function HEAD_NODE function TAIL_NODE function START_NODE function END_NODE function VALUE function VALUE procedure ASSIGN_VALUE function ARC procedure ASSIGN procedure ASSIGN function INCOMING_ARCS function OUTGOING_ARCS function NODES procedure TOPSORT Item 0038 Ford Aerospace May 1985 67 Communications Corporation Project Scheduling Tools function LIST_OF_SINKS function LIST_OF_SOURCES function ANY_CYCLES package body GRAPHS procedure CREATE_ARC function NEXT_FREE_SLOT function NEW_NODE function NEXT_FREE_SLOT procedure CREATE procedure SET_END_NODE procedure SET_START_NODE procedure DELETE procedure DELETE function NUMBER_NON_NULL_ELEMENTS function CURRENT_NUMBER_OF_INCOMING_ARCS function CURRENT_NUMBER_OF_OUTGOING_ARCS function MAXIMUM_NUMBER_OF_INCOMING_ARCS function MAXIMUM_NUMBER_OF_OUTGOING_ARCS function HEAD_NODE function TAIL_NODE function START_NODE function END_NODE function VALUE function VALUE procedure ASSIGN_VALUE function ARC procedure ASSIGN procedure ASSIGN function INCOMING_ARCS function OUTGOING_ARCS function NODES function LIST_OF_SINKS function LIST_OF_SOURCES function ANY_CYCLES procedure TOPSORT package PERT_IO procedure READ_HEADER procedure WRITE_HEADER procedure READ_ONE_ACTIVITY_LINE procedure WRITE_ONE_LINE package body PERT_IO procedure READ_HEADER procedure WRITE_HEADER procedure READ_ONE_ACTIVITY_LINE procedure WRITE_ONE_LINE package FILE_HANDLER procedure VERIFY_OUTPUT function VERIFY_LABEL function VERIFY_INPUT package body FILE_HANDLER procedure VERIFY_OUTPUT procedure CREATE_OUTPUT_FILES function VERIFY_LABEL function VERIFY_INPUT function GETNAME_AND_VERIFY_EXISTENCE procedure SCHEDULE procedure NEWFILE function RETURN_INTEGER procedure WELCOME_MESSAGE Item 0038 Ford Aerospace & May 1985 68 Communications Corporation Project Scheduling Tools procedure SELECTION_DAYS_OR_WEEKS procedure SELECTION_CONTINUE_OR_STOP procedure OBTAIN_NAME procedure CREATEF procedure STARTDATE procedure WRITEF procedure WRITE_GLOBAL function IN_DUMMIES procedure NEW_SIMPERT_LINE function RETURN_ESTIMATE procedure NAME_NODE_ENTRY procedure TAKE_INPUT procedure MODIFY procedure READ_ONE_ACTIVITY_LINE procedure WRITE_ONE_LINE procedure WELCOME_MESSAGE function RETURN_INTEGER procedure OBTAIN_ADD_OR_DELETE procedure SELECTION_CONTINUE_OR_STOP procedure OBTAIN_NAME procedure OBTAIN_INPUT_FILE_NAME procedure GET_FILE_NAME procedure CREATE_INPUT_BUFFER_ARRAY procedure PROCESS_DELETION function HOW_MANY_TO_BE_DELETED procedure PROCESS_ADDITION function HOW_MANY_TO_BE_ADDED procedure ADD_TO_BUFFER_ARRAY function IN_DUMMIES procedure NEW_SIMPERT_LINE function RETURN_ESTIMATE procedure DATA_ENTRY procedure TAKE_INPUT procedure MODIFY_USER_INPUT_FILE procedure PERT procedure SET_UP_DISPLAY function PERT_NETWORK function NODE procedure ZERO_DUMMY procedure PROCESS function TRIANGULAR_DISTRIBUTION procedure HANDLE_TIME_OF_EVENT function PRODUCE_DURATION procedure IS_GOOD procedure OVERALL_CALCS function PROB_TIME procedure OUTPUT_VALUES function CONVERT_TO_NORMAL_DATE procedure WRITE_HEADER_REPORT procedure ADD_NON_DUMMY_ACTIVITY function REQUESTED_UNIT_CODE function TO_DAYS procedure READ_HOLIDAY_FILE function WORKDAYS_BETWEEN function NUMBER_HOLIDAYS function FIND_PROPER_DATE function IS_HOLIDAY function PROPER_DATE function GET_NEW_DATE Item 0038 Ford Aerospace May 1985 69 Communications Corporation Project Scheduling Tools function USE_DATE_STRING procedure REVISE_DATE function TIME_UNIT_STARTED function TIME_UNIT_DONE procedure SORT_NODES procedure SORT_ACT_LIST procedure ACTIVITY_REPORT procedure WRITE_ACT_HEADER_LINE procedure WRITE_ACT_BODY_LINE procedure GANTT_REPORT procedure WRITE_SECOND_HEADER_REPORT function CONVERT_TO_DD_MM_YY_DATE procedure WRITE_GANTT_HEADER_LINE procedure WRITE_GANTT_BODY_LINE procedure NODE_REPORT procedure WRITE_NODE_HEADER_LINE procedure WRITE_NODE_BODY_LINE procedure SUM_MAN procedure WRITE_MANPOWER_REPORT_BODY_LINE procedure WRITE_STOCHA_HEADER_LINE procedure WRITE_STOCHA_BODY_LINE procedure WRITE_SCHED_A_RISK_BODY_LINE procedure WRITE_RESULT_AND_DATE procedure WRITE_NETWORK_SUMMARY_BODY_LINE procedure WRITE_FLOAT_RESULT procedure WRITE_INT_RESULT procedure OUT_GANTT procedure VERIFY_OUTPUT_FILE procedure RESET_EXISTING_OUTFILE procedure GANTT_INITIALIZE function IS_HOLIDAY procedure LIMIT_PRINT function GET_NEW_START function GET_NEW_STOP function NUMBER_HOLIDAYS procedure FILL_HOLIDAY_LINE procedure INIT_ACTIVITY_LINE procedure FILL_WORKDAYS_FOOTER function NON_WORKDAYS procedure VIRTUAL_MAP procedure PRINT_HEADER procedure PRINT_FILLER procedure PRINT_ACTIVITY procedure FILL_ACT_OUT_LINE procedure PRINT_MONTH_DAY_HEADER procedure SPACE procedure PRINT_FOOTER Item 0038 Ford Aerospace & May 1985 70 Communications Corporation Project Scheduling Tools CONTENTS 1. Introduction 1 2. Notification of Future Enhancements 1 3. Computer Program System Capabilities 2 4. Overall Comment Regarding the Four Functions 3 5. Function Description of Creating a New File 4 6. Function Description of Modify 7 7. Function Description of Simpert 8 8. Function Description of Gantt 13 9. Operating Instructions 15 10. Appendix A - Motivation and Background for PERT Tools 17 11. Appendix B - Activity- on- Arc Project Networks 20 12. Appendix C - Methodology for Creating Project Network 25 13. Appendix D - Sample Executions of the Ada Tools 26 14. Appendix E - Compilation Order and Cross Reference Listings 61 - ii -