Oracle Fusion Cloud PLM is a collaborative platform that helps users bring product ideas to market faster by standardizing and structuring the data and processes that go into innovating, developing, and commercializing products and services. It includes the capabilities of the former Agile Software Corporation, acquired by Oracle in 2007.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
ServiceNow is a fast-growing service management provider that went public in 2012. Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management, and (on the higher tier ITSM Professional plan) ITAM and software asset management.
We use Oracle Product Hub Cloud to manage our supply chain and increase productivity. This is an awesome tool to manage our customer database and reduce unwanted costs of product management and shipping. The way this tool is designed is really amazing because we can create a product easily and we can streamline ERP and our supply chain.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
Products and requirements are growing more complex than ever. Oracle's Agile Product Lifecycle Management helps you innovate profitably, with the broadest and most comprehensive solution to efficiently centralize product data, streamline processes, and launch quality products faster. Agile PLM is a strategic approach to managing the lifestyle of a product throughout its full value chain from initial requirements gathering through to design, prototyping, obtaining certification, product customization, service and retirement. Agile PLM emphasizes process efficiency, cross-functional collaboration in the extended enterprise, rapid innovation, rigorous quality control, risk mitigation, and cost-effectiveness.
The aspects that I like of Oracle Agile Project Management is that it helps foster collaboration between internal team members and vendors. All of our processes are documented on the platform, and the platform helps increase accountability across all internal teams. Collaboration is great in this tool.
Oracle Agile is a good product lifecycle management (PLM) software tool/database. Oracle Agile PLS is overall and for the most part, easy to use and has the ability to be customized and is able to provide visibility into the data that was entered into the database. This tool allows cross-functional teams to work on the same task at the same time, which is great when working remotely and/or working on an all remote team. Overall, this tool helped to accelerate product review, approval, and ultimately launch of new materials, therefore maximizing profitability and enhance product features and design as needed. The database is easy to use and does not require much training for someone who is technically savvy with other similar databases, and/or have used them in the past.
There lots of functionality and features in this product which gives you, as a company, great benefits to be able to manage your products portfolio. Easy to document products and have a way of looking up a product history and quality issues in the past. Better teamwork with pair engineering and co-located teams. Less documentation to restrict creativity, less time spent doing blind research, testing and feedback speeds up learning, and smaller more rapid improvements.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
Agile PLM does not let us keep workloads properly balanced if we want to use more than one virtual network (VCN, specifically), forcing us to work with a single network in which we manage the different levels of the work infrastructure. Although this is a drawback, it has helped us to adapt to more centralized methodologies.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
While considering oracle Product Hub Cloud, the most thing which attracted me toward it is that it provides a single, Best in class data management to deliver master product record that threads business process including cross chain compliance product introductions although it hasn't built a cloud product that the general market is looking for.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
