SlideShare a Scribd company logo
Automated Factory Project
James Burgess
Chris Diefenderfer
Nick Vangeli
Michael Vitoroulis
Nathan Webb
For our automated factory project, we were given three different parts to complete our
project. Each part had different amount of days that the project should be completed in. In the
first part of the project, we had to develop a project and schedule for the least cost/most days,
compute the early start, early finish, late start, late finish, slack, and free slack. We wrote down
each activity and how many days it would take for each one to complete. We were given start
times and finish times of when they were each going to be completed. Each activity was also
given a late start and late finish with respect to their early start and finish days. Each activity is
also given an amount of slack, which is the allotted amount of time that a task can slip before it
affects another task or the project's finish date. Some of the activities are given free slack as well,
which is the amount of time a task can be delayed before its successor task is delayed. Once all
of this was given, we then wrote down how much each activity cost for how many days it would
take to be completed. It takes 125 days for the entire project to be completed and a total of
$3,789,490. The critical path for this part of the project was activity 1, 4, 10, 19, 25, 32, 40, 41,
and 42.
In the second part of this project, we had to develop a project network and schedule for
the least days/most cost. When we wrote down the different days some of the activities needed to
be completed by, we saw that the project could be completed within 98 days instead of the 125
days previously stated. Once this information was put into the system, we found the critical path
for how the project should be completed. The critical path for the project at this point is activity
1, 5, 16, 22, 27, 33, and 41. The new cost for the project is $4,428,110 and is more sensitive than
least cost most days.
In the third part of the project, we determined the most likely amount of days that the
project would be completed in. Once we change the correct activity days, it came out to be 110
days. Once this was done, the critical path was changed. The new critical path for the project was
activities 1, 4, 10, 19, 25, 32, and 42. We also had to figure out the weighted average time each
activity would be done in, the activities standard deviation, and its activity variance. To find the
weighted average time, we had to add the worst case to the most likely, add the sum of 4 times
the best case, and then divide that whole answer by 6 in order to find the weighted average time.
In order to find the activities standard deviation, we had to find the difference of the best case
and the worst case and then divide that by 6. To find the activity variance, we had to square the
standard deviation.
The object of this project is to determine how long it will take for a certain project to be
completed and what is the right path to take in order to complete it. The bottom line of this is
project is that it will be completed in the most likely amount of days that were given to us. The
alternate solutions for doing this are the worst case, the most amounts of days, the best case, the
least amount of days, and the most likely case. The probability for completing the project in 107
days is 7.3%. We recommend that the project should get done in the most efficient way by using
the least cost because we would rather spend less money and take more time to do it rather than
taking less amount of time and spending more money.
3
6
7
8 9
10
11
12
13
14
15
17
18
19
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41 42
43
44
2
4
5
1
16
20
Critical path for part 1
2 3
4
5
6
7
8 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41 42
43
44
1
Critical path for part 2
2 3
4
5
6
7
8 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41 42
43
44
1
Critical path for part 3

More Related Content

Viewers also liked

decalogo
decalogodecalogo
decalogo
ProfeAragon
 
Decálogo
DecálogoDecálogo
Decálogo
ProfeAragon
 
Decalogo de computacion
Decalogo de computacionDecalogo de computacion
Decalogo de computacion
ProfeAragon
 
Decálogo de normas en la sala
Decálogo de normas en la salaDecálogo de normas en la sala
Decálogo de normas en la sala
ProfeAragon
 
Decálogo normas sala de computación
Decálogo normas sala de computaciónDecálogo normas sala de computación
Decálogo normas sala de computación
ProfeAragon
 
Decálogo
DecálogoDecálogo
Decálogo
ProfeAragon
 
Decalogo
Decalogo Decalogo
Decalogo
ProfeAragon
 
Automated Factory Project
Automated Factory ProjectAutomated Factory Project
Automated Factory Project
Nick Vangeli
 
Decalogo de normas en la sala de computacion
Decalogo de normas en la sala de computacionDecalogo de normas en la sala de computacion
Decalogo de normas en la sala de computacion
ProfeAragon
 

Viewers also liked (9)

decalogo
decalogodecalogo
decalogo
 
Decálogo
DecálogoDecálogo
Decálogo
 
Decalogo de computacion
Decalogo de computacionDecalogo de computacion
Decalogo de computacion
 
Decálogo de normas en la sala
Decálogo de normas en la salaDecálogo de normas en la sala
Decálogo de normas en la sala
 
Decálogo normas sala de computación
Decálogo normas sala de computaciónDecálogo normas sala de computación
Decálogo normas sala de computación
 
Decálogo
DecálogoDecálogo
Decálogo
 
Decalogo
Decalogo Decalogo
Decalogo
 
Automated Factory Project
Automated Factory ProjectAutomated Factory Project
Automated Factory Project
 
Decalogo de normas en la sala de computacion
Decalogo de normas en la sala de computacionDecalogo de normas en la sala de computacion
Decalogo de normas en la sala de computacion
 

