Concrete CMS (formerly Concrete5) is a free and open source, PHP built content management system for content on the web and also for intranets. It is optimized to support the creation of online magazines and newspapers.
N/A
ServiceNow IT Service Management
Score 8.4 out of 10
N/A
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
Pricing
Concrete CMS
ServiceNow IT Service Management
Editions & Modules
No answers on this topic
Starting Price
$10,000.00
per year
Offerings
Pricing Offerings
Concrete CMS
ServiceNow IT Service Management
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Concrete CMS
ServiceNow IT Service Management
Features
Concrete CMS
ServiceNow IT Service Management
Security
Comparison of Security features of Product A and Product B
Concrete CMS
9.5
38 Ratings
15% above category average
ServiceNow IT Service Management
-
Ratings
Role-based user permissions
9.538 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Concrete CMS
9.7
33 Ratings
23% above category average
ServiceNow IT Service Management
-
Ratings
API
9.731 Ratings
00 Ratings
Internationalization / multi-language
9.730 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Concrete CMS
8.4
42 Ratings
8% above category average
ServiceNow IT Service Management
-
Ratings
WYSIWYG editor
9.342 Ratings
00 Ratings
Code quality / cleanliness
10.037 Ratings
00 Ratings
Admin section
10.040 Ratings
00 Ratings
Page templates
10.040 Ratings
00 Ratings
Library of website themes
4.238 Ratings
00 Ratings
Mobile optimization / responsive design
9.739 Ratings
00 Ratings
Publishing workflow
7.737 Ratings
00 Ratings
Form generator
6.639 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Concrete CMS
6.9
40 Ratings
7% below category average
ServiceNow IT Service Management
-
Ratings
Content taxonomy
8.939 Ratings
00 Ratings
SEO support
9.039 Ratings
00 Ratings
Bulk management
6.039 Ratings
00 Ratings
Availability / breadth of extensions
5.439 Ratings
00 Ratings
Community / comment management
5.439 Ratings
00 Ratings
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
Concrete CMS
-
Ratings
ServiceNow IT Service Management
8.8
68 Ratings
7% above category average
Organize and prioritize service tickets
00 Ratings
9.967 Ratings
Expert directory
00 Ratings
8.051 Ratings
Service restoration
00 Ratings
7.956 Ratings
Self-service tools
00 Ratings
9.965 Ratings
Subscription-based notifications
00 Ratings
8.963 Ratings
ITSM collaboration and documentation
00 Ratings
9.060 Ratings
ITSM reports and dashboards
00 Ratings
8.162 Ratings
ITSM asset management
Comparison of ITSM asset management features of Product A and Product B
Concrete CMS
-
Ratings
ServiceNow IT Service Management
8.3
61 Ratings
1% above category average
Configuration mangement
00 Ratings
8.060 Ratings
Asset management dashboard
00 Ratings
8.159 Ratings
Policy and contract enforcement
00 Ratings
8.952 Ratings
Change management
Comparison of Change management features of Product A and Product B
Suitable if you are part of small to large scale companies or web-houses which have PHP developers and frontend engineers with some budgets. [Also suitable if] you or your client want to build a website that requires some features or uniqueness [and needs] some customization and freedom. Additionally suitable if you want this project to be DevOps based project or if the project requires very tight security and is inside of a closed network.
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.
As a dev, the Page object (coupled with page attributes, nav menus and page lists) makes structuring a website or web app a dream. The separation of page templates from page types also helps, the former being about layout while the latter is more conceptual.
As an admin, you pretty much have as much control as the developers of the site decide to give you.
The versioning system allows admins to roll changes back and work on changes before publishing them.
The permissions system is exceptionally powerful, allowing roles and/or individual users to be included or excluded from each permission.
The attributes system allows pages, files and users to be given custom properties of various types (e.g. text, image, colour).
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.
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!
Its a very solid, very consistent package that never lets you down or leaves you frustrated. It gets a 10/10 because its so much better than anything else currently available. It also gets a 10/10 because, even if not compared to others, it does not leave you wanting for features or functionality. It is an excellent piece of software that will answer almost every CMS need.
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 have used it on over 30 projects in the past 3 years and it's still a pleasure to work in. Doesn't always have all the answers, no CMS does, but I still find it very easy to use from prototyping to working to final project. Also there is no problem working on a localhost then moving to a live site, like there is with WordPress. It's my go to app in my CMS quiver.
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.
Since it's not tied to a central server (other than for authorizing updates and assigning licenses to specific sites), it's available pretty much 100% of the time.
The site works extremely well, the front end flies, searches and form submissions are very fast indeed. The reason its a 9 not a ten? the back end can be a little slow at times, and this is unfair, because for the backend to be so amazing, it has to do a huge amount of work!
Concrete5 is open-source and has an incredibly strong, polite, and supportive community. You can get an answer to nearly anything you want to do with Concrete5 by googling for it, searching the Concrete5 discussion forums or stack overflow, or posting your question to the forum. Members are very courteous and do not look down on those with less knowledge. And answers are always quick, informative, and supportive.
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.
Build off of an existing theme to speed up the creation of custom designed themed. Bootstrap is a good one but there are many others that are probably much simpler to build from than the Bootstrap one was. Make sure you host on a Unix/Linux server so you don't have to install PHP or MySQL separately. It's just smoother on those platforms.
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.
WordPress at the time was riddled with security breaches in the news and while Concrete5 was smaller (and therefore a smaller attack vector), after eleven years of use, Concrete5 has only had one published incident with an add-on that resolved within hours and with excellent communication. You can talk to the CEO and the CTO (or the rest of the team). They are very engaged and you're working with a small company of people who care, not a call-center with people just waiting to go home.
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.
Concrete5 is the customer-facing side of our business. It's where we host the site that potential customers see before they choose to purchase and create an account with us. We are able to keep that site clean, user-friendly, and with a lot of available options for customers to interact with thanks to Concrete5
The ability to have multiple users and admins for the site means that we all members of our team can go in and create new content, fix or troubleshoot issues, and edit the site easily.
Our CRM isn't directly integrated with Concrete5, so when customers go to make a purchase with us, they have to leave our Concrete5 site.
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.