Akamai Technologies, headquartered in Boston, offers a Akamai: a content delivery network (CDN).
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.
Akamai is a well-established brand name with a great product. It meets and many time exceeds the needs for global content delivery and security management layer at the edge. Fine grain security tuning seems cumbersome as the definition of the app keeps changing. It also requires an investment of time for the setup which doesn't necessarily make sense for smaller scale scenarios. Some products offered by AWS, Azure or the Google Cloud can be more tightly integrated with cloud provider offerings thus easier to configure.
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.
Content offloading - once rules are set up within Akamai you don't need to even think about how many images or large JavaScript or CSS files (for example) are being served from your own estate, Akamai takes care of it all via rules that are quick, easy and flexible.
Page caching - for pages that don't change very often Akamai allows you to set up rules, quickly and easily, to serve up your page content for you, which takes even more load away from your origin servers.
Quick rollback - the Akamai system allows easy testing of rules and changes via a staging system, and also offers a quick rollback option, which is perfect for the rare occasions when something has been set up incorrectly.
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.
The interface in their control centre could be a bit more user-friendly with some of the settings in places that you wouldn't expect them to be. The search offsets this problem to an extent but it's still sometimes slower than you'd like to find what you are looking for.
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.
Their support documents are excellent and provide a lot of useful information for all their services. The only reason I didn't give them a 10 is that the time it takes for them to respond to an issue could be slightly faster.
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.
We've used -- and considered -- a whole number of CDN offerings. The good news is that almost all of the CDN products on the market are terrific, and will pay for themselves via increased customer satisfaction and lower monthly hosting bills. For some cases, we're still more likely to suggest CloudFlare (which has a free tier) or an integrated offering from a cloud provider, like Cloudfront.
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.
Akamai RoI improved over a period of times since it comes with heavy costs, however global deliveries in over 100 counties and global web platforms usage helps improve RoI
With the complex UI challenges, ROI could be impacted negatively when you have to invest in operations and time.
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.
