Combine available Planon location and asset data with your CMDB or service desk. Service Automation Suite maps object codes, relates locations and checks the authoritative source for each field.
Scenarios in practice
What would you like to do with Planon?
Choose a use case and explore the related workflow steps.
Connect buildings, rooms and assets to service records.
Combine available Planon location and asset data with your CMDB or service desk. Service Automation Suite maps object codes, relates locations and checks the authoritative source for each field.
Building, room and asset codes with agreed attributes and relationships.
For example, connected to
Load into the agreed register and verify the result.
Select the right data
API licensing, object definitions and permissions determine available read and write operations.
Match and map
Building, room and asset codes with agreed attributes and relationships.
Load and verify the result
Agree the authoritative source for each field. Validate required values and existing records before loading. Retain source and target references, counts and errors; retry only data not successfully processed.
How Service Automation Suite connects data and execution
The work between your applications
Connect buildings, rooms and assets to service records.
Combine available Planon location and asset data with your CMDB or service desk. Service Automation Suite maps object codes, relates locations and checks the authoritative source for each field.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
Compare
What exists? What should exist?
Determine what is needed
Matrix · policy · legal requirements
Coordinate the next steps
Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
PlanonService Automation Suite
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Start with one integration, register or check. Build on the same data and rules.
Combine into one controlled process
Data → rules → execution
Combine
Inventory + CMDB + ownership
Determine & check
Match, compare and review discrepancies
Execute & report back
Update CMDB · Create service ticket · Review replacement or retirement
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Build visually. Manage easily.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
Connect work across your applications
What would you like to connect Planon with?
Choose the role in your workflow. Explore applications from the scenarios and further directions to discuss together. We define the data, actions and available interface for each combination.
Connect Planon with your other applications. Automate the work between them and stay in control.
Process & control
Less manual work
Connect Planon with HR, IT and suppliers. Automate the flow of data and actions.
Control over execution
Define rules, follow up exceptions and verify the outcome.
Purposeful data sharing
Decide which data to share, with whom and under which conditions.
Autonomy & choice
Your applications, one process
Combine Planon with the applications that fit your organisation.
Direct access to the makers
Work directly with Scope4mation: Dutch technology, process expertise and support in one team.
Room to adapt
Reuse your configuration and keep process knowledge transferable as systems or rules change.
Build & operate together
Start small, build further
Start with one use case and reuse the building blocks for the next.
From idea to practice, together
We help with configuration, exceptions and handover, starting from your daily practice.
Operate it your way
Operate it yourself, together or with us. Agree on clear responsibilities upfront.
Beyond the first integration.
Use the same data and rules in your next process.
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.
A replacement laptop without losing context.
An employee receives a replacement device. The old asset, new record and open service or security tickets must remain connected.
Combine
Use the central relationship between owner and device identifiers. Combine handover, technical inventory and return with existing tickets.
The outcome determines what follows
Receipt confirmed: update ownership and relationships. Old device missing or uncertain match: start a targeted review instead of overwriting historical records.
The benefit
Current records and a traceable handover even when a management tool uses different names.
A different name does not mean a new record.
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.
Combine
Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
The outcome determines what follows
Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
The benefit
A consistent data foundation managed by your team instead of investigated again for every connection.
Ordered, delivered and actually in use?
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
Combine
Compare orders, delivery details, serial numbers and inventory with central ownership relationships. Keep missing confirmations part of the workflow.
The outcome determines what follows
Matching data: update the agreed records. Unknown device, unexpected owner or unconfirmed delivery: create work for the correct support group.
The benefit
Fewer gaps between administrative and technical records and targeted follow-up of discrepancies.
Your process needs more than a standard action?
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.
Need 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.
From product to workflow
Planon in your wider workflow
Pull up a chair. Or join us online.
Over coffee, tea or online: tell us what you are working on.
We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.
