What preparations are required for i-Construction 2.0? 5 steps seen in practice

Table of Contents

• Background and Preparatory Approach for Responding to i-Construction 2.0

• Step 1 First, review the entire operation and clarify the target processes

• Step 2 Next, establish data standards and operational rules

• Step 3: Solidify the on-site measurement system and equipment operations.

• Step 4: Build an internal collaboration framework to leverage 3D data

• Step 5: Advance the implementation plan by testing on a small scale and iterating improvements

• Summary: The outcome of i-Construction 2.0 implementation depends on the quality of preparation

Background and Preparation Considerations for i-Construction 2.0

What those responsible for practical implementation should grasp first when considering how to respond to i-Construction 2.0 is that this is neither merely a new buzzword nor something that can be resolved simply by introducing a particular piece of equipment. It should be understood as an initiative required in the shift from traditional paper-centered, experience-dependent, and process-segmented management to a data-centered construction management system, aimed at promoting on-site productivity improvements, labor savings, quality stabilization, and faster information sharing.

In practical work, when people hear "i-Construction 2.0," many will first think of 3D data, positioning, point clouds, as-built management, remote verification, and the digitization of construction records. Of course those things are important. However, what really makes a difference is not using individual technologies in isolation, but whether, within the workflow that runs from surveying through design, construction, inspection, and maintenance, you have organized which information is used, in what format, by whom, and at which stage.

At sites where preparation for implementation is inadequate, the order of deployment tends to be reversed. Teams start by discussing equipment and software first, and even if it appears useful in internal briefings, in the actual field problems arise one after another: coordinate handling is not standardized, data naming is inconsistent and hard to find, it’s unclear where measured values should be submitted, and there is a mismatch in understanding between construction and management departments. This leaves only a feeling of burden on the site and, rather than helping, actually increases resistance to digital adoption itself.

On the other hand, at sites where preparation is carried out appropriately, they do not try to make major changes from the outset. First, they identify within the company which processes have a lot of waste or rework, which are most susceptible to labor shortages, and which documents or records are dependent on specific individuals. Based on that, they begin with the areas where using 3D data and location information is most likely to deliver improvements. In other words, they think from an operations-first perspective rather than a technology-first one.

Organizing the preparations required for i-Construction 2.0 from an operational perspective makes them easier to understand by broadly dividing them into five stages. First, review the entire operation and clarify the target processes. Second, establish data standards and operational rules. Third, solidify the measurement system and equipment operation used on-site. Fourth, create an internal collaboration framework to leverage 3D data. Fifth, advance an implementation plan that starts small, tests, and iterates improvements.

These five are not simply listed in sequence. If a preceding stage is ambiguous, confusion will inevitably occur at the next stage. For example, if you start preparing data before the target process has been defined, it will be unclear what the data is for. If you begin measurements while data standards are still ambiguous, the results will be unusable later. Even if you create 3D data while internal coordination is weak, a gap will emerge between the field and management in how it is used. And without a mechanism for trial and improvement, it will end up as a one-off implementation.

Also, adopting i-Construction 2.0 does not need to take the same form at every site. The issues and the data required differ for roads, land development, rivers, facilities, areas around structures, and sites focused on maintenance. On sites that are widely spread out in plan, consistency of positional information becomes important, while in narrow sections or places with many obstructions, judging the appropriate measurement conditions is crucial. On sites where construction management is the focus, organizing as-built verification and progress records may come first. In other words, it is important to prepare while changing priorities to match your company’s work.

What matters for practitioners is not to view i-Construction 2.0 as a grandiose vision, but to concretely define how to change current operations to take a step forward. Ensure site records are kept in a way that anyone can understand. Reduce workflow steps that are prone to re-measurement and rework. Make it easier to explain by linking location information with photos, as-built conditions, and progress. The accumulation of these improvements will ultimately become the difference in responsiveness.

From here, we will take a detailed look at the five steps for actually moving forward with preparations, including common stumbling points during on-site implementation. Rather than desk-based idealism, by sequentially confirming—along the practical workflow—what to organize, what to decide, and what to try, it becomes easier to advance i-Construction 2.0 adoption as a realistic operational improvement.

