Support and Planning Checklist
Items you need to have in place before you are ready to be live.
Planning for Production
Post deployment planning is a critical part of any software implementation. We advise financial institutions to review the checklists on the pages below to prepare for production activity. All items should be documented, tested, and put into place as soon as possible.
Overall System Administration and Maintenance
Server hosting and networking
- Bandwidth considerations: Monitor the bandwidth volume for the first month. Is the bandwidth contract sufficient?
- Data center and access:
- Do you need to account for both local and remote access?
- Are instructions for accessing remotely documented?
- Who should have access to the data center, and do they have the necessary permissions/clearances?
Server and application monitoring
See our System Administration Documentation for tips on monitoring and logging.
- Which areas will be monitored?
- How will they be monitored?
- What will this information be used for?
- What tools are necessary?
- Who will be responsible for these tasks?
On-going infrastructure planning/needs
What are the criteria for determining when to upgrade hardware, etc. What is the process for upgrading server hardware and software?
Troubleshooting and end-user support
- Processes for end user support and issue resolution
- Hiring/staffing to support this function
Application administration
- Processes for performing application administration duties such as making configuration changes to Mifos, adding/changing products, adding/changing offices, roles & permissions, etc
- Processes for performing user maintenance (adding new system users, removing system users who have left the organization, etc)
- Documentation
- Hiring/staffing to support this function
Integrating Mifos into the organization
- Training new employees on Mifos. What will the process be? How will this work?
- Identify ongoing training needs for existing employees and ensure those needs are met.
- Identify and implement measures for evaluating training success and gaps in training
- Documenting how Mifos fits in with all operations within the financial institution outside of the IT team
Mifos upgrades and bug fixes
- Determining whether upgrades or bug fixes are required:
- What criteria will your organization use for determining this to ensure that it is minimally disruptive to the organization, but still gaining benefit of upgrades/bug fixes when necessary?
- Upgrade process /bug-fix process:
- Who will be responsible for making sure that this is executed successfully at your organization?
- What will the process be?
- What type of test hardware is required to do acceptance testing on an upgrade/bug-fix?
- What kind of user acceptance testing and training will be done for upgrades?
- Hiring/staffing to support this function
- Documentation
Determining future needs in Mifos product
Bug fixes
- Process for communicating bug fix needs to the Mifos community
- Process for having bug fixes made
New features and enhancements
- Process for requesting new features
- Process for working with Mifos community to have new features built
New reporting requirements
- Process for determining requirements for new reports
- Process for having new reports added into Mifos