please see the pdf file and let me know
Faculty of Engineering & Information Sciences (EIS) School of Mechanical, Materials, Mechatronic & Biomedical Engineering (MMMB) ENGG951 Engineering Project Management ASSIGNMENT 1 - Individual Assignment - 20% Use of MS Project 2016 (or equivalent). You are presented with the following problem∗ that involves the design of a Conveyor Belt Project: Project Description: You’ve been assigned to manage a project to design and install a new computer controlled conveyor belt that moves and positions items within the manufacturing process within <1 millimetre. this project will produce a new system that can be used for future installations, and for replacing those in the field, at a low cost. the new system is also easier to update with future technologies. so it delivers advantages of both cost reduction and scalability. id task name duration (days) precedence resources 1 architectural decisions 25 - design 2 hardware specifications 50 1 development, design 3 kernel specifications 20 1 design 4 utilities specifications 15 1 development, design 5 hardware design 70 2 design, development 6 disk drives 100 3 assembly, development 7 memory management 90 3 development 8 operating system documentation 25 3 design, documentation 9 routine utilities 60 4 development 10 complex utilities 80 4 development 11 utilities documentation 20 4 documentation, design 12 hardware documentation 30 5 documentation, design 13 integration first phase 50 6, 7, 8, 9, 10, 11, 12 assembly, development 14 prototypes 80 13 assembly, development 15 serial i/o drivers 130 13 development 16 system hard/software test 25 14,15 assembly 17 order circuit boards 5 16 purchasing 18 network interface 90 16 development 19 shell 60 16 development 20 project documentation 50 16 documentation, development 21 assemble preproduction models 30 17f-s, lag 50 days assembly, development 22 integrated acceptance testing 60 18, 19, 20, 21 assembly, development resource abbreviation availability rate design staff des 2 $100/hour development staff dev 2 $70/hour documentation staff doc 1 $60/hour assembly/test staff a&t 1 $70/hour purchasing staff purch 1 $40/hour site shed ss 1 $500/month hire print copier printer 1 $20/day ∗ based on project management, the managerial process, larson & gray, 6th edition section a – ms project tasks and interpretation of results: 1. create a new file and enter name and title. ensure the author's name and student number is entered in the appropriate field to be displayed in all print-outs and reports. 2. fix the start of the project to 1st october this year. 3. produce a gantt chart to include in your report. 4. generate a resource graph, and investigate any overloads. explore three resource demand management options, for example, considering time-constrained, resource-constrained and cost-constrained scenarios. show their effects on the project duration and cost? produce gantt charts before and after levelling and include in your report. 5. produce a cost report for this project, showing the cost of each task and of each resource. section b - assignment report: you are required to submit a hard copy of your report. the report format should comply with, that of a typical technical report (using a structured layout with appropriate headings). 1. how to guidelines: imagine that you are training a junior assistant to become a future project manager. you need to explain to them how to schedule this project using ms project. write a step by step description of how you accomplished the requirements of section a. 2. assumptions: as for any technical report, it is important to state any assumptions made in setting out your solution approach, as well as in relation to the analysis and/or interpretation of results. ensure that this is included in an appropriately labelled section within the body of your report. 3. results: a results section containing all of the elements identified in section a. each appropriately labelled and referenced. 4. discussion and conclusions: the focus of your report shall be the issues involved, solutions proposed and lessons learnt in completing the exercise, and must demonstrate an understanding of the use of ms project as well as its limitations. a brief comparison of these limitations with other available project management software packages is encouraged. note: the report must include: 1. a well structured gantt chart highlighting the critical path. 2. resource histograms showing pre levelling and post levelling outcomes for each of the levelling options you have considered an a final recommendation regarding the optimal resource allocation and schedule. 3. cost reports showing the breakdown by task and by resource and showing the cost of your recommended solution. 4. a determination of when is the project estimated to be completed? how many working days will it take? submission requirements: format: • all print-outs (gantt charts, histograms and cost reports) must be scaled to fit on one a4 page each • all charts must have a title block which clearly identifies what is being presented and the author’s name and student number • the report and all ms project files must include your name and student id in the file name, submission: • a hard copy of your report must be submitted, with a cover sheet, to eis central. • the completed report must be submitted via turnitin. this must be submitted as a turnitin readable format. • ms project file(s), saved in appropriate format, must be submitted via moodle. due date: all required items must be submitted by 4:00 pm friday, 7 sept. marking criteria please see marking guidelines assessment 1 provided on moodle. engg951 engineering project management millimetre.="" this="" project="" will="" produce="" a="" new="" system="" that="" can="" be="" used="" for="" future="" installations,="" and="" for="" replacing="" those="" in="" the="" field,="" at="" a="" low="" cost.="" the="" new="" system="" is="" also="" easier="" to="" update="" with="" future="" technologies.="" so="" it="" delivers="" advantages="" of="" both="" cost="" reduction="" and="" scalability.="" id="" task="" name="" duration="" (days)="" precedence="" resources="" 1="" architectural="" decisions="" 25="" -="" design="" 2="" hardware="" specifications="" 50="" 1="" development,="" design="" 3="" kernel="" specifications="" 20="" 1="" design="" 4="" utilities="" specifications="" 15="" 1="" development,="" design="" 5="" hardware="" design="" 70="" 2="" design,="" development="" 6="" disk="" drives="" 100="" 3="" assembly,="" development="" 7="" memory="" management="" 90="" 3="" development="" 8="" operating="" system="" documentation="" 25="" 3="" design,="" documentation="" 9="" routine="" utilities="" 60="" 4="" development="" 10="" complex="" utilities="" 80="" 4="" development="" 11="" utilities="" documentation="" 20="" 4="" documentation,="" design="" 12="" hardware="" documentation="" 30="" 5="" documentation,="" design="" 13="" integration="" first="" phase="" 50="" 6,="" 7,="" 8,="" 9,="" 10,="" 11,="" 12="" assembly,="" development="" 14="" prototypes="" 80="" 13="" assembly,="" development="" 15="" serial="" i/o="" drivers="" 130="" 13="" development="" 16="" system="" hard/software="" test="" 25="" 14,15="" assembly="" 17="" order="" circuit="" boards="" 5="" 16="" purchasing="" 18="" network="" interface="" 90="" 16="" development="" 19="" shell="" 60="" 16="" development="" 20="" project="" documentation="" 50="" 16="" documentation,="" development="" 21="" assemble="" preproduction="" models="" 30="" 17f-s,="" lag="" 50="" days="" assembly,="" development="" 22="" integrated="" acceptance="" testing="" 60="" 18,="" 19,="" 20,="" 21="" assembly,="" development="" resource="" abbreviation="" availability="" rate="" design="" staff="" des="" 2="" $100/hour="" development="" staff="" dev="" 2="" $70/hour="" documentation="" staff="" doc="" 1="" $60/hour="" assembly/test="" staff="" a&t="" 1="" $70/hour="" purchasing="" staff="" purch="" 1="" $40/hour="" site="" shed="" ss="" 1="" $500/month="" hire="" print="" copier="" printer="" 1="" $20/day="" ∗="" based="" on="" project="" management,="" the="" managerial="" process,="" larson="" &="" gray,="" 6th="" edition="" section="" a="" –="" ms="" project="" tasks="" and="" interpretation="" of="" results:="" 1.="" create="" a="" new="" file="" and="" enter="" name="" and="" title.="" ensure="" the="" author's="" name="" and="" student="" number="" is="" entered="" in="" the="" appropriate="" field="" to="" be="" displayed="" in="" all="" print-outs="" and="" reports.="" 2.="" fix="" the="" start="" of="" the="" project="" to="" 1st="" october="" this="" year.="" 3.="" produce="" a="" gantt="" chart="" to="" include="" in="" your="" report.="" 4.="" generate="" a="" resource="" graph,="" and="" investigate="" any="" overloads.="" explore="" three="" resource="" demand="" management="" options,="" for="" example,="" considering="" time-constrained,="" resource-constrained="" and="" cost-constrained="" scenarios.="" show="" their="" effects="" on="" the="" project="" duration="" and="" cost?="" produce="" gantt="" charts="" before="" and="" after="" levelling="" and="" include="" in="" your="" report.="" 5.="" produce="" a="" cost="" report="" for="" this="" project,="" showing="" the="" cost="" of="" each="" task="" and="" of="" each="" resource.="" section="" b="" -="" assignment="" report:="" you="" are="" required="" to="" submit="" a="" hard="" copy="" of="" your="" report.="" the="" report="" format="" should="" comply="" with,="" that="" of="" a="" typical="" technical="" report="" (using="" a="" structured="" layout="" with="" appropriate="" headings).="" 1.="" how="" to="" guidelines:="" imagine="" that="" you="" are="" training="" a="" junior="" assistant="" to="" become="" a="" future="" project="" manager.="" you="" need="" to="" explain="" to="" them="" how="" to="" schedule="" this="" project="" using="" ms="" project.="" write="" a="" step="" by="" step="" description="" of="" how="" you="" accomplished="" the="" requirements="" of="" section="" a.="" 2.="" assumptions:="" as="" for="" any="" technical="" report,="" it="" is="" important="" to="" state="" any="" assumptions="" made="" in="" setting="" out="" your="" solution="" approach,="" as="" well="" as="" in="" relation="" to="" the="" analysis="" and/or="" interpretation="" of="" results.="" ensure="" that="" this="" is="" included="" in="" an="" appropriately="" labelled="" section="" within="" the="" body="" of="" your="" report.="" 3.="" results:="" a="" results="" section="" containing="" all="" of="" the="" elements="" identified="" in="" section="" a.="" each="" appropriately="" labelled="" and="" referenced.="" 4.="" discussion="" and="" conclusions:="" the="" focus="" of="" your="" report="" shall="" be="" the="" issues="" involved,="" solutions="" proposed="" and="" lessons="" learnt="" in="" completing="" the="" exercise,="" and="" must="" demonstrate="" an="" understanding="" of="" the="" use="" of="" ms="" project="" as="" well="" as="" its="" limitations.="" a="" brief="" comparison="" of="" these="" limitations="" with="" other="" available="" project="" management="" software="" packages="" is="" encouraged.="" note:="" the="" report="" must="" include:="" 1.="" a="" well="" structured="" gantt="" chart="" highlighting="" the="" critical="" path.="" 2.="" resource="" histograms="" showing="" pre="" levelling="" and="" post="" levelling="" outcomes="" for="" each="" of="" the="" levelling="" options="" you="" have="" considered="" an="" a="" final="" recommendation="" regarding="" the="" optimal="" resource="" allocation="" and="" schedule.="" 3.="" cost="" reports="" showing="" the="" breakdown="" by="" task="" and="" by="" resource="" and="" showing="" the="" cost="" of="" your="" recommended="" solution.="" 4.="" a="" determination="" of="" when="" is="" the="" project="" estimated="" to="" be="" completed?="" how="" many="" working="" days="" will="" it="" take?="" submission="" requirements:="" format:="" •="" all="" print-outs="" (gantt="" charts,="" histograms="" and="" cost="" reports)="" must="" be="" scaled="" to="" fit="" on="" one="" a4="" page="" each="" •="" all="" charts="" must="" have="" a="" title="" block="" which="" clearly="" identifies="" what="" is="" being="" presented="" and="" the="" author’s="" name="" and="" student="" number="" •="" the="" report="" and="" all="" ms="" project="" files="" must="" include="" your="" name="" and="" student="" id="" in="" the="" file="" name,="" submission:="" •="" a="" hard="" copy="" of="" your="" report="" must="" be="" submitted,="" with="" a="" cover="" sheet,="" to="" eis="" central.="" •="" the="" completed="" report="" must="" be="" submitted="" via="" turnitin.="" this="" must="" be="" submitted="" as="" a="" turnitin="" readable="" format.="" •="" ms="" project="" file(s),="" saved="" in="" appropriate="" format,="" must="" be="" submitted="" via="" moodle.="" due="" date:="" all="" required="" items="" must="" be="" submitted="" by="" 4:00="" pm="" friday,="" 7="" sept.="" marking="" criteria="" please="" see="" marking="" guidelines="" assessment="" 1="" provided="" on="" moodle.="" engg951="" engineering="" project="">