5 Ways to Handle Error Messages from the TS As-Built Inspection Tool Without Panicking

When using the TS As-Built Inspection Tool, you may encounter unexpected error messages when loading basic design data, checking measurement points or cross sections, or performing pre-checks before creating as-built management documents. On site, inspection schedules and submission deadlines are often tight, and simply seeing an error on the screen can make it feel as if work has stopped. However, an error in the TS As-Built Inspection Tool does not necessarily indicate a serious malfunction or an error in the measurement results themselves. In many cases, you can narrow down the cause by checking, in order, the data format, coordinates, measurement points, cross sections, file management, and operating procedures.

In this article, we outline five practical approaches to calmly respond when an error message appears in a TS as-built inspection tool. Because the displayed messages and operation procedures vary depending on the specific software environment and construction conditions, it is important to proceed while confirming the manual of the tool in use, the client's instructions, the applicable as-built management guidelines, and internal company rules.

Table of Contents

• Consider error messages from the TS as-built inspection tool by separating their causes

• Countermeasure 1: Check file formats and the items being imported

• Countermeasure 2: Review the coordinates and reference points of the basic design data

• Countermeasure 3: Check for inconsistencies in survey points and cross-sections

• Countermeasure 4: Inspect the correspondence between as-built measurement data and design data

• Countermeasure 5: Organize the work environment and record-keeping practices

• On-site judgments to avoid when handling errors and approaches to preventing recurrence

• Incorporate TS as-built inspection into the overall on-site verification flow

Consider Causes Separately for Error Messages in the TS As-Built Inspection Tool

When an error appears in the TS as-built inspection tool, the first important thing is not to immediately try to recreate the data. If you only look at the text shown on the screen, the cause may appear to be a single one, but in reality multiple factors can overlap. For example, even if the message says a file cannot be read, it may not only be due to the file extension or data format, but also related to the storage location, file name, character encoding, creation settings, the version of the data exchange standard, or missing referenced files.

In as-built management using TS, it is assumed that measured values obtained on site are checked against design values and organized as as-built management documents. Because basic design data, as-built measurement data, as-built management charts and tables, and electronic deliverables are interrelated, it is important not to dismiss error messages as mere operational mistakes but to adopt an attitude of checking where in the as-built management workflow consistency has broken down.

When responding to errors, first record the exact wording displayed. When you are in a hurry on site, you may be tempted to close the screen and try to recall the contents later, but even a small difference in an error message can change the cause. If possible, keep a record of the screen and briefly note the date and time it occurred, the data used, the actions taken immediately beforehand, the device used, and where it was saved. Simply having this record makes it easier to share information later with construction management staff, survey staff, client-side reviewers, and support personnel.

Next, broadly classify the errors. Separate whether they occur during loading, only for some measurement points or cross-sections after display, or during the report or checklist review stage. If the error occurs during loading, suspect problems with the file format or data structure. If it occurs only for specific cross-sections, candidates include measurement point names, cross-section shapes, as-built measurement target points, and the status of design value inputs. If the error occurs during report output or inspection/verification, check for missing required items, data correspondence, and omitted management item settings.

One point to be careful of here is not to assume that all on-site measurement results are unusable the moment an error message is displayed. Errors from the TS as-built inspection tool can indicate actual measurement mistakes, but they can also simply point to mismatches in data transfer or loading conditions. Even if the measured values are correct, if the association with the basic design data has been disrupted, the inspection tool may treat them as errors or warnings. Conversely, even if the tool can load the data, that does not mean you can skip confirming consistency with the design documents and reference points.

Therefore, the first action is to isolate where the problem occurs without assuming the cause. Check, in order, whether it stops at the file input, within the contents of the design data, during reconciliation with measurement data, or at the output/verification report stage. If you can make this isolation, you will avoid reverting work more than necessary and can get to the cause in the shortest possible time.

Countermeasure 1: Verify the file format and the target to be loaded

The first thing to check with the TS As-built Inspection Tool is whether the file you are about to load matches the format and intended use expected by the tool. On site, there are often multiple files with similar names—basic design data, construction management data, as-built measurement data, data converted for verification, and previously created backup copies. Furthermore, when files that include the same project name or the same route name are listed together, it is possible to accidentally load the wrong file.

