I like that MUNIS supports our full P2P process flow from requisitioning through check printing. THe system allows for us to manage contrats, purchase orders, p-card statements, and the city's vendor and item files.
A number of areas need improvement:
- Programming standards needs to be implemented and made consistent throughout the solution. Functionality does not always operate consistently from one program to the next
- Tyler needs to take a much more aggresssive approach to testing their products and updates/MUNs/fixes prior to deployment. Regression testing could find some significant issues without requiring the user community to identify and report issues (thus having to actually experience the issue)
- The user experiene could be significantly improved. Many processes are still very time intensive and manual. Focus on compliance and lega requirements first and foremost, but then on ways for the user to get their job done that don't hamper productivity
- The user groups could be a GREAT tool for future development ideas, but instead are run in such a way that there is little time (or room) for that
- Upgrades: - clients need a full, comprehenisve, and specific overview of ALL changes during each upgrade, including training materials, and screenshots. Often times we find that the upgrade notes don't cover everything and our users are confused by new or modified functionality, leaving us all scratching our heads.
Strongly consider the ability of your internal resources to support the system. It requires significant commitments in terms of administration, training, and user resources to run effectively.
Effectively tying requisitions/POs and P-card purchases to contracts
Monitoring Contract SPend
Monitoring Project Spend across multiple depts/contracts/users
More visibility on overall spend and trands (needs more details line level reporting though)