THE GUIDE TO A SUCCESSFUL SERVICENOW® IMPLEMENTATION

TABLE OF CONTENTS

Before You Start

Planning Your Strategy

Begin Building

Quality Assurance & Testing

Deploying & Training

Maintenance

About the Author

01

03

08

15

18

22

26

CHAPTER 1: BEFORE YOU START

Starting a ServiceNow implementation is no minute task. While ServiceNow may be an extremely expansive and all-inclusive offering for your business, you need to be aware of what the implementation entails.

Keep in mind that many ServiceNow implementation failures stem from not paying attention to both processes and requirements, not the software itself.

WHAT IS ITSM?ITSM, or Information Technology Service Management, is a set of activities that are organized, directed, and structured procedures performed to plan, design, deliver, operate, and control IT services offered to customers. More often than not, ITSM refers to the software utilized to contain all of these processes.There are many different ITSM products on the market—ServiceNow being the largest, by far.

ADVANTAGES OF AN ITSM PROCESS

» Can help to standardize processes across the company » Boosts productivity throughout

the organization due to reduced

manual processes » Reduces operational costs

1. Enables IT operations metrics to be tracked and measured » Improves customer service and

customer experience » Encourages better collaboration

between teams and departments » Disadvantages of an ITSM Process » If not executed correctly, can be

very difficult to utilize » Too many processes to

implement, too little time » Has a learning curve, may be

difficult to understand at first » Lack of adoption among seasoned

employees » May need regular maintenance to

prevent becoming obsolete

CONSIDER YOUR TIMELINEAnother key factor of a successful implementation is to remember that these things take time. An average, simple implementation can take anywhere from 8 to 12 weeks, whereas more in-depth ones can take longer. What is your target deadline to do the switch? Is it feasible? Will you have the manpower to achieve your goal?

BEFORE YOU START

02

CHAPTER 2:PLANNING YOUR STRATEGY

You have done enough research on the product to be confident it is right for your team and you’re ready to jump into ServiceNow, now what?

First, look at your existing processes. Do not forget to also solicit feedback from those that will be using the service every day and ask them these questions:

1. Which of your current processes work? How does that fit into a new strategy?2. Why did your current process fail?3. What is causing you to make a switch, and why? **4. Which aspects of your process need improvements?5. Will this new process be more efficient and/or cost-effective? If not, can you explain why you are changing platforms?

SELECTING THE RIGHT TEAMThe next step—and quite possibly the most important—in your new implementation is finding the right people for your new ServiceNow team. You will, at the very least, need:

» Business Analyst and/or Project Manager » All stakeholders in the process » At least one ServiceNow Certified

Implementation Specialist or System Administrator » Quality Assurance Tester(s)

Why Do I Need a Business Analyst?You may consider to opt out of having a project manager or business analyst on your team. This is fine if you have a very small organization of less than 10

PLANNING YOUR STRATEGY

** Make sure this is an elaborate answer.

Think about someone who has never taken a step into your office before and is looking to streamline your processes. This person is ServiceNow, and your thoughts need to be concise about it.

04

individuals. However, if it involves a more diverse team it would be best to have someone there to help keep everyone on track and on schedule.

You will need a BA/PM for a wide variety of tasks, such as scheduling, management, procurement, and analysis. They would also be the liaison between the stakeholders and the IT team, able to convert technological jargon to more commonplace terms.

ServiceNow Developer CertificationsWhile not technically required to implement a ServiceNow iteration for your business, it is very strongly recommended for the developer(s) that will be working with your implementation to have at least one ServiceNow administrator certification. We at V-Soft recommend having your developer(s) certified in ServiceNow Administration and ITIL, as well as having experience as a Business Analyst.

ServiceNow also provides many more certifications—most at a cost—to help you enhance your knowledge of the platform. They offer classes in Asset Management, Portfolio Management, Application Creation, and more. You can

check out their Training and Certifications page for more information.

