4. Financial Proposal - Mifotra

More documents

Recommendations

Info

REPORTING STRUCTURE For the purpose of this TOR, a simplistic view of the reporting structure is shown in the next diagram. IPPIS PROGRAM MANAGER HRM SYSTEMS & PROCESSES SPECIALIST The Business Analyst is responsible for compiling detail requirement analysis documentation which must be further interpreted by the Software Architect. To ensure the Software Architect understand the full scope and total requirement of the various modules, the Software Architect will work closely together with the Business Analyst who will make available all preliminary, draft and final reports for comment on a frequent basis. It is expected of the business analyst to identify all the stakeholders and to have frequent interactions with them to ensure all requirements and business processes are documented.
PROBLEM The main problem, ● During the implementation of the IPPIS solution as well as the compilation of technical documentation, a number of new requirements including changes to existing requirements were identified which will, when implemented, greatly enhance the functionality of the product. METHODOLOGY To address this problem and to ensure the identified requirements are integrated, the business analyst must, ● Perform a detailed requirement analysis which involve all stakeholders ● Document all workflows and processes ● Identify and consult with all stakeholders and end-users ● Identify and document business interfaces with external systems ● Define the expected input and output for business processes The main objectives of this consultancy are, OBJECTIVES OF THE CONSULTANCY ● Identify and develop detailed requirements for the various software modules ● Identify and document the expected input and output of the modules ● Identify and document the various users and stakeholders and list the requirements of each user ● Collaborate with the Software architect to ensure the requirements are understood and where applicable resolve any issues raised by the software architect / development team. ● Establish a group of end users who will collaborate with the team to test the various software modules. CAPACITY BUILDING AND KNOWLEDGE TRANSFER The consultant shall be responsible for sharing material knowledge therein confined in his/her consultancy deliverables for an effective knowledge transfer. The consultant must understand the fact that the project owner – MIFOTRA holds full ownership rights of the consultant’s work and right to distribution his/her work among MIFOTRA IPPIS. This is so important for effective knowledge sharing and dissemination. The consultant shall conduct regular training /discussion sessions aimed at knowledge transfer and product ownership to all the IPPIS staff and other directly involved or interested stakeholders.
Page 1 and 2: REPUBLIC OF RWANDA MINISTRY OF PUBL
Page 3 and 4: Section 3. Technical proposal - Sta
Page 5 and 6: INTRODUCTION Section 3. Technical p
Page 9 and 10: staff-months shall not be disclosed
Page 11 and 12: 4. SUBMISSION, RECEIPT, AND OPENING
Page 15 and 16: Conclusion of the negotiations Sect
Page 17 and 18: 3.3 The training is an intrinsic el
Page 19 and 20: The minimum score required to be se
Page 25 and 26: 1. Technical/Managerial Staff TECH
Page 27 and 28: Section 3 - Proposition Technique -
Page 29 and 30: Section 3 - Proposition Technique -
Page 31 and 32: 4. Financial Proposal - Standard Fo
Page 33 and 34: Subtotal Local Taxes Total Amount o
Page 35 and 36: 4D. BREAKDOWN OF REMUNERATION PER A
Page 37 and 38: 4F. MISCELLANEOUS EXPENSES Activity
Page 39: TERMS OF REFERENCE SENIOR HUMAN RES
Page 43 and 44: Second Deliverable - Detail Specifi
Page 45 and 46: ○ The input and output of each re
Page 47 and 48: For this deliverable, the consultan
Page 49 and 50: 6. Standard Forms of Contract. CONT
Page 51 and 52: acceptable; and [insert the amount

4. Financial Proposal - Mifotra

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?