Database · SICETAC

The complete SICETAC database.

Work with structured SICETAC references by route, vehicle configuration and cargo type. Each delivery identifies its reference date, coverage and agreed format so your team can use the information in its analysis.

Complete SICETAC database

What it provides

A usable base for transport analysis.

The complete base is designed for companies that need a broad reference for analysis, monitoring and internal work with routes, configurations and cargo types.

01 · COVERAGE

Documented route coverage

A broad route universe for understanding the reference values behind a transport network.

02 · STRUCTURE

Configurations and cargo types

Work with the vehicle configurations and cargo types published in the SICETAC reference.

03 · ACCESS

Accessible for your team

Use the information in queries, analysis, internal comparisons and projects that need a structured source.

Use cases

From a route lookup to a real analytical capability.

AnalysisCross routes, configurations and cargo types for internal studies.
MonitoringKeep a reference available as published values and scenarios change.
ProjectsBuild dashboards, applications or internal tools around structured SICETAC information.
ContinuityConnect the base with SICETAC al Instante, the Network Index or the API.

Next step

Take SICETAC to the scale of your operation.

Tell us how your team needs to work with the complete route universe and we will define the appropriate access and scope.

Define the data delivery before you start

Database delivery and related services
ContentReferences by origin, destination and configuration available for the selected period, with fields and units identified.
CoverageThe delivery specifies the reference date and coverage. Route counts are distinguished from route and configuration combinations.
AccessOne-off delivery or recurring access, with format and update terms defined in the proposal.
Network analysisRoute matching and the Network Index require your operational data and have a separate scope.
IntegrationSystem connections and the SICETAC API have a separate technical scope.