What’s the difference between i-Construction 2.0 and the conventional approach? A clear summary of the Ministry of Land, Infrastructure, Transport and Tourism’s new policy
By LRTK Team (Lefixea Inc.)
Table of contents
• The big picture you should grasp before understanding i-Construction 2.0
• What is i-Construction in the first place?
• What the conventional i-Construction has aimed for
• What changed with i-Construction 2.0
• The core difference: clarifying the shift from “productivity improvement” to “building sustainable systems”
• The three pillars of i-Construction 2.0
• What does automation of construction mean?
• Why enhanced data integration becomes important
• The direction indicated by automation of construction management
• Considering the differences between the conventional measures and 2.0 across the entire process
• Why i-Construction 2.0 matters even to beginners
• Its position as a core measure in the DX action plan
• Key points to keep in mind when interpreting future developments
• Summary
The big picture you should grasp before understanding i-Construction 2.0
When you see the term i-Construction 2.0, you might feel as if a completely new system or an entirely different set of measures has been launched. However, if you calmly look at the overall picture, it is easier to understand i-Construction 2.0 not as something entirely separate from the conventional i-Construction, but as a push to advance the initiatives pursued so far in a clearer direction.
Within that context, i-Construction 2.0 presents three pillars: automation of construction, enhanced data integration, and automation of construction management. What emerges from this is a change where, while inheriting the previous direction, clearer priority areas have been set. More importantly, whereas the conventional approach also aimed at improving overall productivity, 2.0 more explicitly emphasizes building a system that enables safe, high-quality infrastructure development and management to be sustained even with a small workforce.
Put simply, the conventional i-Construction was a broad initiative to “improve productivity across the entire process,” while i-Construction 2.0 can be organized as a new policy that, on that same trajectory, more clearly states the objective of “creating systems that can be sustained while maintaining safety and quality even with fewer people.” Beginners should first grasp this relationship: 2.0 does not negate the conventional measures but rather advances the prior thinking.
What is i-Construction in the first place?
What’s important in understanding i-Construction is the breadth of its scope. The conventional i-Construction has been a productivity improvement initiative that includes surveying and measurement, design, construction, inspection, and maintenance/renewal. The key point is that it does not end with construction alone. It is a framework that links the initial tasks of surveying and measurement to design, execution in construction, inspection, and further to maintenance and renewal.
From this, it becomes clear that i-Construction is not a single-task improvement but a way of thinking that spans the entire process. It is meaningful not to improve only one segment of the process but to enhance productivity in the flow where the preceding and subsequent steps are connected. The information obtained in surveying and measurement, the content organized during design, the execution in construction, the confirmation in inspection, and the use in maintenance and renewal are regarded not as isolated elements but as parts of a whole—this is the foundation of i-Construction.
Therefore, if you simply understand i-Construction as “a measure to make construction more efficient,” you can easily lose sight of the big picture. Of course, construction is an important element, but the conventional i-Construction was not a policy that isolated construction from the start. Rather, its characteristic has been aiming to improve overall productivity by looking broadly across the process.
What the conventional i-Construction has aimed for
To summarize what the conventional i-Construction aimed for, the centerpiece was improving overall productivity. It indicated a direction to raise productivity across a wide process that includes surveying and measurement through maintenance and renewal. The productivity improvement here does not simply mean shortening working hours; it is easier to understand as thinking to make the entire process proceed more smoothly and to improve the workflow.
In the conventional approach, each phase was not treated as isolated but was seen as having connections before and after. Starting from surveying and measurement, progressing to design, moving to construction, undergoing inspection, and continuing to subsequent maintenance and renewal—seeking productivity improvements across this entire sequence was the foundation of the conventional measures. In other words, even if one phase improves, it is not sufficient unless the whole improves, and the perspective of overall optimization was emphasized.
This point is important for understanding the difference with i-Construction 2.0. That is because 2.0 did not suddenly set an entirely new objective; it stands on the preexisting flow of improving overall productivity. Because of the conventional policy’s objective, the directions newly emphasized in 2.0 become easier to interpret.
Beginners are often easily confused by simply dividing things into “conventional i-Construction is old, 2.0 is new.” In reality, the conventional initiatives existed and 2.0 is positioned on that extension. The conventional i-Construction targeted productivity improvements across the entire process, and that way of thinking remains the foundation in 2.0. If you overlook that foundation, you may interpret 2.0 too narrowly.
What changed with i-Construction 2.0
When considering what changed with i-Construction 2.0, the first thing to note is that the conventional way of thinking has not disappeared. The conventional i-Construction also aimed to improve productivity across surveying and measurement, design, construction, inspection, and maintenance/renewal. Therefore, it is natural to understand 2.0 not as denying the conventional direction but as inheriting it and clarifying the priorities.
What becomes visible as a change is that the pillars are clearly presented. i-Construction 2.0 designates construction automation, enhanced data integration, and construction management automation as its pillars. While the conventional approach aimed at overall productivity improvement, 2.0 makes it easier to see where the emphasis will be placed.
A larger difference is that the description of the desired system has become clearer. While the conventional flow also targeted overall productivity improvement, 2.0 puts more emphasis on building a system that can sustain safe and high-quality infrastructure development and management even with a small workforce. From this wording, what can be read is that the focus is not merely on efficiency but on mechanisms that can continue into the future.
What is important here are the phrases “even with a small workforce,” “safe and high-quality,” and “building a system that can be sustained.” With these phrases together, 2.0’s direction can be organized as aiming not for mere labor saving, but for a state where work can continue even with fewer people while maintaining safety and quality. In other words, while the conventional measures supported productivity improvements across the wider process, 2.0 more clearly puts sustainability forward as a goal.
The core difference: clarifying the shift from “productivity improvement” to “building sustainable systems”
If the difference between the conventional approach and 2.0 is to be expressed simply for beginners, the core of the difference is that it is not so much that productivity improvement itself has changed, but that the objective beyond productivity improvement has been made clearer. The conventional i-Construction was a productivity improvement initiative targeting the entire process. This is a very broad and important way of thinking. On the other hand, 2.0 more clearly indicates what kind of state it wants to achieve through that productivity improvement.
In 2.0, creating a system that can sustain safe and high-quality infrastructure development and management even with a small workforce is strongly emphasized. The point here is that it is not just speed-ups or reductions in tasks. What is emphasized is the ability to continue maintenance and management with a small workforce without compromising safety or quality. With this framing, 2.0 is easier to understand not as a mere efficiency policy but as a policy aimed at building operational systems with sustainability.
The conventional i-Construction, of course, also aimed to improve sites and operations through overall productivity improvement. But 2.0 makes the ideal state beyond that more explicit. Improving processes is not the end goal itself; what is clearly put forward is building mechanisms that allow infrastructure development and management to continue while maintaining safety and quality even with few people.
This difference is not merely linguistic. It can be read as a difference in emphasis. While the conventional approach was a broad productivity improvement policy covering the entire process, 2.0, standing on that foundation, makes the objective of building a sustainable system more concrete. For beginners, it is more accurate to understand this difference not as a simple contrast like “efficiency before, automation now,” but as “2.0 makes clearer how to link the conventional productivity improvements to constructing systems that can sustain those gains.”
The three pillars of i-Construction 2.0
To understand i-Construction 2.0, the clearest method is to look at its three pillars in order. These three are: automation of construction, enhanced data integration, and automation of construction management. 2.0 presents these three as its pillars.
First, it is worth noting that while the three pillars may seem independent, they are actually closely connected. Even if only construction automation advances, if data integration is insufficient, the overall flow will be difficult to organize. Likewise, even if construction management automation progresses, if construction itself or data connectivity is weak, it will be hard to achieve a sustainable system. In other words, you should not look at 2.0’s pillars individually; it is important to understand them as a set.
Next, the way the pillars are positioned themselves reflects what is unique about 2.0. The conventional i-Construction aimed at productivity improvement within a broad framework including surveying and measurement through maintenance and renewal. That way of thinking remains unchanged. However, 2.0 organizes what it particularly emphasizes within that broad framework as these three pillars. This makes the priorities easier to see than before.
For beginners, it is easier to think of these three pillars not as newly added detailed measures but as a map showing what 2.0 values. How will construction change, how will data be connected, and how will management change? Viewing the whole from these three perspectives is the basic approach to reading 2.0.
What does automation of construction mean?
The first pillar of i-Construction 2.0 is automation of construction. This phrasing indicates that 2.0 seeks stronger changes in how construction itself is carried out. Construction was an important target in the conventional i-Construction as well, but 2.0 explicitly frames construction in terms of automation.
What is important here is not to understand construction automation as merely pursuing convenience. In a factual note, it is stated that 2.0 more clearly sets out building a system that allows safe, high-quality infrastructure development and management to be sustained even with few people. In other words, construction automation is linked to the direction of enabling continued work while maintaining safety and quality even when personnel are limited.
From this perspective, construction automation is not meant to change construction in isolation but is positioned as a means to support overall sustainability. Considering that conventional i-Construction aimed at improving productivity across the entire process, 2.0’s construction automation should be understood within that flow. The goal is not only to raise construction efficiency but to connect to a system where a smaller workforce can continue to maintain quality and safety.
Beginners may feel that “automation of construction” means construction has become the center of 2.0. But in reality, that is not the case. Construction automation is one of the three pillars and gains meaning when combined with enhanced data integration and automation of construction management. Construction alone does not automatically change; this pillar is positioned within the broader change that includes data and management.
Why enhanced data integration becomes important
The second pillar is enhanced data integration. This phrase is very important for understanding i-Construction 2.0. Since the conventional i-Construction is a broad initiative that includes surveying and measurement, design, construction, inspection, and maintenance/renewal, overall productivity improvement is hard to achieve unless each phase is connected.
When a policy targets the entire process, it becomes important that the information handled in the previous phase is linked to the next phase. If you consider surveying and measurement through maintenance and renewal as a single flow, the linkage of data within that flow has great significance. i-Construction 2.0 making enhanced data integration a pillar can be organized as making this idea of overall optimization more explicit.
Also, 2.0 clearly emphasizes building a system that allows safe, high-quality infrastructure development and management to be sustained even with a small workforce. To build a sustainable system with fewer people, it becomes difficult if information is fragmented across phases. The smoother the information transfer, the more likely operations as a whole will be sustainable with less strain. For that reason too, enhanced data integration is strongly tied to 2.0’s objectives.
For beginners, the term data integration may feel abstract. But considering that i-Construction’s scope extends across the entire process, the meaning of this pillar becomes easier to see. If you think seamlessly from surveying and measurement through maintenance and renewal, something needs to connect the phases—that role is played by the enhanced data integration emphasized in 2.0.
The direction indicated by automation of construction management
The third pillar is automation of construction management. Although this phrase may look similar to construction automation, it is important that emphasis is placed not only on construction itself but also on construction management. In other words, 2.0 intends not only to change how tasks are carried out but also to change how those tasks are managed.
The conventional i-Construction was a policy aiming to improve productivity across the entire process. Construction was a major element of that, but even if construction alone goes well, if management remains as it was, the overall sustainability may not improve significantly. Therefore, 2.0 explicitly lists automation of construction management as a pillar, showing a direction that goes deeper than before.
Moreover, considering the goal of building a system that allows safe, high-quality infrastructure development and management to be sustained even with few people, automation of construction management is a very natural pillar. Without a proper management system, it will be hard to continue operations with a small workforce while maintaining safety and quality. Thus, the emphasis on automating construction management in 2.0 can be understood as the need to rethink not only tasks but also how they are managed.
Beginners may think i-Construction is only about introducing technologies. However, seeing the pillar of automation of construction management reveals that 2.0 is not merely about technology adoption; it is about building systems that include a rethinking of management. Grasping this makes it easier to see why 2.0, while extending the conventional measures, is organized as a policy that places greater emphasis on systems and management.
Considering the differences between the conventional measures and 2.0 across the entire process
The differences between the conventional i-Construction and 2.0 are easier to understand when organized within the perspective of the entire process, not just individual terms. The conventional i-Construction was a productivity improvement policy that included surveying and measurement, design, construction, inspection, and maintenance/renewal. This means it viewed the whole sequence from start to finish as a single flow and sought overall improvement.
This broad perspective has not been lost in 2.0; rather, 2.0 takes that perspective as its premise. On that basis, it sets up three pillars—automation of construction, enhanced data integration, and automation of construction management—and clarifies where to place emphasis. In other words, the conventional approach was a broad productivity improvement policy targeting the entire process, and 2.0, while maintaining that broad target, makes the priority areas and the desired system clearer.
Also, while the conventional approach mainly appeared as overall productivity improvement, 2.0 more explicitly states the objective of building systems that can sustain safe, high-quality infrastructure development and management even with a small workforce. Viewing this difference across the entire process, it can be read that the emphasis is not merely on running the process faster, but on ensuring that the process can be supported without undue strain into the future.
For beginners, rather than memorizing the conventional broad-process policy and the three-pillar 2.0 as separate things, it is less confusing to understand them as “the idea of targeting the whole has existed since before, and 2.0 clarifies the priorities and objectives within that.” The scope was already broad; clarity has increased in 2.0. This organization most naturally expresses the differences between the two.
Why i-Construction 2.0 matters even to beginners
i-Construction 2.0 may look like a specialized policy name and feel somewhat distant to beginners. However, precisely beginners have reason to grasp this difference. That is because if you do not organize the conventional policy’s breadth and 2.0’s priorities, it is easy to misinterpret the overall picture when trying to understand i-Construction.
For example, if you think i-Construction is only about construction, you will miss that the conventional i-Construction covers surveying and measurement, design, construction, inspection, and maintenance/renewal. Conversely, if you regard i-Construction 2.0 as merely a change of name, you will overlook the three pillars—automation of construction, enhanced data integration, and automation of construction management—and the clearer direction of sustaining safe, high-quality systems with fewer people.
For beginners, the important thing is not to memorize difficult terms in detail. First, grasp that the conventional i-Construction is a productivity improvement policy targeting the entire process, and that 2.0 is a policy positioned on that extension which clarifies priorities and objectives. Once you understand these two points, when you encounter specific materials or explanations, it becomes easier to sort out what stems from the conventional thinking and what has been newly emphasized in 2.0.
Its position as a core measure in the DX action plan
One cannot overlook i-Construction’s positioning when trying to understand it. In a factual note, it is stated that i-Construction is positioned as a core measure in the DX action plan for the infrastructure field. This indicates that i-Construction does not exist in isolation but plays an important role within a larger direction.
What is important here is the expression “core measure.” It shows that i-Construction is treated not as one of many initiatives but as a policy placed at the center. Considering this positioning, understanding i-Construction and i-Construction 2.0 goes beyond knowledge of a single system or field. It should be read as a way of thinking close to the center when capturing the major directions of change in the infrastructure field.
Seeing these points together—the conventional i-Construction’s role in improving productivity across the entire process, 2.0’s clearer emphasis on building systems that sustain safe, high-quality operations even with fewer people, and that this is positioned as a core measure in the DX action plan—i-Construction 2.0 can be understood not as a partial revision but as a significant policy for thinking about the direction of the entire infrastructure field.
Beginners need not be intimidated by the word DX. What should be noted here is the fact that i-Construction is at the center of a major policy direction. Precisely because of that, it makes sense to understand the differences from the conventional approach and the three pillars. Rather than focusing only on specific technologies or individual process segments, treating i-Construction as a central policy is a shortcut to understanding.
Key points to keep in mind when interpreting future developments
When interpreting i-Construction 2.0, keeping a few perspectives in mind makes it easier to organize your understanding. First, do not forget the foundation that the conventional i-Construction was a productivity improvement policy targeting the entire process. The breadth that includes surveying and measurement, design, construction, inspection, and maintenance/renewal remains an important premise.
Second, grasp that 2.0 presents three pillars: automation of construction, enhanced data integration, and automation of construction management. This is the basic information for understanding what is being emphasized. When interpreting 2.0, it is important to consider these three pillars not only separately but as mutually connected.
Third, be aware that 2.0’s objective is not mere efficiency but more clearly focused on building a system that can sustain safe, high-quality infrastructure development and management even with a small workforce. Keeping this point in mind makes 2.0’s direction more concrete. 2.0 can be seen as inheriting the conventional idea of productivity improvement while more clearly linking it to sustainability.
Fourth, do not forget that i-Construction is a core measure in the DX action plan for the infrastructure field. This means i-Construction is not a peripheral topic but a central policy. Therefore, understanding the differences in 2.0 is not merely a matter of terminology; it leads to understanding future directions.
Summary
Summing up, i-Construction 2.0 presents automation of construction, enhanced data integration, and automation of construction management as its pillars. This change shows that priorities have become clearer than before. While the conventional flow also aimed at improving overall productivity, 2.0 more clearly states the objective of building a system that allows safe, high-quality infrastructure development and management to be sustained even with a small workforce.
Therefore, the conventional i-Construction can be organized as “a broad policy aiming to improve productivity across the entire process,” and i-Construction 2.0 as “a new policy that, on that foundation, more clearly defines priority areas and the building of sustainable systems.” With this understanding, 2.0 should be seen not as merely a new buzzword but as an evolution of the conventional initiatives.
Furthermore, i-Construction is positioned as a core measure in the DX action plan for the infrastructure field. From this perspective, i-Construction 2.0 is not a temporary topic but an important idea for thinking about future directions. Beginners should first grasp the two points—“the conventional approach already looked at the whole process” and “2.0 clarifies priorities and objectives”—to more easily understand the overall picture.
Understanding i-Construction 2.0 is not about memorizing difficult terms. It is about organizing what has become clearer on top of the existing foundation. If you focus on that, the differences from the conventional approach are not complicated: while inheriting productivity improvement across the entire process, the direction moves toward building systems that can sustain safe, high-quality infrastructure development and management even with a small workforce. That direction is the most significant characteristic of i-Construction 2.0.
Next Steps:
Explore LRTK Products & Workflows
LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.
LRTK supercharges field accuracy and efficiency
The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.