Step 1 First, review the entire operation and clarify the target process

The first step is to review your company’s and on-site operations as a whole and clearly identify which processes will be targeted for i-Construction 2.0. If you skip this, preparation becomes scattered and you won’t be able to measure the effects of implementation. A common mistake is to start talking about measurement methods and 3D data simply because they seem necessary. However, in practice, initiatives that do not clearly define which processes they aim to improve will not take hold.

To clarify the target processes, you first need to break down the on-site work into detailed tasks. Pre-start checks, securing reference points, batter boards and layout marking, verification of finished form, photo management, progress reporting, preparation of coordination materials, tracking completed quantities, and responding to inspections — the daily work is divided into many small processes. For each of these, identify tasks that take a long time, tasks requiring multiple people, tasks that require frequent rechecks, tasks that involve transcribing records, and tasks where decision-making is dependent on specific individuals.

What’s important here is not just relying on on-site intuition, but putting the actual work burden into words. For example, concretely capture things like: each as-built verification requires two people and involves long travel times; photo organization takes half a day; re-surveys occurred due to coordinate-checking errors; after construction it was found that records were insufficient and reshooting was required. Once this kind of visualization is possible, it becomes clear where there is room for digitization and the use of 3D.

Next, you should start with processes that are likely to produce improvement effects. Trying to change everything at once makes the preparation burden too large. Especially in the initial implementation phase, it is important to choose processes where on-site personnel can feel the benefits of the changes. For example, starting with themes whose effects are easy to understand—such as simplifying verification tasks with records that include location information, stabilizing the accuracy of on-site checks using positioning, and making it easier to share pre- and post-construction conditions by utilizing 3D data—will make it easier to gain internal buy-in.

Also, when deciding which process to target, you need to determine whether it can be completed solely on site or whether it will affect interactions with other departments within the company or with the client. Improvements that can be completed solely on site are relatively easy to start, but their effects may be limited. On the other hand, improvements that take into account design review, construction management, preparation of inspection documents, and handover to maintenance tend to yield greater results, but require coordination among stakeholders. As a first step, it is realistic to begin with changes that are easy to implement within the site and then expand to the relevant departments once operations have stabilized.

One thing that must not be forgotten is that the appropriate target processes vary depending on site conditions. On earthwork sites that cover wide areas, topographic surveying, as-built verification, and construction progress monitoring are well suited. Around structures, position verification, interference checks, and ensuring recording accuracy are important. On maintenance-oriented sites, the reproducibility of inspection locations and the consistency of photographic records are important. In other words, implementing i-Construction 2.0 is not about applying technology uniformly, but about carefully selecting the processes that will deliver results according to site characteristics.

When defining the target process, you should also determine what final state you are aiming for. The preparations required will vary depending on whether you want to reduce working time, reduce variability in quality, create a system that can be operated by a small number of people, or make explanatory materials easier to understand. For example, if you prioritize time reduction, mechanisms to reduce duplicate data entry are important, whereas if you prioritize quality stability, standardization of positioning and coordinate management is important. If the goals remain vague, evaluations after implementation will also be vague.

Furthermore, in practice, the understanding and buy-in of on-site staff are indispensable. Even if directives are issued from above, operations will not continue unless those on the ground take ownership of them. When deciding which processes to target, it is important to gather input from the people actually performing the tasks and confirm where the burdens lie and what improvements would help. Preparations that are not tied to the problems faced on site tend, in the end, to become systems that go unused.

The state to be achieved in this step is that the company has shared which processes are targeted for improvement, why they are being targeted, and what the goals are after improvement. Once this is organized, moving on to the next step—establishing data standards and operational rules—won’t cause any ambiguity about what those efforts are for. The first step to successfully implementing i-Construction 2.0 is, before selecting technologies, to clarify the objectives and scope of operations.

Step 2 Next, establish data standards and operational rules