SELECTING A PROJECT ROADMAPOnce you have your team in place you will need to create a plan of attack. Typically, this begins with understanding the needs of your company as a whole and addressing the processes that are lacking. Easier said than done.

It is always recommended to start with the base functionality as quickly as possible, wait a few months to get accustomed to the platform, and then add on any revisions in small increments with frequent backups. Check with your users to ensure that these revisions are agreeable, or where they see room for improvement. Don’t be afraid to restore from backups whenever you run into a process that simply doesn’t work.

Make a list of processes that will not work with an Out of the Box (OOB) ServiceNow implementation. Why will those processes not transfer? Remember that sometimes it is easier to relearn a process versus changing everything to try and get it to work the way you’re used to.

PLANNING YOUR STRATEGY

05

Make a list of the processes that will work with an OOB ServiceNow implementation. These will be the first ones that you should be able to start integrating.

CUSTOMIZATION VS. CONFIGURATIONWhile your ITSM project is meant to simplify the work of many, there will be some that are still set in their ways and will be resistant to change. This is where you will have to step in and justify configuration versus customizing the application to run the same way they’re already used to. If it is an ineffective and cumbersome process, consider reducing the customization aspect of it for a much more reasonable configuration.

REMEMBER, NO PROCESS IS PERFECTNot every process will work for your business. ITIL may be perfect for you, whereas COBIT may be better for your neighbor. There will have to be some tweaks along the way no matter the process, especially with training. Also keep in mind that people learn in different ways. One person may prefer to explore the new process themselves while others will require a detailed manual.

Because of this, you need to be aware of each person’s difference and avoid chiding them on the practice’s processes if they need a different approach to learning. The best way to work through this is keeping all diagrams simple, concise, and easy to understand.

PLANNING YOUR STRATEGY

06

COLLABORATION IS KEYIt is easy to sell upper management on the benefits of ServiceNow, but what about middle management—the ones that run reports, calculate costs, using the system on a daily basis, and managing finances? Their input is just as valuable as upper management’s. It may be a more difficult sell for them, but in the end it will be worth it. If you do not incorporate their help in the beginning stages and planning, you will likely be met with resistance, and ultimately, a lack of adoption.

Another part of collaborating with multiple levels in the hierarchical scare as well as across departments means that you will have your eyes opened to a plethora of things you otherwise would’ve never thought to consider. Something as minute as a suggestion box could be seen as nothing other than just another box to click on a page to you, but could mean the world for someone aiming to improve morale and employee satisfaction.

COMMUNICATION OF CHANGESOnce you have your roadmap in place you will want to start communicating these changes to all affected parties. Set up a frequent meeting to go over status updates, even if brief. Make sure that the following bullets are addressed before you begin implementation:

» What is the objective of this implementation? » Who is the target audience? What

are you communicating to them, and when? » Documentation of all actions,

including minute changes, must be completed

» Record who is performing these actions » Ensure that project teams

and service owners are involved in messaging, even if you have someone specific dedicated to messaging (i.e., marketing, training) » Plan how you are going to

implement training » Will it be a presentation over a

lunch, or a week long course? » Marketing before, during, and

after implementation is critical » Plan training appropriately; do

not have it too soon or risk retention rates to be low » Create after-the-fact training

materials to help jog users’ memories

ANSWER QUESTIONSThere are bound to be many questions from your audience during the transition. Some people will be ecstatic, while others will either be disgruntled or concerned. Be responsive. Ensure them of the benefits you will be receiving with a newer and more efficient process.

Just remember that 70% of a great ITSM platform’s development happens outside of ServiceNow.

PLANNING YOUR STRATEGY

07

CHAPTER 3:BEGIN BUILDING

CHOOSE THE CORRECT PRODUCT FOR YOUBefore stepping foot into the development of your new ServiceNow implementation, you need to be aware of which version will be most appropriate for you and your business. There are different features and functionalities in each version. Here is a brief overview of each type to get you thinking:

