ICT Systems Acquisition and Integration
Individual Report – Request for Proposal
This assessment item contributes 20% towards the total mark of the unit.
Resource:
- Tayntor, C, (2002), Successful Packaged Software Implementation, Auerbach Publications. Note that you have access to the eBook version of this reference. Check Unit Announcements\Welcome.
- Unit lecture 3recordings and references
- All other relevant references
Your Task:
You are required to read and understand the problems encountered by Gothaer Insurance Group, a German insurance company, as presented in the teaching case written by Robmehei al (2017) “Need for a smart solution: developing a sourcing strategy for a policy system at a German insurance company”, Journal of Information Technology Teaching Cases (2017) 7, 9-16.
You need to put yourself in the role of the IT project manager of Gothaer to create a solution for the problems around GoBest. You understand that the desirable solution should be developed without the constraints of existing products or processes. Instead it should meet two main objectives. The first is the standardisation of products and processes.
The second is the adjustment of the customer distribution towards more commerce customers. You understand there is a unanimous agreement within Gothaer that a new system, when established, should show seamless integration with externally bought software. The internal IT infrastructure and support system, GoSys, should have highercapabilities but should requirefewer employees.
You are creating a RFP to attract external software providers to provide solutions. You can use your IT knowledge to give as many details as you can think of for this task.
The word limit of your report is 4000 – 5000 words (excluding title page, table of contents and references).
Submission Requirements
You are required to submit to MyLO submission tool for this assignment before the due date.
The School’s Late Assessments policy (available from http://www.cis.utas.edu.au/downloads/ExtensionPolicy.pdf) describes the penalties for late submission and also explains what to do if you are unable to hand in your assignment on time for genuine reasons, such as illness.
RFP Report Organisations and Presentation (10%)
Marks will be allocated for the general organisation and flow of the report, including use of appropriate headings and sub-headings, effective use of diagrams, bullet points, tables etc if applicable. Grammar, spelling and writing style are also significant.
You will lose marks for: omitting the table of contents; for not structuring the report logically; for poor or inconsistent formatting and layout of the report.
RFP Content Coverage & Details (80%)
This is the ‘heart’ of your report and should cover all aspects of the Request for Proposal and provide as many details as possible to give potential vendors a clear picture of your needs and requirements.
Referencing (10%)
Even though a RFP may not indicate references, I would like you to provide some key references that support your ideas and proposals in your RFP report. Detailed information on how to use referencing properly is available on the UTAS website at:http://utas.libguides.com/referencing.
Marking Criteria for RFP (20%)
KXI303 Systems Acquisition and Integration: Request for Proposal
| |||||
| Criteria (Table Heading) | HD | DN | CR | PP | NN |
| You | You | You | You | You | |
| Apply knowledge by: · Fulfilling the requirements of creating a RFP; · Interpreting the understanding the requirements of the system to be developed: · Providing a clear description of requirements of the target system
Weighting: 80%
| · Have covered all the required elements for a complete RFP documentation; · Have provided extremely clear anddetails of the requirements in all aspects of the target system that you can think of; · Have created logical details (if needed) relevant to the case study and desirable system requirements; · Have provided evidence that shows thorough and in-depth knowledge of the task to be conducted. · | · Have covered all the required elements for a complete RFP documentation; · Have covered requirements in all aspects of the target system but some of them need more clarification. · Have created mostly logical details (if needed) relevant to the case study and desirable system requirements; · Have demonstrated good knowledge of the task to be conducted. | · Have listed all the required elements for a complete RFP documentation; · Have partially covered requirements of the target system and some of them need more clarification. · Have attempted additional details but are remotely related to the case study and desirable system requirements; · Have demonstrated reasonable knowledge of the task to be conducted. | · Have listed all the required elements for a complete RFP documentation; · Have partially covered requirements of the target system with minimal and basic descriptions. · Have limited details for a desirable system making bidding a bit challenging; · Have demonstrated basic knowledge of the task to be conducted. | · Have failed to produce a RFP report of an adequate standard |
| Act professionally by: · Ensuring appropriate communication with all relevant professional parties · Adhering to professional and ethical codes of conduct
Weighting: 20%
| · Have produced an extremely well-structured and easily-followed report · Have indicated genuine reference sources towards RFP creation and used the correct referencing format. | · Have produced a relatively high-quality report · Have indicated relevant reference sources towards RFP creation and used the correct referencing format. | · Have produced a medium quality report with obviously room for improvement. · Most reference sources are obviously related to the RFP creation and referencing format is OK. | · Have produced a report with some obvious formatting and language issues · Some reference sources are obviously irrelevant & some minor issues with referencing format. | · Have failed to provide a report with the basic presentation requirements.
|