The Netherlands Institute for Public Safety (NIPV) supports safety regions and fire services, including the nationwide supply of fire service clothing. Service Automation Suite connects issue and return to your internal workflow, helping you track who has which items and what still needs to be arranged.
The work between your applications
Clothing issued. Properly recorded too?
People, roles and equipment change within a safety region. Keep issue, return and the related records connected. Service Automation Suite links these steps so the responsible team knows what to do and missing returns remain 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.
Arrange handover
Issuing equipment? Assign the activity to the safety region.
Who receives which clothing or equipment, and who arranges the handover? Link the issue to the recipient and give the responsible team a clear activity. Keep the agreement, handover and records together.
Service Automation Suite · Central coordination
Connect equipment, recipient and responsible team
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Supplier connection & context
Agreed data for issuing or taking back equipment
Safety region
Activity to arrange and confirm handover
Determine what is issued to whom
Connect available supplier data to the right recipient, location and item. Use only agreed attributes and request missing information first.
Have the safety region arrange handover
Prepare an activity in your own service management tool. Give the responsible team the information needed, linked to the recipient and item.
Confirm actual handover
Have the person carrying out the handover confirm what was issued. Then process agreed records and feedback. Creating an activity does not mean equipment has been handed over.
Arrange return
Taking equipment back is work too. Keep the activity open until confirmed.
Connect equipment return to an activity for the safety region. Track what must be returned, who coordinates it and what was actually received. Missing equipment gets focused follow-up.
Service Automation Suite · Central coordination
Compare expected and confirmed returns
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Trigger & records
Agreed data about equipment to be taken back
Safety region
Activity for receipt, checking and feedback
Specify the return
Link the request to the correct person and equipment. Record who at the safety region arranges the return and what confirmation is required.
Record what was actually returned
Have the responsible employee confirm receipt. Partial returns, missing equipment and discrepancies remain visible and receive follow-up activities where needed.
Update the records
Record the confirmed return against the recipient and item. Keep any required check or follow-up visible: returned does not automatically mean fit for use again.
Exceptions & follow-up
Something missing? Turn it into focused follow-up.
Missing clothing, a partial return or damaged equipment needs follow-up. Give the right person the information needed to resolve it and keep outstanding work visible.
Service Automation Suite · Central coordination
Connect request, supplier reference and rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Request & context
Exception, affected item and owner
Supplier & feedback
Available response or follow-up action
Identify the discrepancy
Compare available data with the request and confirmations. Record missing or inconsistent information without silently marking the entire workflow complete.
Assign the right person
Route a verification task to the responsible team, with the recipient, item and discrepancy. Keep ownership of follow-up visible.
Process the outcome
Update the records once the outcome is confirmed. Keep return, replacement and any required check distinct.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect NIPV to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Example configuration · shaped by your process
Connect a supplier reference to internal execution
Choose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Build the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Configure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.
Which data do you maintain?
An example configuration, not fixed field names or a mandatory combination.
Request, order and line reference
Store the relationship between the internal request and available external references. Recognise repeated updates before creating anything.
Item, person, location and available status
Map only available data and define the source for each field. Dispatch status does not confirm receipt or handover.
Confirmed receipt, exception and follow-up task
Update records after the agreed checks. Fitness-for-use decisions for protective equipment remain with authorised personnel. An uncertain order outcome requires review before retrying.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Need to publish data yourself?
Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.
Combine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.
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.
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.
Refreshing a report does not guarantee reliable data.
A source request can succeed while data is missing, differently coded or not yet fully retrieved.
Combine
Combine pagination and output mapping with agreed data checks. Use shared relationship tables to connect sources.
The outcome determines what follows
Checks passed: prepare the dataset. Deviation: request review and expose freshness. Temporary API failures follow a bounded recovery path.
The benefit
A clearer distinction between a technically successful import and information fit for decision-making.
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
NIPV in your workflow
Clothing & equipment
Equipment issue and return with the safety region
Connect NIPV to activities for the region. Confirm equipment issue and return, update records and follow up missing equipment.