Service ManagementEnterprise-wide service management that utilizes the service model to many different use cases both inside and outside of IT. It includes domains such as HR, facilities, field services, and more to help manage all of the service relationships that make up your enterprise.

IT Service ManagementOffers a powerful platform for all ITIL processes for ITSM. ServiceNow ITSM helps you reduce cost, lower risks, improve business agility, and boost IT innovation. Easy upgrades and customizations allow organizations to focus on improving service experiences versus software upkeep.

IT Operations ManagementAlso called the ServiceWatch Suite, ServiceNow’s IT Operations Management includes CMDB, Incident and Problem Management, Change Management, and a robust Service Catalog. ServiceWatch is a very inclusive offering with flexible features to suit your business’ requirements.

BEGIN BUILDING

09

IT Business ManagementBetter manage demand, balance resources, manage agile and waterfall projects, perform budget planning, and map costs to technical business services with ServiceNow’s IT Business Management package. Align your IT department with the rest of your corporation with Financial Management, Project and Portfolio Management and Application Portfolio Management.

CORE SYSTEM SETUPThe core configuration can be configured in many different ways to address your organization’s needs. You can use it to create, manage, and distribute applications for your business. You can install any number of applications that are provided by ServiceNow, or even

create your own custom ones. These applications can be made available to specific users, roles, or companies. The system can also be configured to send and receive emails as a way to track service requests.

The primary administrator role, admin, has access to all system features and functionalities regardless of security constraints. Other administrators can be given rights to administer only certain applications.

To learn more about your core installation, you can check out ServiceNow’s Platform Documentation by clicking this link.

Please note that this information is relevant to the Istanbul release.

BEGIN BUILDING

10

HOMEPAGE OPTIONSWonderful, you’ve gotten your ServiceNow iteration and are ready to dive right in. The first place you will come to is the homepage, and it can seem quite daunting at first. Really, it is quite simple. Here are some of the options the Homepage will offer in a new installation:

BEGIN BUILDING

Ten Cool Things in Ten Short MinutesOne of the first things you will notice in your new implementation is a section called 10 Things. It will give you a rudimentary understanding of some of the processes that the ServiceNow platform can handle out of the box.

Guided SetupGuided setup is designed to make it easier for you to get up to speed on the ServiceNow platform. It includes a step-by-step checklist of things to implement and make sure you have readily available well before launch.

Business LogicThe business logic function allows an administrator specify the actions that the platform takes whenever specific events take place. Some of the business logic is set up for you, and you can edit existing rules or create rules.

Create and DeployAs the title suggests, the section Create and Deploy is for essentially, developing and activating an application for your ServiceNow instance.

Data ManagementThis is where you can set up and dictate how you want to have your data managed. The management functions available include importing, exporting, and archiving database data, as well as configuring fields and tables.

DiagnosticsProvides a diagnostic area to look for performance problems in your instance, as well as providing debugging tools.

11

EmailCustomize all inbound and outbound emails that are sent within the ServiceNow platform. You must have an administrator role in order to modify any of the email parameters.

HomepagesConfigure different portals, self-service homepages, and widgets depending on the user’s needs. You are also able to edit portal pages and create unique ITIL homepages for users.

IntegrationAllows you to integrate third-party systems and data sources into your ServiceNow implementation. The most common integrations are with CMDB, Incident Management, Problem Management, Change Management, User Administration, and Single Sign-on.

Reporting and AnalyticsThe Reporting and Analytics tool enables you to create visual representations of data, schedule reports, implement advanced analytics into your ServiceNow instance, and view or create new reports.

User AdministrationMuch alike any website that has logins, the User Administration tool is designed to maintain your users in a simple one-stop-shop. Manage user information, roles, groups, departments, or even companies in a centralized location.

User InterfaceChange the look and feel of your implementation, applications, or plugins. Gives you the ability to create visually appealing custom interfaces, tweak navigation panes, and even enable language translations for specific locations and users.

BEGIN BUILDING

12