When the target process is decided, the next requirement is to establish data standards and operational rules. In adapting to i-Construction 2.0, many sites tend to overlook this area. While attention easily goes to measurement and recording methods, it is not uncommon to begin operations with basic rules left unclear—such as which coordinate system to use, how to name files, where to store deliverables, and who is responsible for verification. In practice, however, this ambiguity in standards generates the largest amount of rework.

What is particularly important is standardizing reference systems when handling location information. Even at the same site, if horizontal positions agree but vertical references differ, if there is no consistency with control points, or if the design and construction teams assume different coordinate origins, such issues cause major confusion in later stages. Data that were painstakingly collected cannot be compared or reused if their reference systems do not align. In other words, the value of digital utilization comes not from merely having data, but from data being correctly linked to one another.

What those responsible in the field should decide first are the reference points to be used on site, how coordinates are handled, how elevations are treated, and the assumptions applied during observations. These should not be left up to individual workers but organized as common on-site rules. What is needed is not the sharing of difficult theory but a system that ensures records are made under the same conditions regardless of who performs the work. For example, simply having basic operational procedures in place—clarifying the origin of the reference used on site, defining the items to check before measuring, and standardizing verification items when transferring data—will greatly reduce accuracy-related problems.

Rules for file management are just as important. On site, a large amount of data is generated daily, such as photos, point clouds, positioning results, drawings, reporting materials, daily reports, and inspection documents. If these are left to each individual's method of storage, they will not be found when needed, the latest version will be unknown, and it will be unclear who finalized what. If you are moving forward with i-Construction 2.0, at a minimum you should clarify storage locations, naming conventions, version control, who is responsible for updates, and the scope of sharing. If this is not organized, no matter how good the data you collect, it will not lead to effective utilization.

Also, the granularity of the information to be collected must be standardized in advance. If what and how much is recorded differs from person to person, the data cannot be compared or aggregated. For example, even when keeping progress records, if the recording units, update frequency, photo capture positions, and comment styles vary, the records will be hard to interpret when compiled later. Three-dimensional data and location information are easy to understand visually, but without sufficient contextual information they have no meaning. It is important to define up front the items required for later use, such as date and time, location, subject, work details, person in charge, and verification status.

Furthermore, operational rules need to be made in a form that can actually be followed on site. Even well-crafted rules will not become established if there are too many input fields, the verification steps are too complicated, or they do not match the workflow. In practice, balancing precision and operational burden is important. You should narrow the scope to what the site can reasonably maintain every day and design the system to reliably retain only the information that is truly necessary. Rules that can be sustained are more valuable than rules that are merely strict.

At this stage, deciding how to respond to abnormal situations in advance will stabilize operations. You should determine beforehand how to judge cases such as when positioning conditions are poor, when data loss occurs, when there are concerns about control points, or when recording omissions are discovered. Unexpected events will inevitably occur on site. If each incident is handled solely based on the person in charge’s experience or intuition, quality will become dependent on individuals. By establishing verification procedures and criteria for re-acquisition, you can reduce variability in judgment.

Establishing data standards and operational rules may at first glance seem like a mundane task. However, it is also the process that most increases reproducibility in responding to i-Construction 2.0. If there is a system in which anyone on-site can collect data under the same conditions, organize it according to the same rules, and share it on the same assumptions, operational improvements will accumulate as a company-wide mechanism rather than as one-off, site-specific improvisations.

By the time this step is completed, the goal should be that the data handled on site are connected. You should know what to check before measuring. You should know how to store data after acquisition. You should know who to hand it to and how to have them verify it. Only when this flow is clarified does the next step—establishing the measurement system and equipment operations—become meaningful. For i-Construction 2.0, preparing data in a usable form is more important than increasing the amount of data.

Step 3 Solidify the on-site measurement framework and equipment operations

Once the data standards and operational rules have been established, the next step is to firm up the measurement framework and equipment operation to be used on site. The key point here is not to line up the seemingly latest equipment, but to create a system that can be used reliably under on-site conditions. If you are swayed by the term "i-Construction 2.0 compatible," you may be tempted to adopt advanced measurement technologies all at once, but in practice, the top priority is ensuring sustained, continuous operation.

