STRATALConnect external providers
Bring agreed provider accounts into one integration approach, with record coverage matched to the access available to your organisation.
Coming soon
Stratal Integration Hub
Stratal Integration Hub.
Connected data. Automated processing.
A central hub for connecting external providers to Stratal and automatically processing the records they make available. The initial focus is ABAX, Depotnet and COINS ERP.
In development. Provider connections and automated workflows will be introduced as they become available.
PLANNED CONNECTIONS
ABAXDepotnetCOINS ERP
Stratal Integration HubConnect · Map · Process
Connected recordsOperational contextLess manual entry
Illustrative workflow · Coming soon
Connected data, useful work
One hub for the systems your business relies on.
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 your 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.
Process data automatically
Turn incoming records into usable Stratal data through configured mapping and processing rules, reducing the need for routine manual handling.
Keep records in context
Associate provider information with the relevant Stratal records so operations, fleet and commercial teams can work from a connected view.
Initial provider focus
Three key systems. One connected approach.
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.
Planned connection
Vehicle tracking & fleet
ABAX
ABAX provides vehicle tracking and fleet information. The planned connection will bring available fleet records into Stratal, helping teams relate vehicle activity to the operation.
- Vehicle and asset information made available by the connection.
- Position, journey and mileage data where exposed and authorised.
- Fleet information connected to the relevant Stratal vehicle context.
Planned connection
Jobs, contracts & workforce
Depotnet
Depotnet supports utilities job, contract and workforce management. The planned connection will bring available operational records into Stratal to support connected delivery workflows.
- Available job, work order and contract records.
- Workforce, progress and completion information where exposed.
- Related operational data linked to the appropriate Stratal context.
Planned connection
Enterprise resource planning
COINS ERP
COINS ERP supports construction business processes across finance and operations. The planned connection will bring available ERP records into Stratal to connect enterprise data with operational delivery.
- Available project, job and contract information.
- Financial, commercial and procurement records where exposed.
- Related ERP data mapped to the agreed Stratal workflow.
These describe 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.
Automatic data processing
From provider records to usable Stratal information.
The planned workflow starts with an authorised connection and ends with records in the right operating context. The data source, field mapping and processing rules need to be agreed for each organisation.
- 01
Connect the provider
Identify the provider account, authorised access and record types available to the connection.
- 02
Map the records
Match provider fields and identifiers to the relevant Stratal records. Agree which system owns each piece of information.
- 03
Apply the rules
Process incoming data automatically using the configured workflow. Record matching, required values and update behaviour form part of the agreed setup.
- 04
Check the outcome
Confirm that processed records appear in the intended Stratal context and agree how incomplete or unmatched information should be handled.
Built around your organisation
Agree the data flow before relying on it.
“All available records” means the records your provider account can expose through the authorised connection. Each deployment needs a clear scope so automated processing supports the way your business works.
Record coverage and access
Confirm the provider modules, account permissions and record types available for use. Some information may need additional provider access or licensing.
Ownership and direction
Agree the source of truth and whether a workflow reads provider data or also requires updates back to the provider. Two-way transfer is not assumed for every connection.
Timing and processing rules
Define when data should be processed, how records are matched and which changes belong in each system. Frequency and supported actions will be confirmed for the connector.
Exceptions and responsibility
Agree who reviews missing information, unmatched records or failed transfers, and how the team checks the outcome before relying on the connected workflow.
Common questions
What to expect at launch.
Is the Stratal Integration Hub available now?
The hub is coming soon. This page describes its planned purpose and initial provider focus. No launch date has been announced on this page.
Which providers are planned first?
The initial focus is ABAX for vehicle tracking and fleet data, Depotnet for operational records, and COINS ERP for enterprise data. Availability and supported workflows will be confirmed as each connection is introduced.
Will it process all records?
The intended scope is all records made available through the authorised provider connection. Coverage depends on the provider API, licensed modules, permissions and connector support. The agreed mapping determines how those records are used in Stratal.
Will data move automatically in both directions?
Automatic processing is a core aim of the hub. The direction of transfer, supported write actions and processing frequency will be agreed for each provider and workflow. Not every connection should be treated as a two-way sync.
Can we discuss other providers?
Yes. Contact Stratal with the provider name, records involved and the workflow you want to support. Additional providers can be considered as the hub develops; this page does not commit to a particular future connector.
How do we prepare for a connection?
Identify your provider accounts, data owners, relevant records and intended outcome. Bring a representative workflow to the discussion so access, mapping and responsibilities can be assessed together.
ABAX, Depotnet and COINS ERP are third-party products. Their names identify the intended connection targets; this page does not announce a partnership or provider endorsement.
Stratal Integration Hub · Coming soon
Bring your data
into the workflow.
Tell us which systems you use and what you want their data to do in Stratal.