Similar to Project Management Paper

Resource-Allocation.ppt
Resource-Allocation.pptResource-Allocation.ppt
Resource-Allocation.ppt
TecnicoItca
 
MBA 6951, Managing Complex Projects 1 Course Learning.docx
 MBA 6951, Managing Complex Projects 1 Course Learning.docx MBA 6951, Managing Complex Projects 1 Course Learning.docx
MBA 6951, Managing Complex Projects 1 Course Learning.docx
aryan532920
 
UNIT-3.pptx
UNIT-3.pptxUNIT-3.pptx
UNIT-3.pptx
Raja Manyam
 
Chapter 5,6,7 (group 1 project man)
Chapter 5,6,7 (group 1 project man)Chapter 5,6,7 (group 1 project man)
Chapter 5,6,7 (group 1 project man)
Arvin Dela Cruz
 
Critical chain-concepts
Critical chain-conceptsCritical chain-concepts
Critical chain-concepts
Fernanda Farias
 
Part II: Planning Time: Determining When and How Much
Part II: Planning Time: Determining When and How MuchPart II: Planning Time: Determining When and How Much
Part II: Planning Time: Determining When and How Much
Muzo Bacan
 
Drs 255 project management skills
Drs 255 project management skillsDrs 255 project management skills
Drs 255 project management skills
paulyeboah
 
-PM-09-7.ppt
-PM-09-7.ppt-PM-09-7.ppt
-PM-09-7.ppt
TecnicoItca
 
Estimating software development
Estimating software developmentEstimating software development
Estimating software development
Jane Prusakova
 
Questions
QuestionsQuestions
Questions
venkat27
 
LAFS PREPRO Session 5 - Project Schedule
LAFS PREPRO Session 5 - Project ScheduleLAFS PREPRO Session 5 - Project Schedule
LAFS PREPRO Session 5 - Project Schedule
David Mullich
 
Project Management Basics
Project Management BasicsProject Management Basics
Project Management Basics
Grayson J. Stedman jr.
 