Basic design data is the foundation for verification created from the design documents. In the TS出来形検査ツール, there are occasions when you need to check whether this foundation has been created properly and whether the information required for inspection and verification is complete. If an error message appears, first confirm whether the file you have loaded is basic design data, construction management data after as-built measurement, or verification data intended for another purpose.

When checking file formats, it is important not to judge solely by the extension. Even if the extension appears correct, the contents may have been created in a different format. Also, data that conforms to an older exchange standard may cause errors if you try to load it unchanged into the current validation environment. There are multiple generations of data exchange standards related to TS as-built data, and the formats supported and whether conversion is required can vary depending on the tools used and the client's operating procedures. When handling older data, it is important to verify whether conversion is necessary and to check the contents of the data after conversion.

Next to check are the file name and storage location. If a file name contains full-width punctuation, special characters, an excessively long string, or environment-dependent characters, loading can become unstable depending on the environment. This does not necessarily cause problems with every tool, but when isolating the cause of an error it is advisable to temporarily rename the file to a simple filename that indicates the project name, date, and data type and verify whether that resolves the issue. However, if you change the name of data intended for formal submission, confirm consistency with internal rules and the client's instructions, and always retain the original data before making any changes.

The storage location is another easy-to-overlook point. If you load data directly from shared folders, external storage media, syncing folders, or compressed files, you may encounter issues such as some referenced items not being found, lack of write permissions, or paths that are too long. When troubleshooting errors, create a working folder with a short path on the device, copy the target files there, and then load them—this makes it easier to isolate problems caused by the storage location.

Also, even for the same construction project, data may be separated by purpose—such as for client confirmation, internal review, or surveyor work. The file you open thinking it is the latest may actually be a pre-revision version. Check not only the date and time you received the data but also the creation date, update date, author, and details of revisions to clarify which file is the authoritative one. On projects where multiple people are working, rather than piling ambiguous suffixes like "final", "revised", or "re-revised" onto filenames, it is safer to manage them by specifying the date, version number, and purpose.

Many errors can be resolved by checking the file format and the items being loaded. In particular, when a process stops at the initial load, the quickest solution is to straighten out file management—the entry point—before suspecting the contents of survey points or cross-sections. If you skip this and start modifying the design data, you may end up backtracking because you were simply trying to load the wrong file. To avoid panicking over error messages, the basic step is to check the file type, format, version, and storage location one by one.

Countermeasure 2: Review the coordinates and reference points of the basic design data

If the file is correct but errors or inconsistencies still occur, the next thing to check is the contents of the basic design data. In particular, the relationships among coordinates, reference points, alignment, and survey stations greatly affect the verification results in the TS as-built inspection tool. In as-built management, measured points taken on site are matched to their designed positions, so if the design data's coordinate system or reference point information is misaligned, it can lead to various errors and anomalous displays in downstream processes.

When verifying the basic design data, the first thing to check is whether the construction control points have been entered correctly. Confirm that the control point names match the drawings and survey results, that the digits and signs of the coordinate values are not incorrect, and that there are no omissions in the elevation entries. Confusing the east/west/north/south directions of coordinate values, losing digits, mixing up units, and reusing old results are common mistakes on site. If even one control point is wrong, subsequent alignments and cross sections may look correct yet the overall position can be incorrect.

Plan alignment and longitudinal alignment are also important. Verify that the inputs for the start point, end point, key points, curve elements, and longitudinal change points match the design documents. Even if survey points appear continuous, missing intermediate change points, incorrect curve element input values, or reversed survey point directions can affect the positions of cross sections and the calculation of design values. If only some cross sections are displayed unnaturally on the screen of the TS as-built inspection tool, focus on checking the alignment conditions at those locations.

Checking the coordinate system is essential. If public coordinate systems, local coordinates, and site-specific temporary coordinates are mixed, you may be able to load the data but the positional relationships might not match. When creating the basic design data from design drawings, if coordinate transformations, rotations, or translations have been applied, confirm that those transformation parameters have been recorded. If the TS-side coordinate settings used on site do not match the coordinate settings in the basic design data, measured points can appear in unexpected locations.

