Distribution and Disclaimer
This content is not to be redistributed by the recipient without written permission from Syncfish.
While every effort has been made to ensure the accuracy of the information, it is possible for inaccuracies to be present. Readers are encouraged to engage with either Syncfish or Lansweeper to discuss individual topics.
High Level Product Comparison
CI Synchronizer
-
CI Sync is a comprehensive and sophisticated integration solution designed for rigorous alignment of Lansweeper source data and ServiceNow CMDB (and Asset) destination data.
-
CI Sync can cater for any business rule, business requirement, or data anad workflow requirements in the destination ServiceNow instance.
-
CI Sync’s transactional record handling, data mapping and transformation logic and data correlation logic deliver perfect data to meet every customer’s specific ServiceNow requiremetns.
-
CI Sync delivers a large number of Lansweeper assets, child records and CI-to-CI relationships to your ServiceNow CMDB (all OOTB). CI Sync can be extended to include any record type or attribute available from the Lansweeper data.
-
CI Sync does not require ServiceNow ITOM licences.
-
CI Sync works with Lansweeper On-Prem or Lansweeper Cloud.
Lansweeper Service Graph Connector
-
Lansweeper ServiceGraph connector is a simple data transfer solution to move source data largely “as is” between Lansweeper and ServiceNow.
-
The Lansweeper Service Graph Connector provides a limited number of Lansweeper asset types, child records and very few CI-to-CI relationships OOTB.
-
Any tuning or extension of Lansweeper Service Graph data mapping or data transformation is a customer responsibility.
-
Lansweeper Service Graph requires ServiceNow ITOM licences.
-
Lansweeper Service Graph only works with Lansweeper Cloud (it does not support Lansweeper On-Prem).
High Level Service Comparison
Syncfish
-
Our CI Sync product delivers a sophisticated, flexible, secure and scalable CMDB automation solution using data from Lansweeper and many (many) other sources.
-
While delivering source data into a ServiceNow CMDB is a complex undertaking (made simple via CI Sync), the primary challenge faced by organisations is “what’s required to maximise the value of this CMDB and asset data in ServiceNow”. Questions such as following are common:
-
“We don’t understand the customisations inside of our ServiceNow, and therefore don’t know how much time/effort is needed to transform the source system data to meet our needs”
-
“We have various asset management processes across our organisation to address stock items, assets under repair, purchase and warranty information, and so on. We aren’t sure how to ensure the incoming source data (from Lansweeper or other systems) can be adjusted to align to our key HAM processes”
-
“We have some understanding of our ITIL processes, but aren’t really sure how they should be amended to leverage an automated CMDB”.
-
-
This is where CI Sync differs from most commercial integration solutions. CI Sync is supported by the Syncfish team, who have over 15 years' experience with ServiceNow!
-
The Syncfish team can provide a services layer, alongside the CI Sync technology, to ensure the automated CMDB (and asset) data is mapped, transformed and shaped to perfectly align to your key business processes.
-
CI Sync is NOT a commodity based integration solution that leaves customers to deal with changes to the important rules that drive asset and CMDB data. Syncfish partners with customers to alleviate the burden of integrating data into a key system like ServiceNow.
-
It is the Syncfish service layer, based on SMEs who come with data integration expertise, ServiceNow technical and functional expertise combined with business process expertise that truly separates CI Sync and Syncfish for large or complex organisations.
Lansweeper
-
Lansweeper provide the Service Graph connector as a commodity offering that does not include a services layer.
-
Customers are generally expected to adopt the Service Graph connector “as is”. Each customer is responsible for making changes to the Lansweeper Service Graph to align to their data and/or business process needs within ServiceNow.
Detailed Feature Comparison
|
Feature |
Syncfish CI Synchronizer |
Lansweeper Service Graph Connector |
|
Services Layer |
|
|
|
Yes (See Implementation and Support Plans) |
Documentation only |
|
Yes (See Implementation and Support Plans) |
Documentation only |
|
Yes (See Implementation and Support Plans) |
No |
|
Yes (See Professional Services Team) |
No |
|
Yes (Bronze, Silver, Gold - see https://www.syncfish.com.au/support) |
No |
|
Yes (various options tailored to individual customer needs) |
No |
|
Flexible and customisable integration with HAM/SAM processes |
|
|
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes
|
No |
|
Supported Lansweeper Discovery Repositories |
|
|
|
Yes |
No |
|
Yes |
Yes |
|
Licence Requirements |
|
|
|
Does not require ServiceNow ITOM Licences |
Does require ServiceNow ITOM Licences |
|
Yes |
Yes |
|
Yes |
Yes |
|
Core Architecture and Data Hosting |
|
|
|
CI Sync is provided via a dedicated instance per customer |
Service Graph integrates with Lansweeper cloud which is a shared hosting model. |
|
Syncfish/customers agree. the hosting location of the customer’s dedicated instance of CI Sync (which can be in almost any Azure Region globally) |
LS Cloud storage is held in Ireland or USA only |
|
For Lansweeper On-Prem: SQL For Lansweeper Cloud: Lansweeper Cloud API. For both: Robust transactional extraction and synchronization technology with pre-caching engine to support all of the advanced functionality offered by CI Sync. |
For Lansweeper On-Prem: SQL For Lansweeper Cloud: ServiceNow flows calling into Lansweeper Cloud API. |
|
Yes |
To the extent provided by Service Graph. |
|
Yes |
To the extent provided by Service Graph. |
|
Initial Data Sync/Bulk Load and Ongoing Synchronization Capabilities |
|
|
|
For Lansweeper On-Prem: Transactional synchronization engine For Lansweeper Cloud: Bulk Export, File Drop, then transactional synchronization engine |
Bulk Export, File Drop, File Load directly into ServiceNow |
|
Simple re-synchronization trigged via a UI option |
Repeat of Initital Data Sync |
|
Automatically caters for deleted parent/main CIs (retirement) or deleted child records (deletion). |
No OOTB support (does not cater for deleted parent/main CIs or deleted child records - customer responsibility to manage). |
|
Natively supported via record level checksum to determine if a record has changed (or not). |
Scheduled job based on customer defined “last record update date”. |
|
Yes (UI selectable record sets, OOTB support to filter record subsets on CIDRs, additional filters to meet any critiera can be easily implemented) |
Customer responsibility (ServiceNow Admin/Developer involvement) |
|
Yes |
Yes |
|
Yes |
Yes |
|
Low (all transformation and correlation handling is performed within CI Sync and therefore is offloaded from the customer’s ServiceNow instance) |
Higher than CI Sync (all transformation and correlation handling is performed within the customer’s ServiceNow instance). |
|
Record and Attribute Mapping Flexibility and Extensibility |
|
|
|
> 40 |
~20 |
|
Syncfish responsibility (no customer overhead) |
Customer responsibility (ServiceNow Admin/Developer involvement) |
|
~200 |
~40 |
|
Syncfish responsibility (no customer overhead) |
Customer responsibility (ServiceNow Admin/Developer involvement) |
|
> 100 |
~5 |
|
Syncfish responsibility (no customer overhead) |
Customer responsibility (ServiceNow Admin/Developer involvement) |
|
Data Transformation Capabilities |
|
|
|
Sophisticated rules engine |
ServiceNow transform maps (ServiceNow Admin overhead) |
|
Natively and comprehensively supported OOTB. |
Nothing provided/supported OOTB |
|
OOTB default value maps with flexible overrides |
Nothing provided/supported OOTB |
|
OOTB default value maps with flexible overrides |
Nothing provided/supported OOTB |
|
Comprehensive and flexible OOTB defaults that can be override with sophisticated rules based logic. |
Nothing provided/supported OOTB |
|
Intelligent OOTB defaults to populate Assigned_To and link with the User table in ServiceNow. OOTB defaults can be overridden with sophiticated rules/logic to read any attributes/data in Lansweeper and transform the data as it is persisted into ServiceNow. |
Static support for Last Logged On and Assigned_To using Name attribute matching only. Changes to location data handling is the Customer responsibility (ServiceNow Admin/Developer involvement). |
|
Supported |
Not Supported |
|
Asset Source Systems Supported |
|
|
|
List of Source Systems supported |
|
|
|
Advanced Record Types Support |
|
|
|
Lansweeper On-Prem: OOTB Support Lansweeper Cloud: OOTB Support |
Lansweeper On-Prem: Not Supported Lansweeper Cloud: Not Currently Supported (no current roadmap to support) |
|
Comprehensive (management and hypervisor objects, hosts and guest) |
Limited/basic (Host/Guest) |
|
Recognised |
Not recognised |
|
Yes |
Yes |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Automatically caters for deleted child records (such as Installed Software, Storage, Memory Modules, Network Adapters and so on). |
Not supported (obsolete records remain in place). |
|
CI-to-CI Relationships (CI Dependency) Support |
|
|
|
Comprehensive |
Limited |
|
Comprehensive |
None |
|
Comprehensive |
Limited |
|
Supported |
Not Supported |
|
Management of ServiceNow Master Data and Reference Data |
|
|
|
Dynamically inserts new Master Data Dynamically prunes unused Master Data records (when no longer referenced from CI records) Above rules can be suppressed for the main/parent asset or child records (CPUs, Disks, NICs, etc) |
No OOTB update/management of ServiceNow Master Data tables. |
|
Dynamically inserts new Choice values (can be suppressed) |
No OOTB update/management of ServiceNow Reference Data. |
Control Information
|
Created |
|
|---|---|
|
Reviewed |
|
|
Data Classification |
PUBLIC
|