Assignment 1 Identify elements of concern (e.g. resources.docx
Assignment 1 Identify elements of concern (e.g. resources.docxAssignment 1 Identify elements of concern (e.g. resources.docx
Assignment 1 Identify elements of concern (e.g. resources.docx
sherni1
 
Project Analytics: Visibility that Aids Risk Management
Project Analytics: Visibility that Aids Risk ManagementProject Analytics: Visibility that Aids Risk Management
Project Analytics: Visibility that Aids Risk Management
Aggregage
 
Analytics in Action: Project Analytics: Visibility that Aids Risk Management
Analytics in Action: Project Analytics: Visibility that Aids Risk ManagementAnalytics in Action: Project Analytics: Visibility that Aids Risk Management
Analytics in Action: Project Analytics: Visibility that Aids Risk Management
Hannah Flynn
 
Project Management How To
Project Management How ToProject Management How To
Project Management How To
kellyfrey
 
Agile Projects | Rapid Estimation | Techniques | Tips
Agile Projects | Rapid Estimation | Techniques | TipsAgile Projects | Rapid Estimation | Techniques | Tips
Agile Projects | Rapid Estimation | Techniques | Tips
cPrime | Project Management | Agile | Consulting | Staffing | Training
 
Project TimeIST4055Chapter 6Now that you have the Sc.docx
Project TimeIST4055Chapter 6Now that you have the Sc.docxProject TimeIST4055Chapter 6Now that you have the Sc.docx
Project TimeIST4055Chapter 6Now that you have the Sc.docx
briancrawford30935
 
2Project_management. Ghjjkkutfghuuijkpdf
2Project_management. Ghjjkkutfghuuijkpdf2Project_management. Ghjjkkutfghuuijkpdf
2Project_management. Ghjjkkutfghuuijkpdf
RedietWegene
 
Project
ProjectProject
Project
sobakavi
 

Similar to Project Management Paper (20)

Resource-Allocation.ppt
Resource-Allocation.pptResource-Allocation.ppt
Resource-Allocation.ppt
 
MBA 6951, Managing Complex Projects 1 Course Learning.docx
 MBA 6951, Managing Complex Projects 1 Course Learning.docx MBA 6951, Managing Complex Projects 1 Course Learning.docx
MBA 6951, Managing Complex Projects 1 Course Learning.docx
 
UNIT-3.pptx
UNIT-3.pptxUNIT-3.pptx
UNIT-3.pptx
 
Chapter 5,6,7 (group 1 project man)
Chapter 5,6,7 (group 1 project man)Chapter 5,6,7 (group 1 project man)
Chapter 5,6,7 (group 1 project man)
 
Critical chain-concepts
Critical chain-conceptsCritical chain-concepts
Critical chain-concepts
 
Part II: Planning Time: Determining When and How Much
Part II: Planning Time: Determining When and How MuchPart II: Planning Time: Determining When and How Much
Part II: Planning Time: Determining When and How Much
 
Drs 255 project management skills
Drs 255 project management skillsDrs 255 project management skills
Drs 255 project management skills
 
-PM-09-7.ppt
-PM-09-7.ppt-PM-09-7.ppt
-PM-09-7.ppt
 
Estimating software development
Estimating software developmentEstimating software development
Estimating software development
 
Questions
QuestionsQuestions
Questions
 
LAFS PREPRO Session 5 - Project Schedule
LAFS PREPRO Session 5 - Project ScheduleLAFS PREPRO Session 5 - Project Schedule
LAFS PREPRO Session 5 - Project Schedule
 
Project Management Basics
Project Management BasicsProject Management Basics
Project Management Basics
 
Assignment 1 Identify elements of concern (e.g. resources.docx
Assignment 1 Identify elements of concern (e.g. resources.docxAssignment 1 Identify elements of concern (e.g. resources.docx
Assignment 1 Identify elements of concern (e.g. resources.docx
 
Project Analytics: Visibility that Aids Risk Management
Project Analytics: Visibility that Aids Risk ManagementProject Analytics: Visibility that Aids Risk Management
Project Analytics: Visibility that Aids Risk Management
 
Analytics in Action: Project Analytics: Visibility that Aids Risk Management
Analytics in Action: Project Analytics: Visibility that Aids Risk ManagementAnalytics in Action: Project Analytics: Visibility that Aids Risk Management
Analytics in Action: Project Analytics: Visibility that Aids Risk Management
 
Project Management How To
Project Management How ToProject Management How To
Project Management How To
 
Agile Projects | Rapid Estimation | Techniques | Tips
Agile Projects | Rapid Estimation | Techniques | TipsAgile Projects | Rapid Estimation | Techniques | Tips
Agile Projects | Rapid Estimation | Techniques | Tips
 
Project TimeIST4055Chapter 6Now that you have the Sc.docx
Project TimeIST4055Chapter 6Now that you have the Sc.docxProject TimeIST4055Chapter 6Now that you have the Sc.docx
Project TimeIST4055Chapter 6Now that you have the Sc.docx
 
2Project_management. Ghjjkkutfghuuijkpdf
2Project_management. Ghjjkkutfghuuijkpdf2Project_management. Ghjjkkutfghuuijkpdf
2Project_management. Ghjjkkutfghuuijkpdf
 
Project
ProjectProject
Project
 

Project Management Paper

  • 1. Automated Factory Project James Burgess Chris Diefenderfer Nick Vangeli Michael Vitoroulis Nathan Webb
  • 2. For our automated factory project, we were given three different parts to complete our project. Each part had different amount of days that the project should be completed in. In the first part of the project, we had to develop a project and schedule for the least cost/most days, compute the early start, early finish, late start, late finish, slack, and free slack. We wrote down each activity and how many days it would take for each one to complete. We were given start times and finish times of when they were each going to be completed. Each activity was also given a late start and late finish with respect to their early start and finish days. Each activity is also given an amount of slack, which is the allotted amount of time that a task can slip before it affects another task or the project's finish date. Some of the activities are given free slack as well, which is the amount of time a task can be delayed before its successor task is delayed. Once all of this was given, we then wrote down how much each activity cost for how many days it would take to be completed. It takes 125 days for the entire project to be completed and a total of $3,789,490. The critical path for this part of the project was activity 1, 4, 10, 19, 25, 32, 40, 41, and 42. In the second part of this project, we had to develop a project network and schedule for the least days/most cost. When we wrote down the different days some of the activities needed to be completed by, we saw that the project could be completed within 98 days instead of the 125 days previously stated. Once this information was put into the system, we found the critical path for how the project should be completed. The critical path for the project at this point is activity 1, 5, 16, 22, 27, 33, and 41. The new cost for the project is $4,428,110 and is more sensitive than least cost most days. In the third part of the project, we determined the most likely amount of days that the project would be completed in. Once we change the correct activity days, it came out to be 110
  • 3. days. Once this was done, the critical path was changed. The new critical path for the project was activities 1, 4, 10, 19, 25, 32, and 42. We also had to figure out the weighted average time each activity would be done in, the activities standard deviation, and its activity variance. To find the weighted average time, we had to add the worst case to the most likely, add the sum of 4 times the best case, and then divide that whole answer by 6 in order to find the weighted average time. In order to find the activities standard deviation, we had to find the difference of the best case and the worst case and then divide that by 6. To find the activity variance, we had to square the standard deviation. The object of this project is to determine how long it will take for a certain project to be completed and what is the right path to take in order to complete it. The bottom line of this is project is that it will be completed in the most likely amount of days that were given to us. The alternate solutions for doing this are the worst case, the most amounts of days, the best case, the least amount of days, and the most likely case. The probability for completing the project in 107 days is 7.3%. We recommend that the project should get done in the most efficient way by using the least cost because we would rather spend less money and take more time to do it rather than taking less amount of time and spending more money.