CONSIDER PLUGINSPlugins are optional features that can be activated within a ServiceNow instance. There are plugins for many different types of processes and features, such as Asset Management or integrations with other platforms. The types of plugins that you will want to enable will vary greatly depending on your business needs. Even so, the most basic and common are automatically included in your ServiceNow instance, such as Problem Management.

The availability of plugins can range from free and easily accessible to by request only and several thousand dollars. Do your research before finalizing on a specific plugin, as well, as once a plugin is activated it cannot be disabled or deleted.

SDLC Scrum ProcessServiceNow offers a native scrum process plugin referred to as the Scrum Process Pack. The pack provides the ability to support several teams that are utilizing the scrum methodology.

Scrum is a repetitive and incremental framework for project management. It is often used in agile software development environments. Characteristics of scrum may include:

» A reoccurring sequence of events and milestones » A short, fixed schedule of

meetings with a flexible agenda referred to as Sprints to address rapidly changing development needs » Implementing and testing new

requirements, called stories, to

quality check work after each sprint. » Unique terminology to refer to

individuals participating: scrum team, product owner, scrum master, and development.

A major benefit of the plugin is how it is capable of using data that is already in the ServiceNow iteration’s database, such as configurations and user information. Scrum activities can also be tied into ITSM processes such as Incident, Problem, and Change Management.

If you would like to learn more about the Scrum process for ServiceNow, you can go to ServiceNow’s Documentation listing on the Scrum Process here.

DAILY MEETINGSYour team should put at least fifteen minutes of availability on their calendar every day (or most days) to be able to discuss any changes that may have happened. These can be simple standing meetings where you can discuss changes in a quick manner or to keep everyone informed, but some of these meetings should take more time.

For example, if you only have weekly meetings and your developer has completed a specific change you’d requested the following day, they will have to wait almost an entire week to obtain feedback on this change. Your meetings should be as malleable to help processes flow along at their natural pace.

BEGIN BUILDING

13

BUILD IN ITERATIONSMost organizations start their software development with receiving a list of requirements for a given release or solution. Developers will then take these changes and include them in the software. Implementing ServiceNow in this traditional approach can take a great deal of time longer than anticipated when questions are asked, conflicts are challenged, gaps are discovered, and documents are updated. Some organizations even require their developers to document technical details in a breakdown list before they are even allowed to start the work. This process fails as most often developers don’t even have a precise solution until they have tried a few others to find what does and doesn’t work.

ServiceNow’s flexible architecture is capable of allowing developers to quickly build a prototype of their needs to see feasibility of the project. Because of this flexibility, it allows the developers to identify what processes they need to define, develop, review, or rework while refining their documentation. This gives them the opportunity to “design a little, develop a little, review, and repeat” until the process is completed.

With ServiceNow, it is often more feasible to break the process down into defined stages with reviews along the way than it is to define and document all of your requirements in one sitting. Delays

often do occur as developers discover bugs, issues in process, and conflicts. Instead of documenting everything at once, create a proof of concept draft and review them with those involved with the implementation and get an agreement on the process before moving on. By building everything in stages, you can discover and address issues more quickly.

By defining your needs, working in sections, and conducting evaluations after each one, it is easier to make adjustments in the development processes as well as the documentation. This makes it much easier to detect issues before they become serious. Because of the constant evolution of the project, meetings should be held frequently to prevent any delays.

CUSTOMIZATIONIf you’re not happy with the out of the box appearance of your ServiceNow implementation, you are able to manipulate it by changing the theme.

You can change the appearance for aesthetic reasons or to help distinguish it from other instances. For example, some organizations utilize multiple iterations of ServiceNow to separate customers to employees and development. To prevent a user from accidentally operating in the wrong instance, administrators can make each individual instance look visually distinct.

BEGIN BUILDING

14

CHAPTER 4:QUALITY ASSURANCE & TESTING