The important point here is not to judge solely by what is displayed on the tool, but to return to the original source documents. Check the materials that formed the basis of the basic design data, such as design documents, alignment calculation reports, control point survey results, construction plans, and consultation records. In as-built management using TS, it is expected that design values and as-built values can be confirmed simultaneously with measurements and that the efficiency of report generation can be improved; however, as a prerequisite, the basic design data must have been prepared appropriately. Tools help detect inconsistencies, but the basis for deciding which values are correct lies in the design documents and the official survey results.

Also, when modifying the basic design data, always keep the pre-modification data. If coordinates or survey points are changed directly to resolve an error, it may become impossible to explain later why the changes were made. Record the reason for the modification, the locations modified, the verifier, and the verification date, and, when necessary, confirm with the relevant parties. Especially before inspections, it is safer not to change data based solely on an individual worker's judgment; proceed only after agreement with internal construction management and surveying personnel.

Inconsistencies between coordinates and reference points may appear as a clear error message, or they may manifest as a case where the data looks loaded on the display but the measurement results do not match. Therefore, you should review the coordinates and reference points in the basic design data not only when an error occurs but also whenever the display after loading appears inconsistent. To prevent rework on site, it is important to verify the basic design data against a checklist at the stage of creating it—not just immediately before inspection—and to share the correct data among stakeholders.

As countermeasure 3, check for inconsistencies in survey points and cross-sections

One common cause of error messages in TS as-built inspection tools is inconsistencies in measurement points and cross-sections. Even if the overall basic design data can be loaded, errors or warnings may occur for specific measurement points, specific cross-sections, or specific as-built measurement target points. In such cases, rather than the overall file format or coordinate system, you need to check the settings and names for each section and the correspondence of the target points.

First, what I want to confirm is the notation of the survey point names. If the notations of survey points in the design documents, the basic design data, and the on-site management records differ even slightly, the correspondence can break down. Differences in the number of digits, plus sign notation, full-width versus half-width characters, extra spaces, or even just a different rounding method for the survey point numbers can result in them being treated as different survey points. Because something that looks the same to the human eye can be handled as a different string in the data, carefully verify the names of any survey points that produced errors.

Next, check the number and positions of the cross sections. Verify that the design-required cross sections are not missing, that unnecessary sections are not mixed in, and that the order of measurement points is not reversed. Cross-section shapes are related to as-built control items such as reference elevation, width, and slope length. When checking the basic design data, confirm the measurement points and count of the as-built cross-section shapes, the reference elevation, width, slope length, and the assignment of symbols to as-built measurement target points. If error indications are concentrated on specific sections, reviewing these items will make it easier to identify the cause.

The symbols and names of as-built measurement target points are also important. Points managed on site—such as the left and right slope shoulders, slope toes, the center, and end sections—have specific meanings. If the symbols for these points do not match between the design data and the measured data, they cannot be correctly matched in the tool. For example, setting the left and right points reversed, having target points missing on only one side, or a point that exists in the design but is absent from the measured data can cause errors or warnings.

In locations where the cross-sectional shape is complex, care must be taken to avoid omissions in reflecting design changes or site conditions. If slope gradients, width, steps, side ditch locations, or interfaces with structures change during construction, the basic design data may remain outdated. Even if crews on site are working from the latest drawings, if the data loaded into inspection tools is from before the change, inconsistencies can occur. For cross-sections that show errors, confirm whether design changes were made, the details of any agreed changes, and consistency with the latest drawings.

When checking survey points and cross sections, it is effective to visually verify them not only with the on-screen list but also by using graphical and cross-sectional displays. If you look only at numerical values, it can be difficult to notice left-right swaps or flipped cross sections. Displaying the cross-sectional shapes and comparing them with the field topography and drawings makes it easier to find clearly incorrect locations. In particular, for works where cross sections are continuous along the longitudinal direction, such as road earthworks and river earthworks, comparing the preceding and following cross sections makes abnormalities easier to detect.

