Breadcrumbs

How-to - Assess the Success of a CI Synchronizer Trial

Aim

To provide suggested Success Measures to assist customers conducting a trial/POV of CI Sync.

This KB applies to:

Applies to Versions

All

Applies to Source Connectors

All

Applies to Destination Connectors

ServiceNow

Overview

Syncfish offer prospective customers the opportunity to trial CI Sync.

A trial instance of CI Sync is identical to a production/paid instance of CI Sync, with the only difference being a trial is typically limited to two weeks duration.

Syncfish are often asked by customers trialling “what do you recommend as a simple set of success criteria” for a trial. In response we have prepared this article.

Clearly each customer circumstance can be slightly unique, and therefore so are the success criteria. Please treat this information as a starting point which can be built upon as required. Syncfish have intentionally kept these criteria “lean and mean” to ensure they are a manageable start. Syncfish can work with you to provide significantly more detailed evaluation criteria, so contact us if you would like this.

Sample Trial Success Criteria

#

Criteria

Outcome

1

Was the setup of CI Sync (and the source & destination system connectors) as per the documentation provided?


2

Was the setup time/overhead in-line with what was expected?


3

Did CI Sync provide a “mock sync” test option to evaluate whether ServiceNow was ready to receive actual sync’d data?


4

Did CI Sync deliver a fundamental outcome of transmitting IT asset/resource records from each in-scope source system into the ServiceNow CMDB?


5

Did CI Sync insert and/or update CIs in the CMDB tables (CI Classes) in accordance with the CI Sync documentation?


6

Did CI Sync demonstrate the ability to correlate to existing CIs in the CMDB (i.e. not create duplicates)?
If duplicates were detected during testing, was Syncfish support able to explain the reason/s why?


7

If Syncfish support was engaged to assist during the trial, was the responsiveness and knowledge/capability of the support in line with expectations?


8

If requested during the trial, did Syncfish demonstrate the ability to modify CI Sync rules (mapping, transform or correlation rules) to ensure the data was as required in the CMDB?


9

Does the CI Sync provide flexible options for dealing with topics such as:

  1. Whether various master data and choice values in ServiceNow is updated (or not)?

  2. Whether attributes such as discovery source and correlation prefix values can be easily adjusted?

  3. Whether insert vs update rules can be made different?


10

Did Syncfish demonstrate the level of customer commitment and expertise to be confident in the long-term use of CI Sync within the organisation?


There are currently no related articles.

Control Information

Created

Reviewed

Data Classification

PUBLIC
Classified in accordance with the Syncfish Data Classification Framework