BWise vs. Jira Service Management

- What does our organization aim to achieve with the application? - Who will be using the tool? - How mature is our organization in the areas/processes that will fall in scope? - Are our areas averse to change? - How flexible and prone are our areas to modify their way of doing business and processes/procedures to accommodate BWise? - After implementation, who and how will perform application maintenance and change management (e.g. how easy will it be to update user privileges, central catalogs, assessment configurations, etc).

Incentivized

Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up

• Great reporting tool (uses SAP Business Objects). It is quite flexible on types of reports that can be created and supported. Also the reporting consultants are very competent and nice.
• Highly customizable solution: almost everything can be tailored to an organization's needs, assessments, audits, issues, recommendations, tasks, etc. However, there's a trade-off between customization and the integration of different areas of the organization.
• Increases visibility and efficiency in the organization. BWise offers centralized repositories (catalogs) that can be easily accessed and used by everyone in the organization (e.g. Process catalog, Policies and Procedures catalog, Risks, Controls, Laws catalogs, etc.). Also, the application allows findings on controls tested by Audit to be automatically reflected in controls monitored by SOX for example, without the need for SOX to retest them. So one area can leverage on the work of other areas increasing operational efficiency.
• Increases integration and avoids silos. By choosing the correct design (e.g. Risk Workshops instead of Open Assessments), one area can see and benefit from another areas' work. An example was mentioned above; another would be Operational Risk area considering the results of Business Continuity, Vendor Management, Info Security, etc. assessments when carrying out theirs. Additionally, processes can be integrated: when contracting a new vendor for instance, one can include questions about data confidentiality and usage of models in the Vendor risk assessment. Answers to these could then trigger Info Sec / Model Risk assessments.
• Increases accountability. Application provides full audit/change log with the type of change, name of executor, and date of change.
• Easier follow-up. BWise sends automatic emails with reminders to the people required to take action on an issue, assessment, etc.

Incentivized

• Highly configurable Notification Scheme, allowing free customization on who receives notifications and when
• Ability to add extra features through the highly diverse Atlassian Marketplace.
• Simple and highly customizable ticket interface. The Software can be almost completely branded in every aspect to represent your organization.
• Integration with Jira Software allows support tickets to be moved into other Log Term projects as necessary.

Incentivized

• Integration with SAP for continuous control monitoring.
• Control mapping to standards: ISO; COSO; COBIT; HIPAA; SP800_53 (NIST); FedRAMP; PCI_DSS; BITS; GAAP; AICPA; BSI; CCM; COPPA; CSA
• Surveys.

Incentivized

• Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
• The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
• It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.

Incentivized

BWIse is very flexible, and an affordable GRC tool.

Incentivized

I found BWise to be very intuitive and user friendly.

Incentivized

I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.

Incentivized

BWise support is knowledgeable and responsive. Bug fixes and development are also timely and ongoing.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

The main issues were managing the internal conflicts and competing objectives, rather than the capability and implementation of BWise itself.

Incentivized

Wasn't personally involved in the vendor selection process. I am aware that one of the main drivers for selecting BWise was cost (I believe BWise total project cost was several times lower than MetricStream's).

Incentivized

We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.

Incentivized

• Increased employee efficiency especially considering incident management and follow up.
• Increased visibility and senior management information/awareness.
• Increased employee accountability.
• Reduction of silos.

Incentivized

• It has allowed us to take on a larger volume of work at a faster pace.
• We have established best practices with the tool that we have taught and sold to clients.
• It has allowed for further collaboration with a larger team.

Incentivized