From Aspen to Kingston: The History of ServiceNow Versions

ServiceNow takes product updates pretty seriously, and has released new and improved versions of its software periodically since Summer 2007. The names of these updates once revolved around the release date, but following the Aspen update in 2011, new versions of ServiceNow have been inspired by famous cities and locations.

For ServiceNow veterans looking to take a trip down memory lane, or new users hoping to study up on the platform’s legacy, here is a breakdown of the history of ServiceNow updates, with release notes on each of them:

ASPENDecember 2011

With Aspen, the emphasis was on ensuring a robust, scalable system.

New project management templates were added, while Gantt charts

introduced as new features.

GENEVADecember 2015

While the Fuji update massively increased the functionality of the

ServiceNow platform, Geneva was a version focused more on an improved

UI for a more engaging overall experience. It also introduced native applications for both Apple iOS and

Apple Watch, a massive breakthrough in making the platform truly remote.

DUBLINNovember 2013

The Dublin released enhanced the features introduced by Calgary, with the application creator tool receiving a welcomed overhaul. The new HR

Service Automation application further expanded the ServiceNow portfolio

beyond that of IT service management.

JAKARTAJuly 2017

ServiceNow is no slouch when it comes to machine learning, and the Jakarta version debuted the much-anticipated Intelligent Automation

Engine. This proved to be a decisive move for ServiceNow, as they began the journey towards transforming IT

HR Service Management was also renamed HR Service Delivery,

accompanied by a massive increase in functionality.

BERLINJuly 2012

The Berlin update was actually in response to user feedback from the ServiceNow community. As a project

management system, it was important

management styles, such as the agile methodology.

HELSINKIMay 2016

Modern consumers want a quicker service than ever, and the Helsinki update took a customer-focused

approach that greatly improved self-service portals. It also introduced

to encourage real-time collaboration between development teams.

EUREKAMay 2014

Eureka, named after the Californian city, was intended to improve the overall user experience with an aim to make the platform more accessible. With a new demand management tool and

facilities service automation, Eureka’s goal was to open up ServiceNow as an option to manage all aspects of a

business, not simply IT delivery.

KINGSTONJanuary 2018

The Jakarta version, and its emphasis on machine learning, really unlocked the potential of data analytics inside

ServiceNow. However, Kingston’s Agent Intelligence application took that to the next level. The update also made the

much simpler for non-developers, making the ServiceNow platform

without a technical background.

CALGARYFebruary 2013

Having established itself as the go-to product for IT Service Management, ServiceNow aimed to move beyond

just the IT sector with the Calgary release. A new collaboration

workspace allowed users to track live tasks in an easy-to-navigate interface, while the iPad view was also greatly

improved.

INSTANBULJanuary 2017

With the Istanbul version, ServiceNow aimed to help businesses transform by introducing a change advisory board workbench, as well as a governance, risk, and compliance feature. Cloud

improve navigation across multiple ServiceNow products.

FUJIMarch 2015

While previous product updates were

release was a game changer. The 10-month development cycle was fully utilised, with Fuji introduced a

host of new applications to align with

model; Service Taxonomy, Service Experience, Service Delivery, Service

Assurance, and Service Analysis.

ASPENDecember 2011

With Aspen, the emphasis was on ensuring a robust, scalable system.

New project management templates were added, while Gantt charts

introduced as new features.

GENEVADecember 2015

While the Fuji update massively increased the functionality of the

ServiceNow platform, Geneva was a version focused more on an improved

UI for a more engaging overall experience. It also introduced native applications for both Apple iOS and

Apple Watch, a massive breakthrough in making the platform truly remote.

DUBLINNovember 2013

The Dublin released enhanced the features introduced by Calgary, with the application creator tool receiving a welcomed overhaul. The new HR

Service Automation application further expanded the ServiceNow portfolio

beyond that of IT service management.

JAKARTAJuly 2017

ServiceNow is no slouch when it comes to machine learning, and the Jakarta version debuted the much-anticipated Intelligent Automation

Engine. This proved to be a decisive move for ServiceNow, as they began the journey towards transforming IT

HR Service Management was also renamed HR Service Delivery,

accompanied by a massive increase in functionality.

BERLINJuly 2012

The Berlin update was actually in response to user feedback from the ServiceNow community. As a project

management system, it was important

management styles, such as the agile methodology.

HELSINKIMay 2016

Modern consumers want a quicker service than ever, and the Helsinki update took a customer-focused

approach that greatly improved self-service portals. It also introduced

to encourage real-time collaboration between development teams.

EUREKAMay 2014

Eureka, named after the Californian city, was intended to improve the overall user experience with an aim to make the platform more accessible. With a new demand management tool and

facilities service automation, Eureka’s goal was to open up ServiceNow as an option to manage all aspects of a

business, not simply IT delivery.

KINGSTONJanuary 2018

The Jakarta version, and its emphasis on machine learning, really unlocked the potential of data analytics inside

ServiceNow. However, Kingston’s Agent Intelligence application took that to the next level. The update also made the

much simpler for non-developers, making the ServiceNow platform

without a technical background.

CALGARYFebruary 2013

Having established itself as the go-to product for IT Service Management, ServiceNow aimed to move beyond

just the IT sector with the Calgary release. A new collaboration

workspace allowed users to track live tasks in an easy-to-navigate interface, while the iPad view was also greatly

improved.

INSTANBULJanuary 2017

With the Istanbul version, ServiceNow aimed to help businesses transform by introducing a change advisory board workbench, as well as a governance, risk, and compliance feature. Cloud

improve navigation across multiple ServiceNow products.

FUJIMarch 2015

While previous product updates were

release was a game changer. The 10-month development cycle was fully utilised, with Fuji introduced a

host of new applications to align with

model; Service Taxonomy, Service Experience, Service Delivery, Service

Assurance, and Service Analysis.

VERSION HISTORY