At this stage, be careful not to fix only the single cross-section that produced an error and call it done. If the data were created under the same rules, similar inconsistencies may remain in other cross-sections. Check the notation rules for measurement point names, the left/right point-naming rules, and the rules for setting target points, and verify whether the same problems exist throughout. If you fix only one spot right before inspection and the same error appears elsewhere later, work will stop again.

Inconsistencies in survey points and cross sections are more likely to occur when field personnel, surveyors, and data preparation staff have misaligned understandings. Taking error responses as an opportunity to clarify which survey points are to be managed, which points are designated as as-built measurement targets, and which drawings are to be taken as the authoritative reference will help prevent recurrence.

As Countermeasure 4, inspect the correspondence between as-built measurement data and design data

Even if the basic design data appears to be correct, if the correspondence with the as-built measurement data is broken, the TS as-built inspection tool may report errors or warnings. In as-built management, the as-built values measured in the field must be mapped to the design target points. If this mapping is misaligned, even though the measured values themselves exist, problems can occur such as the tool being unable to match them, treating them as out of scope, or displaying abnormally large discrepancies.

First, verify that the measurement data correspond to the project, the relevant section, and the target measurement points. When multiple sections are being worked on simultaneously, or when data in the same format are saved daily, you may end up loading measurement data from a different section. On site, survey point numbers are often similar, so you sometimes cannot determine this from the file name alone. Check the measurement date, the person in charge, the reference points used, the target scope, and the cross-sections measured to ensure they cover the same scope as the basic design data.

Next, verify the names and attributes of the measurement points. If the as-built measurement target points in the design data and the points in the measurement data do not correspond, they cannot be matched correctly. Even if you measure points such as the center point, end points, slope shoulder, and slope toe at the site, if the naming or attribute assignment differs from the design data, they may be treated as different points. If temporary point names were used on site, they must be mapped to the official target points during post-processing.

Pay attention to anomalies in measured values. Even if no error is displayed, when the difference from the design value is extremely large, possible causes include misidentification of measurement points, mismatch of coordinate systems, errors in setting the instrument station, or incorrect entry of prism conditions. In as-built measurement, it is not enough simply to have coordinates recorded; it is important that the correct points are being measured in relation to the design data. When you find locations with large discrepancies, check the on-site measurement conditions, instrument setup, backsight, the control points used, and any mix-up of the measurement targets.

Also, check the edit history of the measurement data. A different staff member may organize the data collected on site, deleting unnecessary points, renaming point names, or converting data formats. If necessary points have been deleted or point names changed during this process, errors will occur in the inspection tool. Rather than looking only at the converted data, compare the original measurement data with the converted data to determine which process caused the inconsistency.

When checking the correspondence between as-built measurement data and design data, trying to look at all points at once takes time. First, narrow the focus to measurement points showing error messages, points with large discrepancies, and points with missing displays, and then look for common causes from there. If the problem occurs only in the measurement data from a particular day, check the instrument settings and work procedures for that day. If it occurs only in data produced by a specific person, check for differences in point-naming rules and output settings. If it occurs only in a specific section, check for design changes or differences in control points.

The important thing here is not to aim solely at eliminating errors. If you delete the target points or force-fit point names, the display in the tool may improve. However, if the data becomes something that cannot be explained as actual as-built management documentation, it will cause problems during inspection. When handling errors, you need to consider making the data loadable in the tool and making it valid for as-built management together, rather than treating them separately.

To ensure the correspondence of as-built measurement data, it is effective to decide on point naming rules, the range of measurement points, target points, and storage methods before conducting on-site measurements. Rather than organizing after measurement, preparing the data at the time of measurement in a form that easily corresponds to the design data greatly reduces the burden of handling errors. The error messages displayed by the TS as-built inspection tool can also serve as an opportunity to review on-site measurement operations.

Countermeasure 5: Organize the work environment and record-keeping methods