When planning a measurement system, the first thing to consider is the site environment. Whether the sky is open and positional information is easy to obtain, whether structures or trees cause heavy occlusion, whether you need to cover a wide area in a short time, or whether you need to carefully record fine structures — the appropriate measurement method changes accordingly. For example, at sites where obtaining positional information is easy there is much room for efficiency gains, but in heavily occluded locations you should plan on using alternative verification methods or supplementary measures in combination. The important thing is to design operations that are realistic and appropriate for the site conditions.

Also, the differences in skill levels among those responsible for measurements cannot be ignored. A system that only experienced personnel can handle will see quality decline as soon as the person in charge changes. If you want to establish i-Construction 2.0, it is important that anyone can operate at a consistent level of quality by following a fixed procedure. To that end, pre-checks, checks to be performed during measurement, and post-acquisition verification methods need to be standardized concisely. Since there is little spare time on site, short, to-the-point confirmation procedures are more effective than complex manuals.

In equipment operation, not only accuracy itself but also ease of handling, integration with record-keeping, and everyday usability are important evaluation criteria. In practice, even systems that are highly accurate become difficult to sustain if they take too long to set up, are burdensome to transport, or require separate work to organize records. What truly matters to field personnel is a set of tools that secures the required accuracy without interrupting the overall workflow. Particularly for frequent tasks such as daily as-built checks and location recording, operations that can be handled quickly and easily linked to records are required.

At this stage, the important thing is to clarify the accuracy requirements. Depending on whether even a difference of a few centimeters is unacceptable, whether a general overview is sufficient for construction management, whether the data will be used as inspection documentation, or whether it is for internal verification, the measurement system will change. If accuracy requirements remain vague, you will either carry out excessive measurements and increase waste, or conversely fail to meet the required accuracy and end up reworking. It is important to organize the information handled on site according to its purpose.

Furthermore, you must decide how to verify the validity of the measurement results. If it is unclear by what criteria the acquired positions and shapes will be checked for correctness, site personnel will continue to use them with uncertainty. Preparing confirmation procedures appropriate to the site—such as cross-checking with control points, comparing with known points, verifying by acquiring data multiple times, and confirming consistency with on-site visual inspections—increases confidence in the data. This is necessary not only to ensure accuracy but also to allow site personnel to continue using digital tools with confidence.

Also, equipment operation should not be considered in isolation but from the perspective of integrating it into everyday work. If measuring becomes an end in itself, it adds extra effort on site. Instead, aim for practices that are naturally incorporated into existing tasks—data that can be captured incidentally during pre-construction checks, updated as part of routine rounds, or stored together with photos and notes. Responding to i-Construction 2.0 will be easier to establish if it is seen not as adding special tasks but as measures to run current operations more reliably with less burden.

In on-site operations, practical issues such as connectivity, power supply, storage methods, and check-out management cannot be overlooked. No matter how ideal an operational plan is, if problems arise—equipment is unusable when needed, batteries run out frequently, check-out histories are unclear, or data transfers stall—field users will stop using it. It is important to design not only for technical performance but also to include the peripheral conditions required for daily operations.

The milestone for this step is having a measurement system that site personnel can use without hesitation. If it is clear when to use it, what to check, what level of quality to require, and how to handle the data after acquisition, measurement will become part of site management rather than a one-off event. Under i-Construction 2.0, the robustness of an operation that can be repeatedly used on site will determine outcomes more than the sophistication of the measurements.

Step 4 Create an internal collaboration framework to leverage 3D data

Even if a measurement system is established, that alone does not complete i-Construction 2.0 compliance. What is needed next is to build an internal coordination framework that leverages the acquired 3D data and positioning information. A common situation in practice is that field teams work hard to collect data, but other departments within the company are not able to make sufficient use of it. This leaves only the data-entry burden on the field and does not lead to results for the organization as a whole.

