CI Synchronizer (Enterprise Edition) has been designed and built with three key things in mind:
- Scalability (it can handle millions of CIs through a scalable queuing architecture).
- Performance (it supports delta synchronization in addition to other).
- Extensibility (it includes many, many more asset types/CI classes, CI attributes, related lists and CI relationships).
CI Synchronizer is delivered as a SaaS solution which is managed and maintained by Syncfish. Key features of the service include:
- An incredibly rapid setup time (60-90 minutes).
- A sophisticated duplicate record handling and correlation engine to ensure duplicate CIs are not created in your CMDB.
- Delta synchronization (only synchronizes Lansweeper assets which have been added or changed since the previous sync).
- The Out of the Box (OOTB) CI Sync configuration, deployed with each customer instance, caters for following record sets (all fully automated)
- Over 30 Lansweeper asset times
- Over 10 related records
- Over 10 major CI-to-Ci relationship types (and almost 80 individual relationships)
- An OOTB configuration that can be adjusted to deal with customer specific CMDB designs.
- The ability to handle complex transformation rules and logic to address the needs of large/complex organizational environments.
CI Synchronizer has been designed to meet enterprise level cyber security and data privacy requirements, including:
- Each customer is provided their own dedicated instance of the SaaS solution. There is no sharing of processing or storage between customers.
- Each customer decides the physical location of their SaaS instance. CI Sync is hosted in Azure and therefore can be in hosted in Azure data centre locations across the globe.
- CI Sync does not store a copy of the Lansweeper data after it has been processed and persisted into ServiceNow.
- Each CI Sync instance is integrated/enrolled into your own Azure AD. This means all authentication and authorisation is controlled by your own Azure AD.
- CI Sync is offered with two architect options, one base on cloud-native isolation and the other based on VNET and private-end point isolation. Customers can select an architecture (and related subscription) which meets their cyber security needs.
