Project Data From Manual Import

Design surfaces (.ttm)

Design surfaces can be manually imported into a WorksOS project as a Trimble Triangulated/Terrain Model (TTM/.ttm).

Ideally, the exact design prepared in WorksOS should be sent to the machine in the field so they have the same definition and can map progress and productivity consistently. Design surfaces use X,Y,Z coordinates for length, width, and height (elevations) dimensions.

Importing a design in the Imports window requires you to choose whether the TTM is a design surface or surveyed surface.

Once imported, a design appears as a blue, closed polygonal boundary on the Map screen. Boundary filtering can be used on a design to show only data inside the boundary. Design surfaces can also be used for Work Remaining cut/fill and volume calculations required to achieve the Finished Design surface.

Linework Files (.dxf)

Linework can be manually imported into a WorksOS project as a .dxf (a universal CAD exchange format) .

Linework provides you with visuals and guidelines for what a finished surface, structure, or area could look like when finished (or as a plan view while it is being built).

When importing a linework file through the Imports window, you must select the unit type in which the file was created in the source program (e.g., TBC). Selecting the wrong units for the data will cause linework to be displayed in the wrong place. 

Once you have imported linework, it will appear on the Map screen in its original colors. Linework files can be large, varied, and detailed to render and upload. In  WorksOS, they are for visualization purposes only,  i.e., to show what a virtual finished surface/road/project could look like. You cannot filter or interact with the data in any way.

Alignment Files (.svl)

Alignments can be manually imported into a WorksOS project as an .svl (a native Trimble Sitevision linework format). An alignment file contains an alignment centerline plus stationing/chainage (distance) start and end values within it.

Once alignments are imported, they appear as red lines on the Map screen, complete with stationing/chainage labels. Alignments can be very long and typically represent one or more road centerlines, i.e., the center of a new road being built. 

Alignments are used to spatially filter and report data for what is typically a road building project (as the alignment is the centerline of the new road).

The Alignment Filter allows you to select an alignment file and spatially filter the data for a set distance along it (which can be part or all). You can also specify how wide to sample left and ride of the centerline, e.g., to encompass one or more traffic lanes. 

Example:

The Station & Offset Report uses the same spatial filtering method to select data and also to specify the frequency at which you want to sample it in the report.

Surveyed Surfaces (.ttm)

Surveyed surfaces can be manually imported into a WorksOS project as a .ttm file.

A surveyed surface may come from a survey device, data collector, or drone; it represents a surveyed area at a given point in time and is used as a source of truth for the ‘as-at’ state of the surveyed project area. 

Surveyed surfaces combine with machine productivity data to form a composite surface where there are no spatial overlaps between the two. If machine productivity data and surveyed surfaces overlap spatially, then the most recent of the two supersedes the other in the composite surface. The date/time of the surveyed surface and the date/time for machine data are taken into account when producing the composite surface. There are data filter settings in WorksOS that can also control the two surface types.

Importing a surveyed surface in the Imports window requires you to select whether the .ttm file is a design surface or surveyed surface.

Once you choose a surveyed surface, you are prompted for a Survey Date/Time which determines the ‘as-at’ date/time for the surface. Any other data that overlaps spatially with this surveyed surface will either supersede or be superseded by it, depending on its own date/time.

Once imported, surveyed surfaces only appear visible on Elevations, Cut/Fill Quality Metrics, and in Volumes Calculations. They contain no pass counts, compacted meter value (CMV), temperature, machine drive power (MDP), or speed values, so they are not visible in those quality metrics and the detailed data view (DDV) tool does not pick them up either (shows machine data only).

Surveyed surfaces are imported:

In the Imports section you can toggle on/off all surveyed surface imports at once. This will work for all surveys that are not actively used as part of any Activity Setup.