IFS Applications is presented by the vendor as an agile application suite that offers enterprise resource planning (ERP), enterprise asset management (EAM) and enterprise project management, handling 4 core processes: Service & Asset Management Full Enterprise Asset Management (EAM), Maintenance Repair and Overhaul (MRO) and Field Service Management (FSM) Manufacturing Enterprise Resource Planning (ERP) with support for process manufacturing, discrete manufacturing…
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.
Order to cash processes and scenario are implemented natively in IFS. An HR module exists for career management also (objectives, comportments, training, mobility) but may be improved in terms of workflow validation (e.g. training to validate by a manager) or reporting.
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.
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 speed of bug fixes should be improved by the IFS after sales teams. We saw the difference of responsiveness prior to Go Live and after Go Live, with a change of teams. IFS France is working on that point, and strategically wants to innovate by acting now with two other third-party companies in early 2017, to improve the after sales experience for customers.
There is no license model between the full licenses, which gives access to all IFS features, and the light licenses, to get access to a specific module like expense sheet. As a consequence, you must acquire a full access license for one team working only with a dedicated module (e.g. general ledger). Maybe an intermediate type license would be welcome to balance the budget. IFS tries to make prices competitive but you have to consider full upgrades of the product too, where requiring full licenses can be hard on the budget.
When you have an Active Directory ecosystem with a trust relationship, users from domain B can't natively access IFS, even if AD sync is in place with domain A. It's important to improve that functionality because many companies have a merge and acquisition context, with SOX constraints sometimes, and avoiding maintaining contacts or local accounts simplifies SOX compliance, or to management of accounts within the company.
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.
We have been unable to get answers to our questions, solutions to our problems, and they don't seem interested in working in the construction industry.
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.
Microsoft AX, QAD (in continuation of our previous ERP), Sage X3 was an out of the box ERP that was part of initial RFP. We have chosen IFS based on the compromise between costs & budget, functionality, technical features, and feedback from similar customers that gave their feedback. The project manager team and qualification level of technical or consultant teams were differentiating factors too. Finally IFS application was named in the Gartner’s mid-market ERP Magic Quadrant, along with SAP, and helped us to finalize our choice
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.
Reporting is now centralized and managed. Previously, reports were outside the information systems and there was a risk of incoherence.
Accounting controls are now in place on the overall processes, including production, which helped the company to reduce closing periods or to produce more easily official mandatory accounting files yearly.
Interfaces between the CRM forecast tool and IFS helped to keep the tools in sync, and to decrease the processing times prior to production launch.
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.