As the ServiceNow platform is very malleable, some things can be changed in a matter of minutes. However, any changes to a platform’s configuration can have some unintended consequences that can be potentially system-breaking. Fortunately, there are methods available to prevent this from happening. Here are only a few options that you have available.

TEST MANAGEMENTServiceNow offers a testing plugin called Test Management. You are able to activate it in one of two ways: either as an individual application, or as part of Project Portfolio Suite with Financials. The Test Management application provides a tool for manual software testing.

Test managers can use the tool to manage all phases of the testing process, such as:

» Creating and maintaining a test repository of test suites, cases, and tests » Generating test plans, adding

test cases, and assigning testers to specific test cases » Monitoring progress of the testing

process » Viewing and evaluating test reports

Testers can use the Test Management application to:

» Perform tests and record results » Update case status » Report defects as necessary

AUTOMATED TESTINGAutomated testing is the use of specialized software to control an array of different tests to simulate different incidents that a user may experience. The software

will automatically compare the actual outcomes versus predicted outcomes.

Having this type of testing can take care of some repetitive, but necessary, tasks in a formalized testing process already in place. It can also perform additional testing that would be difficult or labor-intensive to do manually.

There are several different types of automated testing, but the two approaches that are most common are:

GUI (Graphical User Interface) TestingA testing framework that replicates inputted data such as keystrokes and mouse clicks, observing the changes that result in the interface, to validate on whether or not the action and response of the program is correct.

API-driven TestingA testing framework that uses a programming interface to the application to scrutinize the behavior under test and determine if it meets expectations. As APIs lack a GUI, API testing is typically performed at the message layer protocol. It can also be testing public (usually) interfaces to classes, modules, or libraries are tested with a variety of input arguments to validate that the results returned are correct.

QUALITY ASSURANCE & TESTING

16

MANUAL TESTINGIf you prefer to do things yourself, or lack the funds to invest in a quality testing automation program, there’s always the option to provide manual testing for your ServiceNow implementation. Manual testing is where you have an individual, or group of individuals, manually testing software for defects. It requires the tester(s) to play the role of an end-user to verify that all functions operate as expected. The tester will often follow a written test plan that guides them through sets of important behaviors, or test cases.

Test CasesA test case is a set of conditions in which a tester will determine whether an application or one of its features is working as intended. It may take many test cases to determine whether or not a program is satisfactorily reviewed and given permission to be released.

Traceability MatricesA traceability matrix is a document or spreadsheet used to assist in determining the completeness of any two base-level reference documents by utilizing a many-to-many relationship comparison. It may be used to check if a project’s requirements are being met, to create a software requirements list, or project plan tasks. Typically, a traceability matrix is used for high-level requirements as well as detailed requirements of the project.

QUALITY ASSURANCE & TESTING

17

CHAPTER 5: DEPLOYMENT & TRAINING

Once the quality testing has been completed and you’re sure all of the bugs have been worked out, it’s time to officially go live. Your next task is to make sure that adoption of the process goes through without a hitch.

BUILD A GOVERNANCE PLANThere is no sense in building a new process if no one follows it. Because of this, you’ll want to create an action plan where users will be held accountable for the processes and use of the system. A process will naturally erode over time and eventually become abandoned if it is left ungoverned for a certain period of time, and we definitely don’t want to see that happen to our ServiceNow implementation.

GO-LIVE COMMUNICATIONSIt’s time to make Go-Live official. Create a communication list of things that you will want to send out to your users. This is the time to:

» Provide a highlight reel of new capabilities » Recognize those that have put

extra effort on the project » Employ “Power Users” within

specific groups that will help the rest of their group adjust to the changes » Announce a reward system for

utilization, if desired » Some examples are of first

person to successfully close a ticket, the first person to attach a knowledge article to solve a case/incident, or the use of the chat functionality » Create and deploy a brief

explanatory video that shows users the basics of the system, including step by step directions for setting up their account » Schedule a Q&A session (or

multiple) to answer any questions users may have » Address any concerns that end

users will arrive at

