4 out of 5.0, Reviewed Jun 24, 2016
1. Clear ownership and accountability for implementation and ongoing investment/maintenance/governance. 2. Have your end reporting needs understood.
Integration of data elements across the platform. Ability to configure based on our methodology while being able to maintain an upgrade path.
User interface out of the box is not intuitive for the non-risk professional. Lack of product support for release management/upgrades.
Appropriate skillsets and understanding of the product in the local market to support our ongoing investment.
1. Don't build solutions on untested concepts or inefficient processes (clarity in methodology). 2. Confidence in data quality and integrity from legacy systems. 3. A structured and sustainable training model for end users.
4 out of 5.0, Reviewed Jun 22, 2016
Keep the install and subsequent modifications as vanilla as possible, while ensuring that staff are allocated and trained for supporting workflow changes and other manageable modifications as needed.
1) The integrated approach to GRC and the system structure that provides for building the relationships between business entities, processes, risks, and controls. 2) The product development and improvement focus on the vendor. 3) The product support team do a great job - very responsive. 4) The vendor's focus on emerging technologies and risk industry needs for product improvement.
1) Seemingly frequent changes within the vendor organization on client relationship management. 2) Some of the system administration maintenance functionality is a bit cumbersome to use. 3) Inability to compete in the IT risk and security space, creating the opportunity for clients to feel the need to introduce other GRC technologies to work alongside GRC OpenPages.
Have better intel and understanding of what the competition is doing in GRC in order to develop competitive functionality and ease of deployment in OpenPages, and drive to top of the market product capability.
1) Develop and maintain management expectations, budget, and resources to ensure that all new releases and fix packs are installed as released and available. 2) Allocate resources and funds to ensure that Cognos report development skills with specific OpenPages knowledge are onboard.
3 out of 5.0, Reviewed Jun 14, 2016
Provides almost too much customization capability. Workflow not the easiest to use. Absolutely need a third party to assist with use cases and functionality.
Hire solution experts who really know the tool.
Consider the users of the system, not just the consumers of the info/data being input.
Make selection process more rigorous and consider IT Risk as well as Operational Risk.
Utilized phased approach introducing different GRC modules over a period of time.
4 out of 5.0, Reviewed Jun 13, 2016
Know what methodology you want to implement but be open to other possibilities that automation brings.
The product is exceedingly flexible.
Reporting via Cognos is so complicated. We are struggling to find a simpler reporting tool for our end users.
Tell us the pros and cons of changes or features we wanted to implement before we went ahead. Be more transparent.
Two thoughts - 1. Reconsider our current methodology and perhaps not try to shoehorn it into the system. 2. Consider following a more Agile Implementation method allowing us to learn from our mistakes sooner and make fewer of them later.