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.
$10,000
per year
Upland PSA
Score 5.8 out of 10
N/A
Upland PSA helps professional services teams grow their business.
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.
We have discovered over the last few years using Tenrox that we could adapt our needs or processes to fit in the Tenrox box rather than adapting Tenrox to fit in ours completely. I feel like Tenrox would be better suited for a company that has fewer clients and projects over the course of a year, as well as fewer users. We have approximately 350 clients, 21,077 projects in Tenrox at this exact moment (we close projects as we can), 188 active users currently, and 415,635 tasks (some of course assigned to now closed projects). With this much information hosted through the Tenrox cloud server, we experience increased lag time frequently. This causes a lot of unwanted rejection towards Tenrox in our company.
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.
We love that our timesheets are pre-populated with all our employee's assigned contracts and we get to control what is on their timesheet as far as funder and contract codes.
Tenrox did very well with our integration and getting a timesheet that exports well with our payroll provider.
Tenrox has a great email reminder system for when people need to submit or approve timesheets.
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!
Tax calculation per state tax rules. Tenrox's current capabilities relative to tax codes is extremely limited and we have to do several time-consuming work-arounds in order to apply the tax as needed for our business. What is particularly frustrating about this aspect is that our need is based on tax laws and codes set by states and I feel a financial system should be able to sufficiently structure for legally-defined tax codes.
Tenrox Project Planning add-on module. This portion of the system has never worked as seamlessly as you would assume given they were designed to work together. We've run in to many bugs and just oddities over the years. It's very finicky in my experience. We only use TPP for a small portion of our projects - those being our smaller or need to have huge task lists per client naming requirements.
(The bad that became the good!) In the past, we have had significant customer-service challenges with Tenrox and then Upland, however over the past several months we have noticed a marked change in this. If we had not previously experienced issues with the customer service, I would not have any issue with the level of service that we are currently receiving. Given the history, I am cautiously optimistic that our current level of customer service will continue. I think our service concerns finally reached the 'right' people and I am reasonably confident the positive changes are here to stay!
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.
I am not in charge of renewing the Tenrox contract. However, if it was up to me, I would renew in a heartbeat. Tenrox is an asset to our organization and it keeps us focused. I am not aware of other products similar to Tenrox that provide the depth that they do.
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 feel like if the user interface could combine time and expense for users to be entered on one screen rather than two completely separate locations it would greatly improve usability. If the expense entry process could be improved completely, it would greatly improve the usability as well. Everything else within Tenrox, makes everything very user friendly.
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.
The support team is always very helpful and strives to ensure they have met your needs and corrected your issues in a timely manner. If they need more information or cannot recreate the issue themselves, then they will follow-up to gather the necessary data themselves. They are constantly striving to meet the needs of all users and understand so many different industries and types of environments out there, it is very impressive.
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.
The main thing with implementation is to make sure you have taken full advantage of the "sandbox testing" site that Tenrox provides to you during development. Try out every scenario you can think of, have other people enter information if needed, so that you can make sure you have not missed any big items. If you have the opportunity, roll out implementation to small groups of users. Depending on how your company is set up, I would choose groups that are not all in the same department so that you can address questions across all areas before adding in more users in the next wave of implementation.
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.
The Tenrox software looks and feels older and is not as user friendly! Harvest, for example, is an upgraded version that is easier to track and compile. This is what I'm comparing it to and it's not even close! We only selected Tenrox because it was cheaper and we had a connection in the company with someone at Tenrox to use that platform. We are currently looking for a change.
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.
Tracking, tracking, tracking. It keeps the data we need and gives us the ability to look at it in countless different ways with just a few clicks, which is a big time saver. Without Tenrox, we would definitely have to increase our headcount in order to accomplish billing and payroll.
We recently were able to automate a huge portion of business that was still (yes, still in 2014!) being managed out of an Excel spreadsheet. We experienced a great deal of resistance to the change with our own employees, however now that we have it going we have cleaned up our invoicing and impressed the highest-financial officer for two consecutive months - our first/only two months billing directly from Tenrox for that group.
A newer development for our team - Some client managers in the other divisions our company have begun to look at what we are able to do with Tenrox and our other primary system and get some of their work moved over to our group. This is great and is giving us new opportunities - we will likely need to increase the headcount of our admin. team, but for a good reason (too much work coming our way!).