DEPLOYMENT & TRAINING

19

TRAINING BEFORE, DURING, AND AFTER GO-LIVETraining your staff on the new platform is absolutely critical. Never assume that any member of your team catches on right away and doesn’t need a how-to guide. It can be catastrophic and ultimately lead to abandonment of the platform if it is too frustrating to the end user.

Designate a member of your team or a group of members to be your go-to trainers that will be available to answer any questions a user may have regarding the platform. Train them intensively on ServiceNow’s platform and give them the resources they will need to educate others successfully.

PLATFORM TRAININGPlatform training is education on how to use ServiceNow’s features, or platform. It is not tied to a specific service or process. All users that will be utilizing the platform in some way—even if in intermittent, small amounts—should have this training. The basics should cover:

» Basic navigation » Reports » Application Navigator » Views » Bookmarks

PROCESS TRAININGAs processes are changing, it is critical to ensure that the users are properly trained on the new ones. This could include complicated integrations with other systems or services, such as payroll or incident management.

All of the users affected should be trained on the new version(s) of their processes. Ensure they are aware of what their responsibilities and expectations are with the new system and revisit as needed. Don’t forget to identify where any new forms of automation have been included to reduce strain.

END USER TRAININGWhile the end user’s experience should be intuitive and may not require training, providing them with an overview or guide can provide additional support to those who may not be comfortable with adopting a new process. Consider creating a step-by-step guide or prerecorded video with instructions on how to navigate the user portal.

SURVEYSSurveys are a great tool to assess adoption and feedback of your new platform.

» Consider the option to make them anonymous – you will get more honest feedback that way » Make them brief – less than 5

minutes is recommended » Keep them running throughout

the entire implementation cycle and then incrementally after launch (recommended 30, 60, 90 days, then every 6 months from there) » Follow up on survey responses!

Whether this be on a global newsletter or responding to an individual that has provided their contact information, it is important to make sure employees know they’re being heard.

DEPLOYMENT & TRAINING

20

MARKETINGMarketing should have a collaborative role in announcements and go-live messaging. They should also include similar materials to continually market the new platform as well as its improvements.

Advertising the success rates of other departments, creating infographics from the data that has been recorded in ServiceNow, promoting Lunch & Learns and webinars, and creating informational articles should be the marketing department’s responsibility at least in part.

If you are wanting to be more festive, consider memorabilia such as lanyards, stress balls, note pads, or water bottles to drive interest regarding the launch.

CELEBRATE!Congratulations, you have successfully deployed a ServiceNow implementation! It’s time to take a moment to sit back and relax before getting prepared for the next phase: maintenance and support. Remember to continue soliciting feedback from all users on the processes, performance, and features.

Having a party to celebrate Go Live is not uncalled for. It may even encourage users to try out the process more – themed, fun events can really ease users into exploration of the ServiceNow platform.

DEPLOYMENT & TRAINING

21

CHAPTER 6: UPGRADES & MAINTENANCE

UPGRADES & MAINTENANCEUpgrading is the act of moving to a release that is in a different family than your current release. Upgrading or modifying your ServiceNow instance requires planning, testing, and authentication. To make sure your upgrade goes along smoothly, you need to be sure to read the release notes, create upgrade plans, and test your upgrade on a demo instance of your iteration before upgrading your active instance.

HI SERVICE PORTALNew to ServiceNow with the Helinski release, the remodeled HI Service Portal is for maintenance of your ServiceNow instance. You can utilize the HI Portal to view and schedule upgrades, manage instances, open incident tickets whenever you need support for your instance, and more. It is effectively your go-to portal for all maintenance and upgrade related matters.

Note: Only customer administrators are provided with an account for the HI Portal. You are required to have at least one customer administrator for your organization at all times.

Manage InstancesView information about your instances, schedule clones, activate plugins, and request resets in the Manage Instances section. You are also able to request a VPN, a non-production instance reset, view issues and alerts, and more.

