Company assets · Service Automation Suite
Your inventory detects the device. Your records show a different user. Service Automation Suite connects records to handovers, ownership and returns using the tools you already have.
Sound familiar?
Names and device IDs differ. Comparing exports remains manual work.
Service Automation Suite connects Intune or Lansweeper to TOPdesk, for example, using agreed identifiers and maps users to the same employee.
Usable records without repeatedly matching names by hand.
The laptop was issued, but its receipt confirmation is in a separate email.
Service Automation Suite connects the request and asset to receipt confirmation or signing through ValidSign, for example, and updates the records.
Find the owner, agreement and evidence with the same handover.
A device is vulnerable, but its owner and next action are missing.
Service Automation Suite combines Intune data with ownership, for example, and creates a targeted ticket in your service tool.
The right team gets context and can track resolution per asset.
Scenario · Company assets
The supplier provides the initial data. You then compare those records with what is technically present. Service Automation Suite connects these steps into one continuous process, for example with TOPdesk and Intune.
Use available item, delivery and serial-number data to create or match a TOPdesk asset, for example. Retain the supplier reference and prevent duplicate records.
Match the same device using reliable identifiers. Compare available attributes, user and status. Not visible in Intune yet? Keep that difference explicit; a delivered device may not yet be enrolled.
Define the authoritative source per field. Update technical attributes selectively without blindly replacing procurement data or confirmed ownership. A signed-in user is not automatically the person who received the asset.
An uncertain match or missing field can create a TOPdesk activity, for example. Process the confirmed correction and compare again. Records, execution and feedback stay connected.
Dustin is an existing supplier connection. Bechtle and ALSO illustrate other supplier routes, not deployed Service Automation Suite connections. API, XML/EDI or OCI: the available interface, data and permissions determine what we can connect. Delivery or technical detection does not prove physical receipt; confirmation remains a separate workflow step.
Scenario · Clothing & equipment
A safety region needs to know which clothing and equipment has been issued to each person. Connect issue and return to records and the responsible team's work. NIPV supplies fire service clothing; organise activities and follow-up in your own service management tool, such as HaloITSM, ServiceNow, Freshservice or TOPdesk.
Match available data to the correct recipient and location. Apply your rules for role, permitted equipment and approval. Request missing information first.
Prepare the activity in the service management tool your team uses. Specify what must be issued or returned, who coordinates it and what confirmation is needed.
Have the person carrying out the handover record what actually changed hands. An activity does not prove issue; a return request does not confirm receipt.
Update records after handover is confirmed. Keep missing equipment and partial returns visible, assign follow-up work and check what remains outstanding.
Returned is not the same as fit for use again. Keep any required check or release as a separate process step.
Connecting your tools
Service Automation Suite links serial numbers from Intune or Lansweeper to employees and asset records in TOPdesk, for example. Manage source rules and relationship tables centrally and reuse them across integrations.
Not a solution only its builder understands. Together, we define data relationships, mappings and rules for reuse in future processes. We agree who tests and maintains them so a colleague can take over.
Your process leads
Other tools? We review the capabilities, APIs and permissions in your environment. Your existing systems remain where you work.
From plan to delivery
The integration is one part. The surrounding agreements make it work.
An import captures a moment. Issue, relocation, replacement and return then change ownership. We connect agreed sources to those actions and configure comparison and exception handling.
Not everything has to be perfect upfront. We select the data and identifiers needed for the first use case. Uncertain matches are flagged for review; we agree which records may be updated automatically.
NVM
NVM brought HR and IT together in one standardised employee process, managing permissions, mailboxes, laptops and access through personnel changes.
Read the customer storyAccess and assets driven by employee changes.
Strukton
Strukton connects employee processes, identity and assets to maintain control over security, compliance and resources.
Read the customer storyEmployee workflows, identity and assets connected.
Mesdag
Mesdag uses Service Automation Suite/Qixium as an IAM orchestration platform to bring policies, assignments, exceptions and fulfilment together in a verifiable process.
Read the customer storyPolicies, assignments and exceptions brought together.
Start with what is stuck today
Show us where inventory, ownership or returns diverge. We will look at the sources you have and how to connect them usefully.
From question to execution
Device data and asset records diverge. Manual exports reveal discrepancies too late.
Use Service Automation Suite to read agreed data from Intune, for example, match existing assets and map fields and lookup values to your asset records, for example in TOPdesk. Link the right person to the asset and route discrepancies for follow-up.
Up-to-date records with visibility into discrepancies. Data, API permissions and source ownership are agreed per environment.
The inventory tool detects a device, but your records may lack its correct user, location or status. A single import does not establish whether all data agrees.
Use Service Automation Suite to connect data from Intune, Lansweeper or Snow, for example, to your existing asset records. Define the source of truth for each field, match the same asset using configured identifiers and combine it with employee and owner data. Service Automation Suite updates agreed fields in your service tool, for example, and routes differences for follow-up.
Bring inventory and management together without repeatedly comparing exports. Reuse the same employee-to-asset relationship for handover, role changes, returns or a ticket about that device.
Many organisations have automated parts of asset management but lack a coherent process for procurement, registration, issue, ownership, use, return and disposal. This leaves a gap in control.
Service Automation Suite connects the full lifecycle: receipt and registration, issue and digital handover, deployment and use, followed by return, decommissioning, wiping, reuse or controlled disposal.
Less manual follow-up, fewer errors, better reuse, less dependence on specialist knowledge and demonstrably stronger control over ownership and compliance.
Show not just which licences have been assigned, but why, which source supports the assignment and whether they are actually used.
Licences are often assigned historically and remain active without current justification or usage checks.
Detect, explain, review, approve, change and verify: controlled optimisation instead of blindly revoking licences.
Let active assets and services feed into contracts and billing in a controlled way.
Asset changes and billing often diverge, causing lost revenue or corrections.
The asset source can be TOPdesk, Intune, Ultimo or another system; the orchestration logic stays in Service Automation Suite.
Turn assigned and used Microsoft licences into a verifiable billing process.
Licence counts, customer contracts and actual usage can quickly diverge.
Graph provides Microsoft context; Service Automation Suite centralises rules, approvals, exceptions and audit records.
Your process leads. The tools can vary. We configure connections around the capabilities and permissions in your environment.
Explore all integration examplesOne foundation. More possibilities.
Populating an inventory is the starting point. The value is knowing which asset belongs to which person, supplier and service, and whether that remains correct.
Relate serial number, asset ID and technical device ID. Use agreed identifiers to recognise the same laptop across sources.
Assign an asset to the correct owner even when names or user codes differ by tool. The same relationship table can feed other integrations and processes.
Combine procurement and supplier records with technical inventory. Review differences before a source overwrites existing data.
Keep selection, change, employee and receipt together. Do not let a missing return or signature disappear behind an updated asset record.
Reuse relationships for security tickets or corrective actions: which device, owner and service are involved? Linked tickets and agreed measurements let you track handling per asset.
Keep central relationships and process agreements as the starting point. When a tool changes, adapt the connection and identifiers and verify the outcome.
Relationships, mappings and process agreements have a recognisable place in the same environment. Colleagues can follow configuration and processing without first reconstructing the original builder’s personal approach.
Your process keeps evolving after go-live. Handle an extra field, changed owner, new exception or small workflow change from the same foundation: adjust it, review the impact, test it and track processing. Agree who manages it, who reviews changes and when our support is needed.
Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Build it yourself: explore the technical approachNeed to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