First, what you should review is the flow of which departments the data passes through. The information required differs depending on the people involved—on-site personnel, construction management, quality control, cost estimating, document preparation, management, and so on. What matters to on-site staff may be that information is tied to specific locations, while the management side may prioritize visualization of progress. Quality personnel will emphasize reproducibility of as‑built results and audit trails. In other words, even a single piece of data will be used differently depending on who looks at it. If you don’t understand these differences and merely drop files into a shared folder, they will not be put to effective use.

Therefore, within the internal coordination framework, it is necessary to clarify who looks at what for what purpose. Consider, in a connected way, what the on-site staff will input, what the management side will check, where reporting materials will be produced from, and what will serve as the basis for inspection responses. Once this is organized, on-site staff can reduce unnecessary data entry, and managers no longer have to search around for the information they need. The essence of data utilization is not collecting data, but making it easy to retrieve when needed.

What is especially important is not to make 3D data and positional information something that is only specific to the site. If information is understood only among the people in charge, it becomes vulnerable to personnel changes or site transfers. To ensure that anyone can understand it, it is effective to keep, along with the data itself, concise explanations, mapping to drawings, update histories, and verification status. This makes it easier for those with little field experience and for managers to grasp the situation, and improves the quality of internal explanations.

Also, when establishing an internal collaboration framework, it is necessary to adopt a perspective that does not limit the use of 3D data to only during construction. By broadening the scope to include pre-construction explanations, pre-start checks, as-built management during construction, progress reporting, records at completion, and handover to operations and maintenance, the value of the same data is increased. Rather than treating it as a one-off record, regarding it as an information asset that can be reused along the site’s timeline is an approach that closely aligns with i-Construction 2.0.

On the other hand, when promoting internal collaboration, it is also important not to aim for perfect integration from the start. Field teams and headquarters, younger and veteran staff, and construction and management departments have different levels of understanding and expectations regarding data. Because it is difficult for everyone to use it with the same level of engagement from the outset, it is better to begin with situations where collaboration is likely to be produced. For example, expanding internal use around themes where results are easy to see—such as making progress updates easier to understand, speeding up the preparation of meeting materials, and clarifying the basis for as-built verification—will make it easier to convey the value of its use.

Furthermore, clarifying the division of roles within the internal coordination structure is indispensable. If on-site staff have to shoulder everything, operations will not be sustainable. It is necessary to decide who will establish the rules, who will provide training, who will verify outcomes, and who will collect improvement requests. Especially in the early stages of implementation, a mechanism to ensure that small defects and usability issues that arise on-site are not left unaddressed is important. The more thoroughly an organization can identify and capture these issues, the more steadily its ability to respond will improve.

How you approach in-house training is also important. Simply explaining the overarching concept of i-Construction 2.0 compliance won't resonate at the worksite. What is needed is to concretely convey why the work will change, what this input will be useful for later, and what decisions the record will inform. When the background and purpose are communicated, it is more likely to be perceived not as mere additional work but as meaningful work.

The state targeted in this step is one in which the acquired data does not remain buried on-site but is used across multiple in-house processes. Information collected in the field informs management, management’s perspective is reflected in on-site input design, and as a result overall rework is reduced. Once this cycle is established, i-Construction 2.0 implementation begins to operate as an organizational mechanism rather than as the result of individual effort.

Step 5: Move forward with an implementation plan to test on a small scale and iterate improvements

The final step is to proceed with an implementation plan that starts small and cycles through improvements. The important point here is not to roll out company-wide as soon as preparations are complete, but to implement on the premise of a cycle of trial, evaluation, and revision. Adapting to i-Construction 2.0 is not something that will be completed in a single, plan-driven effort. There will always be issues that only become apparent when actually used on job sites. Precisely for that reason, an implementation plan that incorporates improvements from the outset is necessary.

Selecting the right site is crucial in a pilot implementation. If you start at a site that is too difficult, problems will become prominent and negative impressions of the implementation itself will deepen. Conversely, succeeding only at sites with overly favorable conditions will not lead to broader adoption. As an initial target, a site that has some room for improvement, is easy to gain stakeholders’ understanding, and allows basic conditions to be clarified is desirable. What matters here is not creating a success story, but obtaining learnings that can be standardized.