If no major problems are found in the contents of the files or data, the working environment itself may be causing the error. Factors such as the device used to run the TS As-Built Inspection tool, the storage location, permissions, other files opened at the same time, the device’s update status, and the connection state of peripheral devices can all have an impact. Even if an error message makes it look like a data defect, sometimes simply changing the environment will allow the data to be read.

First, tidy up the working folder. If you are working directly with files that are still compressed, files on a shared folder, or files on external storage media, create a working folder on your machine and copy the necessary files there before checking. At this time, do not modify the original data; test using the working copy. If the copy can be read, the storage location or permissions may have been involved. If the same error occurs with the copy, you can more easily narrow the problem down to the data content or format.

Next, check whether the file is open in other software or by another user. In a shared environment, if someone else has the same file open or a synchronization process is underway, loading or saving can become unstable. For important pre-inspection checks, it is advisable to temporarily lock the data you will use and adopt procedures that prevent others from overwriting it while you work. Simply separating master data, verification data, and data under modification can greatly reduce confusion.

Check the device environment as well. On devices that have been used for a long time, the accumulation of temporary files, insufficient free space, permission settings, display settings, security settings, and so on can have an effect. Loading the same data on another device and checking whether the same error occurs lets you determine whether the problem is with the data or with the device environment. If it loads correctly on the other device, the original device’s environment may be the cause.

How records are kept is also extremely important in error handling. When an error occurs, if you record which data was used, which operations were performed, what was displayed, and what actions were taken, you can verify reproducibility when the same problem happens again. Without records, you may end up in a situation where someone fixed it previously but the method is unknown, causing the same investigation to be repeated each time. Keep a simple response history for each site, and write down the error that occurred, the cause, the action taken, and the verification results in writing — this will also be useful for handovers.

This record is intended not to assign blame but to reduce rework. When an error message appears and the person responsible tries to handle it alone, isolating the cause is delayed. If screen recordings, the files involved, the conditions under which it occurred, and the items that were checked are available, surveyors and construction managers can more easily understand the situation. Especially just before inspections or submission deadlines, the speed of information sharing is critical.

Also, do not forget to perform checks after resolving errors. Just because the loading error has disappeared does not necessarily mean the as-built management documents are free of problems. After responding to the error, check the basic design data, verify the relevant measurement points, reconcile with the as-built measurement data, and review the contents of the reports. Also confirm that the modifications made to eliminate the error have not affected other areas.

Organizing the work environment and records may not seem like a direct technical countermeasure. However, many of the reasons why on-site error handling drags on are management-related: not knowing where data is located, not knowing which version is the latest, not knowing who fixed what, and being unable to reproduce the same error. To use the TS as-built inspection tool reliably, it is essential to put operational procedures in place that include not only tool operation but also data and record management.

On-site decisions to avoid during error handling and approaches to prevent recurrence

Regarding error messages from the TS as-built inspection tool, there are decisions we want to avoid on site. The thing we most want to avoid is manipulating the data so that no error appears without first confirming the cause. Even if an error disappears from the display, if consistency with the design documents and measurement results is lost, the reliability of the as-built management records declines. When asked to explain during an inspection, you must avoid being in a situation where you cannot explain why those values or target points were chosen.

The next thing to avoid is reusing old data as-is. Using data from past projects or past sections as a template can itself help improve work efficiency. However, if the project name, station range, reference points, alignment conditions, target points, and management items remain unchanged, oversights can occur. In particular, for projects with similar structures, the on-screen display looks natural, making errors harder to notice.

Also, you should avoid postponing checks until just before the inspection. The TS as-built inspection tool should not be used for the first time immediately before inspection; it is safer to use it progressively within the workflow: after creating basic design data, for checks during construction, when organizing data after as-built measurements, and for verification before report generation. If you find errors or inconsistencies at an early stage, it will be easier to address them even if on-site verification or re-measurement becomes necessary. If they are discovered just before the inspection, stakeholder confirmations, data corrections, re-outputting, and re-checking all pile up at once, making decision errors more likely.

