Connected data, useful work
Vehicle tracking, job delivery and enterprise finance often sit in different systems. The Integration Hub is being developed to bring available provider records into the Stratal environment and process them against the workflows each organisation uses.
The aim is to reduce repeated data entry and give teams a clearer connection between what happens in the field and the records used for planning, fleet management and commercial decisions.
Three systems first
ABAX, Depotnet and COINS ERP are the first planned connections. The scope is all records exposed through the authorised provider connection, with the usable fields and workflows confirmed during setup.
- ABAX, vehicle tracking and fleet. Available vehicle and asset information, with position, journey and mileage data where exposed and authorised, connected to the relevant Stratal fleet context.
- Depotnet, jobs, contracts and workforce. Available job, work order and contract records, with workforce, progress and completion information where exposed, linked to Stratal operations.
- COINS ERP, enterprise resource planning. Available project, job and contract information, with financial, commercial and procurement records where exposed, mapped to the agreed commercial workflow.
These are the planned connection areas, not a final list of supported fields. Provider APIs, account permissions, licensed modules and connector capabilities determine what can be accessed and processed.
How automatic processing will work
The planned workflow starts with an authorised connection and ends with records in the right operating context:
- Connect the provider. Identify the provider account, authorised access and record types available to the connection.
- Map the records. Match provider fields and identifiers to the relevant Stratal records, and agree which system owns each piece of information.
- Apply the rules. Process incoming data automatically using the configured workflow, including record matching, required values and update behaviour.
- Check the outcome. Confirm that processed records appear in the intended Stratal context, and agree how incomplete or unmatched information is handled.
Agreed with each organisation
Each deployment needs a clear scope so automated processing supports the way the business works. Organisations will agree the provider modules and record types available, the source of truth for each record, and whether a workflow reads provider data or also needs updates back to the provider. Two-way transfer is not assumed for every connection. Processing timing, matching rules and responsibility for reviewing unmatched records or failed transfers are agreed before teams rely on the connected workflow.
Availability
The Integration Hub is coming soon and no launch date has been announced. Provider connections and automated workflows will be introduced as they become available, with supported workflows confirmed as each connection is introduced.
In the meantime, Stratal’s existing integration areas cover documents through Google Drive and Microsoft 365, company sign-in and SSO, ABAX telematics, Hubstaff, mapping and streetworks gateways, and file, API and webhook data exchange, with availability confirmed for each installation.
Talk to us about your systems
To prepare, identify your provider accounts, data owners, relevant records and intended outcome, and bring a representative workflow to the discussion. Other providers can be considered as the hub develops; contact the Stratal team with the provider name, the records involved and the workflow you want to support.
ABAX, Depotnet and COINS ERP are third-party products. Their names identify the intended connection targets; this announcement does not announce a partnership or provider endorsement.
Bring your data into the workflow.
Tell us which systems you use and what you want their data to do in Stratal.
Discuss the Integration Hub