When running a trial, you should decide the evaluation criteria in advance. Looking at perspectives such as how much work time was reduced, whether rework decreased, whether it became easier to create explanatory materials, whether it became easier for a small number of people to handle, and whether data sharing became faster allows you to make improvement judgments rather than mere impressions. Especially in practical operations, an impression that something just “seems convenient” has weak persuasive power for internal rollout. If you ensure it can be evaluated from both quantitative and qualitative aspects, subsequent rollout will be easier to advance.

Also, recording failures during a pilot implementation is important. If you only summarize what went well, it will not be reproducible in actual operations. By documenting in which situations it was difficult to use, under what conditions accuracy or operability declined, where the data-entry burden increased, and who experienced difficulties, you can drive the next improvements. In fact, in the early stages of implementation, being able to identify issues quickly can itself be regarded as an achievement. Instead of hiding problems, it is important to treat them as material for improving the system.

The advantage of trying things on a small scale is that it can reduce resistance among on-site staff. If a comprehensive operational change is required from the outset, staff will be on guard. However, if you pilot within a limited scope and expand while making improvements, it becomes easier to gain acceptance. For practitioners, a mechanism that improves through use is more reassuring than a perfect system. The success or failure of implementation depends not only on technology but also on whether the workplace can accept it psychologically.

When running improvement cycles, it is essential to regularly gather input from on-site staff. If operations continue to be designed solely by management, small inconveniences in the field will accumulate and lead to disengagement. Conversely, if only field requests are adopted, overall optimization can break down. Therefore, it's important to set up review sessions where both field teams and management can confirm matters and decide what to keep and what to change. Organizations that have rules for improvement are more likely to sustain their i-Construction 2.0 efforts.

Additionally, when moving from trial to standardization, training materials and verification procedures need to be updated. The manual created at the outset is not necessarily optimal as-is. By reflecting practical workarounds found during trials, procedures that proved unnecessary, and expressions that were easily misunderstood, and by converting them into a form that is easy for on-site staff to use, operational quality becomes stable. Improvements only become meaningful when they are reflected not only in the field but also in the rules and training.

The goal at this step is to ensure that the introduction does not end as a one-off but continues on the premise of improvement. Rather than stopping after a trial, the situation should be organized so that it is clear how to roll it out to subsequent sites, under what conditions it can be replicated, and what should be retained as common rules. To truly turn i-Construction 2.0 into a capability of your company, the ability to implement and continuously improve is more important than the initial success.

Summary: The results of implementing i-Construction 2.0 depend on the quality of preparation

The preparations required for i-Construction 2.0 are not simply about introducing new technologies. It is important to review overall operations to define the target processes, establish data standards and operational rules, build a measurement system that can be used on-site, connect this to an internal collaboration framework that leverages three-dimensional (3D) data, and finally start small to test and iterate improvements. Only when this sequence is in place will benefits such as increased on-site productivity, labor savings, and improved explanatory capability become a reality.

In real-world operations, rushing implementation without sufficient preparation can cause even well-intentioned initiatives to end up increasing the burden on-site. Conversely, when preparation is carried out carefully, the same technology can produce significantly different results. The difference in i-Construction 2.0 readiness is not determined by how many things have been introduced, but by whether they have been translated into a form that can be operated on-site without strain. It is important to proceed in a manageable sequence while identifying where the current workflow has issues and which information needs to be connected to enable improvement.

Especially when you want to improve the accuracy of site records and construction management that include location information, considering operational methods that balance ease of use and accuracy at an early stage will raise the quality of preparation. If there is a system that lets you quickly capture position on site and easily link it to recording and sharing, supporting i-Construction 2.0 becomes something you can advance as a day-to-day practical improvement rather than a desk-based concept. From that perspective, iPhone-mounted GNSS high-precision positioning devices like LRTK are one option that advances the use of location information while keeping on-site implementation hurdles low. They are also easy to adopt if you want to start with a field-usable approach before making large-scale organizational changes, making them an easy-to-consider first step toward i-Construction 2.0 compliance.