Project Description New Computer Controlled Conveyor Belt Exciting Project Moves Positions Q29009159

Project Description

The new computer-controlled conveyor belt is an exciting projectthat moves and positions items on the conveyor belt within 1millimeter. The project will produce a new system for futureinstallations, and for replacement of those in the field, at a lowcost. The computer-controlled conveyor belt has the potential to bea critical unit in 30 percent of the systems installed infactories. The new system is also easier to update with futuretechnologies. Table 1 has been developed for you to use incompleting the project exercises.

Table 1 Conveyor Belt Project;WBS

Hardware

Hardware specifications

Hardware design

Hardware documentation

Prototypes

Order circuit boards

Assemble preproduction models

Operating system

Kernel specifications

Drivers

Disk drivers

Serial I/O drivers

Memory management

Operating system documentation

Network interface

Utilities

Utilities specifications

Routine utilities

Complex utilities

Utilities documentation

Shell

System integration

Architectural decisions

Integration first phase

System hard/software test

Project documentation

Integration acceptance testing

The project begins January 4, 2010.

The following holidays are observed: January 1, Memorial Day(last Monday in May), July 4th, Labor Day (first Mondayin September), Thanksgiving Day (4th Thursday in November),December 25 and 26.

If a holiday falls on a Saturday then Friday will be given as anextra day off, and if it falls on a Sunday, then Monday will begiven as a day off.

The project teams work eight-hour days, Monday throughFriday.

Table 2 Conveyor BeltProject; Schedule

Activity

Description

Resource (one team each)

Duration (days)

Preceding Activity

1

Architectural decisions

Design

25

—

2

Hardware specifications

Development, design

50

1

3

Kernel specifications

Design

20

1

4

Utilities specifications

Development, design

15

1

5

Hardware design

Design, development

70

2

6

Disk drivers

Assembly, development

100

3

7

Memory management

Development

90

3

8

Operating system documentation

Design, documentation

25

3

9

Routine utilities

Development

60

4

10

Complex utilities

Development

80

4

11

Utilities documentation

Documentation, design

20

4

12

Hardware documentation

Documentation, design

30

5

13

Integration first phase

Assembly, development

50

6,7,8,9,10,11,12

14

Prototypes

Assembly, development

80

13

15

Serial I/O drivers

Development

130

13

16

System hard/software test

Assembly

25

14,15

17

Order circuit boards

Purchasing

5

16

18

Network interface

Development

90

16

19

Shell

Development

60

16

20

Project documentation

Documentation, development

50

16

21

Assemble preproduction models

Assembly, development

30

17F-S, lag 50 days

22

Integrated acceptance testing

Assembly, development

60

18,19,20,21

Table 3 OrganizationResources

           Name

Group

Cost ($/hr)

Design

R&D (2 teams)

$100

Development

R&D (2 teams)

70

Documentation

R&D (1 team)

60

Assembly/test

R&D (1 team)

70

Purchasing

Procurement (1 team)

40

Part 3 (Bonus)

Prepare status reports for the fourth quarter of the project(Fourth Quarter, January 1, 2011) given theinformation provided in Table 4. This requires saving your resourceschedule as a base- line and inserting the appropriate statusreport date in the program. Assume that no work has been completedon the day of the status report.

Your status report should include a table containing the PV, EV,AC, BAC, EAC, SV, CV, and CPI for each activity and the wholeproject. The report should also address the followingquestions:

How is the project progressing in terms of cost andschedule?

What activities have gone well? What activities have not gonewell?

What do the PCIB and PCIC indicate in terms of how much of theproject has been accomplished to date?

What is the forecasted cost at completion (EACf)? What is thepredicted VACf ?

Report and interpret the TCPI for the project at this point intime.

What is the estimated date of completion?

Table 4 January 1,2011

Activity

Start Date

Finish Date

Actual Duration

Remaining Duration

Hardware specifications

2/9/10

4/12/10

45

0

Hardware design

4/13/10

7/16/10

67

0

Hardware documentation

7/19/10

8/24/10

27

0

Prototypes

11/11/10

–

34

44

Kernel specifications

2/8/10

3/12/10

25

0

Disk drivers

3/15/10

8/17/10

110

0

Serial I/O drivers

11/11/10

–

34

119

Memory management

3/15/10

7/30/10

98

0

Op. systems documentation

3/15/10

4/16/10

25

0

Utilities specifications

3/8/10

3/29/10

16

0

Routine utilities

4/26/10

7/27/10

65

0

Complex utilities

3/30/10

8/11/10

95

0

Utilities documentation

5/3/10

6/2/10

22

0

Architectural decisions

1/4/10

2/5/10

25

0

Integration 1st phase

8/25/10

11/10/10

55

0

Part 4

You have received revised estimates for the remaining activitiesat the end of the fourth quarter:

Prototypes will be completed on 3/8/11.

Serial I/O drivers will be completed on 6/30/11.

System hardware/software test will start on 7/1/11 and take 25days.

Order circuit boards will start on 8/8/11 and take 5 days.

Assemble preproduction model will begin on 10/14/11 and take 18days.

Project documentation is expected to start on 8/8/11 and willtake 55 days.

Network interface is expected to start on 8/8/11 and will take99 days.

Shell is expected to start on 8/8/11 and will take 55 days.

Integrated acceptance testing is expected to start on 12/29/11and will take 54 days.

Prepare a memo that addresses the following questions:

What is the new EAC for the project? How long should the projecttake given these revised estimates?

What recommendations would you make?

Include a revised schedule, a Tracking Gantt chart, and costtable with your memo.