Manage UpgradesView, schedule, request, and cancel upgrades to your instance in the Manage Upgrades section for up to three of your ServiceNow instances.

Get HelpStuck somewhere on your instance? Reach out to one of ServiceNow’s talented customer support agents to get answers. If your matter isn’t as pressing, you can also visit the ServiceNow Community, where users not only socialize, but also help other ServiceNow Admins in need.

UPGRADING RELEASESThe release cycle is designed to maintain stability and quality with the flexibility to address problems immediately. Customizations are typically maintained

23

24

throughout upgrades. ServiceNow uses the term “family” for a group of features. A family contains a feature release that provides a new offering or functionality, or fixes to an existing functionality, or patches and hot fixes that will resolve issues that may arise.

Make sure you are aware of all of the changes in the upgrade you are looking into. Obtain all of the knowledge, tools, software, and resources you need before you begin the project. It is also important to understand how your current instance is operating and be aware of key functionalities. Dedicate resources and time for preparing, implementing, and testing any upgrades you may perform.

DIFFERENT RELEASE CONTENTSEach release “family” contains unique-to-them features, patches, and/or hot fixes. Release notes are available in the product documentation for all releases.

FeaturesA feature provides a new, unique offering that you can implement to add value to your implementation. These are often only available as part of a feature release. These features are production-oriented, meaning they have a high priority towards quality and stability throughout the life cycle of the product.

PatchesA patch supports existing functionalities with a collection of problem fixes. It does not generally include new features, only corrections to existing features.

UPGRADES & MAINTENANCE

25

Hot FixesHot fixes support existing functionalities with a targeted and specific problem fix. They may or may not include previous fixes for a given release, and often do not include new features or functionalities.

ROLLBACKS AND BACKUPSWhile planning on performing an upgrade, keep in mind that ServiceNow does not provide a universal rollback option. Rollbacks are available for upgrades within your existing family (i.e., Helinksi patch-to-patch or Istanbul patch-to-hot fix). The rollback window is 10 days by default; you can customize this window by modifying the glide.rollback.expiration_days property. To request a rollback, contact ServiceNow Customer Support.

Also, try to avoid restoring a production instance from a backup when possible, as it can cause unnecessary downtime and loss of data. When you have a problem that cannot be solved using other methods, consider restoring a production instance

from a backup a last resort. However, ServiceNow does provide 24/7 customer support for assistance with critical post-upgrade issues.

Please be aware that ServiceNow does not perform on-demand backups. Instead, instances are automatically backed up during slow business hours on set schedules that are defined by ServiceNow.

FINAL WORDSImplementing the ServiceNow platform into your organization may be time-intensive, but is most definitely doable with the right resources. It can be a very powerful platform with an unending amount of offerings when programmed correctly. If you have any further questions regarding how to properly implement a ServiceNow instance, feel free to reach out to one of our experts, free of charge. One of them will be happy to assist you in any way they can.

ABOUT THE AUTHORV-Soft Consulting is headquartered in Louisville, Kentucky, USA with strategic locations in North America and India. Known as an agile and innovative technology services company, V-Soft was recently recognized among the top 100 fastest-growing staffing companies in North America. V-Soft is a trusted partner with experience across diverse technology stacks to help business get IT done.

From analysis through implementation, V-Soft offers a blended support model that meets most any budget results in a reliable and realistic means to accomplish integration objectives. Unlike most IT companies, V-Soft has a large quantity of expertise in-house complimented by on-demand talent via their IT staffing division. These compelling facts for business when combined with numerous “best of” employer awards make V-Soft Consulting the employer of choice and the partner of choice for the enterprise.

To learn more about V-Soft Consulting and its offerings, click here.

© V-Soft Consulting Group, 2017. All Rights Reserved.ServiceNow is a trademark or registered trademark of ServiceNow in the United States and other countries.

Contact Us:

V-Soft Consulting101 Bullitt Lane

Suite 205Louisville, KY 40222

USA+1 (800) 425-8425

26