News · TNE Platform · Infrastructure · BIM Expertise 7 May 2026
A platform for managing transport networks and the data on them
An open and configurable platform for managing transport network data through its whole lifecycle, from import and validation to storage and supply. Part of Triona's Infra Data Management Solution.
Why
Built for data that has to outlive the systems reading it
TNE Platform manages transport network data through its whole lifecycle. It holds the network itself and the objects positioned on it, with the history of both. Let TNE Platform manage the data, and integrate it with the other modules that register the data and the ones that use it.
The data model is yours. You define it in your own feature catalogue, and validation checks the data against the rules you set there. Import, validation and export run as configured jobs on a schedule, so the flows in and out are repeatable rather than rebuilt for each delivery.
- Efficient data management - the whole data lifecycle on one platform, from collection to use
- High data quality - validation against the rules you define, both on import and as a check on the data already stored
- One store with a history - version control and historical validity
- Scalable and configurable - modular, open architecture that connects to the systems you already run
- Your own data model - feature types, attributes, value domains, and relationships that you define
- Flexible deployment - on-premises, as an OEM component inside your own product, or as a cloud service
Features
The parts of the platform
-
TNE Studio
Where the work is scheduled and monitored. Create and track import, export, and validation jobs through a browser-based interface, and control who can read, write, and execute operations on specific resources.
-
TNE Catalogue Editor
Define and maintain your transport network data model. Configure the feature types you manage, specify their attributes, and determine how they connect to the network so the model can evolve together with your information needs.
-
Validation
Run quality checks against the rules you have defined across the entire dataset or only the changed data, ensuring that errors are identified and resolved before they affect downstream users and systems.
-
Segmentation
Automatically divide long roads into sections with consistent characteristics, creating reliable segments that support analysis, planning, maintenance, and procurement activities.
-
Application Server and Services
Connect TNE with the rest of your ecosystem through documented REST APIs, map services, synchronization capabilities between TNE systems, and support for custom plugins and job services when standard functionality is not enough.
-
Open Database Integration
Store and manage data in open, documented databases such as Oracle, SQL Server, and PostGIS, with optional ArcGIS geodatabase support. Standard GIS tools including ArcGIS, FME, and QGIS can access the data directly.
-
OpenTNF
Exchange transport network data through OpenTNF, an open format based on a single OGC GeoPackage file. This enables straightforward sharing of transport network and related data using an openly licensed standard.
Challenge
Data arrives from many sources, and it all has to end up in one registry
Transport network data comes in from field registration, from project deliveries, from other registries and from other organizations. Each source has its own data model, its own level of quality, and its own way of saying where on the network something sits.
Without one platform to take all of it in, the merging is manual, the checking happens late or not at all, and what the registry held last year is gone. A decision taken two years ago was taken against a network that has since changed, which is exactly what audits and contract follow-up ask about.
- Every source has its own model, and bringing them together is manual work each time
- Nothing checks incoming data against your rules before it becomes part of the record
- No record of the network as it stood on the date a decision was taken
Challenge
Closed storage and one-off integrations
A master database earns its name by being read. If the only way in is a proprietary interface and the only way out is a support ticket, every new consumer turns into a project, and the store you paid for turns into a dependency. An open platform works the other way around: it is configured to how your organization describes the network, and the tools you already run keep reading it, so taking it on does not mean changing the rest of your stack.
- A separate integration for every consumer of the data
- Standard GIS and analysis tools have no direct access to the data
- No open format for exchanging the data
- Bringing in a new store means changing the tools around it
Solution
From your data model to the data on someone else's screen
The platform covers the data lifecycle in four stages. Each is configured to your data model and your rules, which is why the same platform can carry a national registry and a single municipality's network.
-
Model
The feature catalogue defines how your organization describes and structures the transport network. Maintained by your own team, it provides the foundation for the entire information lifecycle, from import and validation to storage and data delivery.
-
Import and Validate
Bring data into TNE from field surveys, construction projects, external registries, and partner organizations. Before becoming part of the network record, incoming data is automatically validated against your defined rules and quality requirements.
-
Store with History
Network objects are stored together with their attributes, geometry, network location, and temporal validity. Historical versions are preserved rather than overwritten, making it possible to understand exactly how the network looked at any point in time.
-
Supply
Deliver data to the people and systems that need it, with the appropriate level of detail and without creating custom solutions for every use case. Information can be shared through REST APIs, map services, segmented datasets, database replication, or GeoPackage exports.
Who is it for?
Owners, managers, and users of transport network data
The platform is used by organizations that own, manage, or use transport network data and need a single store for it over the whole of its lifecycle.
-
National
Road and rail administrations
Running a national registry at national volume, where import, validation, and delivery have to work without anyone watching them
-
LOCAL
MUNICIPALITIES AND REGIoNS
Maintaining a local network, and delivering updates into a national registry without a separate export exercise
-
FORESTRY
FOREST ROAD OWNERS
Managing large private networks, where centralized data replaces local knowledge that walks out the door when someone retires
-
PARTNERS
SOLUTION PROVIDERS AND OEM PARTNERS
Building their own product on a transport network platform, embedded as an OEM component, rather than spending years building one
Contact
Start with the data, not with the product
Tell us what your data has to describe, and how it has to get in and out. We will tell you whether the platform is the right answer, and what it would take to run it where you want it.
Related links
