Connect the data your process needs. Agree the authoritative source for each field and which records should follow.
Service Automation Suite · Central coordination
Combine data and apply rules
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Information & trigger
Relevant data or workflow status
Follow-up & feedback
Update, execute and record outcomes
Define source and destination
Choose the available data and what other teams need.
Compare and update
Match records, apply field rules and update relevant differences.
Check the result
Show what succeeded and follow up missing or conflicting data.
Education & support
Student information without disconnected handovers.
Connect relevant student-information changes to education service, access and communications. One change can reach several teams at the right time.
Service Automation Suite · Central coordination
Combine data and apply rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Information & trigger
Relevant data or workflow status
Follow-up & feedback
Update, execute and record outcomes
Choose a relevant event
Start with a change that is currently passed to another team manually.
Reach the right team
Connect the necessary data to facilities, access or service tasks.
Track the outcome
Keep track of what is arranged and which questions remain open.
How Service Automation Suite connects data and execution
The work between your applications
Change processed. Why still re-enter data?
Service Automation Suite connects OSIRIS with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
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
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
Student or schedule + facilities + rules
Determine & check
Compare change and determine service needs
Execute & report back
Start account or facilities task · Notify team · Track execution
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.
From product to process
How to use the integration
Student lifecycle
Use available enrolment changes for student accounts, facilities and service tasks.
Keep people records current
Synchronise agreed person and organisation fields between the relevant applications.
Handover & return
Connect staff changes to equipment handover and confirmed return.
Connect work across your applications
What would you like to connect OSIRIS 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 OSIRIS with your other applications. Automate the work between them and stay in control.
Process & control
Less manual work
Connect OSIRIS 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 OSIRIS 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.
Under the hood
This integration, step by step.
How we configure this example
Pass OSIRIS changes to education services
Connect and retrieve
Use the data exchange available to your OSIRIS environment. Select a relevant enrolment change as the trigger.
Find the correct record
Relate the student reference, programme and effective date to the correct person and education organisation. Check the valid situation before changing access or service.
Execute the agreed action
Start only the agreed support, communication or access task. Include the OSIRIS reference so the responsible department can identify the student.
Verify the outcome
Retain the outcome with the processed OSIRIS change. Route missing student matches for review and prevent duplicate account or service tasks.
In this integration
Identification
OSIRIS student reference
Data
student reference, programme and effective date
Feedback
Confirmed support or open exception
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.
Signature declined. Keep the process moving.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
Combine
Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
The outcome determines what follows
Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
The benefit
Appropriate follow-up for each outcome without counting a sent signing request as completed work.
Temporary access, with the end handled too.
Additional access is approved for a limited period. A checkbox alone does not preserve why, for whom and until when.
Combine
Connect identity, approval, expiry date and the available access action. Reuse the same data for a scheduled follow-up check.
The outcome determines what follows
Revocation confirmed: record the result. Extension requested: ask for a new decision. Not revoked: raise the exception with the authorised group rather than silently completing it.
The benefit
Fewer forgotten exceptions and a traceable relationship between approval and actual access.
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.
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
OSIRIS in your 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.