To prevent recurrence, it is effective to classify the causes of errors. Record them by categorizing into file format issues, base design data issues, coordinate and reference point issues, survey point and cross-section issues, issues with matching measurement data, and working environment issues. If a cause repeatedly occurs at the same site, review the work procedures. For example, if there are many mismatches in point names, share the point-naming rules before measurement. If many survey points are omitted, strengthen the verification procedures after creating the base design data. If files are frequently mixed up, review the folder structure and naming rules.

From the perspective of on-site training, it is important not to make error handling dependent on specific individuals. If only a particular person understands the cause, the team cannot respond when that person is absent. By sharing within the site the frequently occurring errors, the order of checks, reference materials, and precautions when making fixes, anyone can carry out the initial response. Not all staff need to understand the detailed data structures, but at a minimum they should have the ability to determine which stage the problem is occurring in.

Furthermore, it is important to distinguish between matters that require confirmation with the client or supervisory staff and matters that the contractor can confirm. Organizing file names and changing storage locations can be handled by the contractor, but inconsistencies with the design documents, incorporation of design changes, and the handling of control points may require confirmation among the parties involved. Proceeding based solely on on-site judgment can make it difficult to explain things later.

To turn error handling into a means of preventing recurrence, do not simply fix the issue on the spot; record why it happened, at which stage it could have been prevented, and what will be changed next time. Error messages from the TS as-built inspection tool are also signs that point to weaknesses in field operations. Rather than treating errors as nuisances to be avoided, treat them as material for improving data management, surveying procedures, and verification flows, which will reduce rework in subsequent construction work and future inspections.

Incorporate TS as-built inspections into the overall on-site verification workflow

To avoid being caught off guard by error messages from TS as-built inspection tools, it is important not only to prepare responses for when errors occur but also to establish on-site workflows that make errors less likely. As-built management is not work that happens only at the time of inspection. It is necessary to maintain data consistency throughout the entire sequence of processes: construction surveying, creation of basic design data, as-built confirmation during construction, post-construction confirmation, and report generation.

First, checks are carried out when the basic design data are created. If reference points, alignment, survey points, cross sections, and target points are verified at this stage, the risk of discovering major inconsistencies after construction can be reduced. Next, during construction, perform trial reconciliations using some of the survey points to confirm that the measured data correctly correspond to the design data. Rather than loading all the data only after construction is complete, making small checks along the way is the key to easing error handling.

At the site, clearly identify the points to be measured. Share in advance which survey point, which specific point, what name will be used, and which reference point will be applied for the measurement. If operators name points differently, inconsistencies will occur during post-processing. Skimping on this extra step in the field can lead to major rework when organizing data before inspection. With confirmation using the TS as-built inspection tool in mind, be conscious of acquiring data that is easy to reconcile from the outset.

In data management, it is important to establish a single source of truth. If working data, verified data, and data intended for submission are mixed together, it becomes unclear which one should be used. Separate folders should be used, version numbers managed, and a practice of not overwriting verified data inadvertently must be enforced. When corrections are necessary, retain the pre-correction data and record the reason for the change. This basic management makes it easier to trace the cause of errors.

Also, the on-site verification workflow includes both desk-based checks and field verification. If discrepancies or errors appear in the tool, it is necessary to determine whether they are due to a configuration mistake in the data or are caused by on-site construction conditions or measurement conditions. Simply correcting the data at the desk may be insufficient. When necessary, recheck the relevant points on site and verify that measurement points were not swapped and that there are no differences in the constructed shape.

In recent years, there has been growing demand to manage on-site location information, photos, point clouds, drawings, and as-built verification in an integrated way. Verifying with a TS as-built inspection tool is more effective when positioned not as a standalone task but as part of the site's overall digital verification workflow. If the locations of construction areas, design data, as-built measurement results, and site photos are well organized, it becomes easier to explain the situation when an error occurs.

LRTK Phone is an option for making it easier to obtain and record high-precision location information on site using an iPhone. To reduce error handling with the TS As-built Inspection Tool, it is important not only to check data immediately before inspections but also to leave information that will be easy to explain later from daily site records and location checks. If you want to streamline as-built management, photo management, location verification, and comparison with drawings on site, consider creating a site-recording system that leverages LRTK Phone together with improvements to the operation of the TS As-built Inspection Tool.