We advise you to use Microsoft Project 2013 for this work - but you can use other software if you prefer (provided it has similar features and you know how to use them). Instead of using this case study for your coursework, you may use details from your own project - but only if you clear this with Martin Topple by Teaching Week 8 at the latest. Of course, your own project must be of equivalent size and complexity to the case study enclosed. This is an individual assessment. All work submitted must be your own work. Any plagiarism or copying discovered will be referred to the appropriate Head of School and constitutes a serious examination offence. You must submit a written, typed or printed version of your coursework. Electronic submission or submission on cd-rom or memory stick is not acceptable. It is not necessary to word process this assignment - work completed in a fair hand is permissible. If you do word process the task(s), we may wish to examine your media at any stage during or after the assessment period. So please keep any media safe and make regular backups. Keeping discs and/or other electronic media (and their copies) safe is your responsibility. Disc, media or printer failure is not an acceptable reason for late submission. Feedback: If, on submission, you attach a stamped addressed envelope to your work, we will post your feedback sheet to you. This is the quickest way for you to obtain feedback. BACKGROUND INFORMATION: This case study is based on a job run by a firm of Computer Consultants to install some new database query software across a company with several different sites (nodes). The tasks are already grouped and indented - but resource allocations have been stripped out. You can obtain the project file from WebLearn or from the shared area of your file server. The file, called BA6052.mpp, has been saved with a baseline. The project consists of about 50 tasks (some of which are summary tasks or milestones). Notice that the critical tasks are unshaded whereas the non critical tasks are shaded in. This is so you can tell them apart on a monochrome printer or a photocopier. Part A: You are given the following information about the supply of resources (all work based):Martin Topple File: BA6052 Coursework.doc Page 2 Resource Name: Max Units: Standard Rate O/T rate: Applications Manager 200% £70.00/h £90.00/h Integration Manager 100% £65.00/h £80.00/h Manager 100% £80.00/h £95.00/h Network Engineer 500% £50.00/h £80.00/h Programmer 500% £50.00/h £65.00/h Software Installer 400% £50.00/h £70.00/h Support Manager 100% £60.00/h £80.00/h Systems Analyst 300% £55.00/h £75.00/h System Tester 300% £55.00/h £70.00/h Technical Author 100% £60.00/h £90.00/h Required: Part A i) First, allocate these resources to the tasks as stated below (where 'NE' means Network Engineer, 'M' means Manager … and so on): ID Brief Name: Resources to be allocated: 3 Install Ethernet and fast ethernet NE at 100% and SI at 300% 5 Request BT for connections M at 100% 6 Schedule downtime for installation NE at 100% and SI at 200% 10 Determine subsystems to be installed M at 100% and IM at 100% Next, using your common sense (and differently from every other student), allocate at least one of the resources to each of the sub tasks as you consider appropriate. Do not add resources to top level summary tasks or milestones (though you may wish to add various fixed costs to these later). For example, sub tasks that involve installation of software will require Software Installers, sub tasks which involve writing or reviewing manuals will involve the Technical Author, etc. Some sub tasks may need more than one resource. Do not feel that you have to use all of the resources listed. (Your mark will ignore the relevance, or otherwise, of your allocations.) It is likely that some resource clashes will occur. For the first three such clashes that occur: Resolve them in any way you consider sensible or let MS Project do it for you. Document carefully and explain any changes made either by you or by Project at the task level. For any other clashes that occur: Simply resolve them. There is no need to document any of the additional clashe