Development Trend of highway engineering project management

I have been submitting bids for the Fujian project this week. I was notified today before I leave work, so I am busy. By the way, I would like to make a summary.

I. Why is Quality Management always a weakness?

 

This is exactly the case. China does not know how many quality management systems are called, and each system advocates how advanced it is. However, I pulled down a trial version from the Internet, but I felt that the function was too bad. In fact, I did not support a slightly complicated division of sub-projects. Naturally, I could not give an accurate summary score. It makes people feel that the software producer does not know how the project is divided.

Of course, this is only from the software perspective. From the perspective of actual operations, quality management is divided into two major parts:

1) Fill in the Quality form. Including the original table, monitoring table, and quality evaluation.

2) quality process control. Such as start-up, inspection application, and intermediate work handover.

In reality, the software should only include the "rating" in "form filling. Even this item is facing a lot of difficulties: the software can not only help the summary (the summary usually has a small amount of work), it cannot play a major role. This summary work is also related to software functions, and the functions are not strong. In this case, what should I do with the software?

At the same time, the software does not reduce the workload, but increases the workload on a program. The supervisor's signature was originally very convenient, and the speed of a table could basically reach 2 to 3 seconds. Now it is necessary to exhaust time, one open form, one signature, after the signature is completed, the contractor has to sign again after printing. I personally think that this is the essential reason why the quality management system cannot be promoted.

How can this problem be solved? I have already elaborated on the quality management system science and technology application, and there is no way to use electronic signatures. The electronic signature must be approved by the archive department.

Ii. Why is Progress Management just a false one?

 

There are also many progress management systems, and P3 has never been used. Projects and Menglong have a concept of collaborative work, And the rest seem to be in the standalone version. Unfortunately, collaboration is just a few people who can work on a progress chart at the same time. Then, without exception, these software attaches great importance to resource optimization.

As a road and bridge industry, progress control is not too complicated, at least not complicated to the extent that several people work on a diagram at the same time. From the perspective of the owner, resource optimization is only the internal management of the contractor, and you do not need to worry too much.

Is there no need for Progress Management in the highway industry?

None. It is not unnecessary, but a shift of focus.

I personally think that the focus of Highway Project Progress Management is to allow participants to grasp and control the project progress themselves at any time, and to assess the risk of the construction period (rather than dynamic resource optimization ), at the same time, the plan and completion information reported by the contractor are confirmed.

Based on this idea, I mentioned the following points in the "Dynamic Management System Technology Application for Construction Projects:

1) the C/S architecture is used, and a project has a central database.

 

2) support both general project management that facilitates the management of the owner and sub-project management that facilitates the input by the construction unit. The general project management is used for the overall arrangement and scheduling of the owner. The sub-project management is based on the construction bidding Section as the management unit. Each construction bidding section is used as a sub-project, and the bidding sections cannot be viewed from each other, however, the owner can view all the CIDR blocks.

 

3) based on the project decomposition structure WBS, the project can be decomposed at any level as needed to adapt to different management depths. WBS is associated with the engineering quantity list, and the computer automatically calculates the output value based on the current progress;

 

4) diverse graphical display methods and multi-level query methods;

 

5) summarize the key monitoring objects, progress of the total project, and output value of each bidding segment and each bidding segment at any time, and display the current progress using the frontend line technology;

 

6) Complete permission management (group and Role authorization) and workflow management mechanisms. The management permissions of each organization and operator can be flexibly defined, and the approval process can also be customized;

 

7) not only can the percentage of completion of a single project be displayed, but also the amount of physical work (such as the number of meters completed by the pier );

 

8) supports geographic location query. You can click a structure object on the map to display the current progress of the object. You can use a graphical display or a construction photo.

 

As for easyplan, we hope that it will be associated with wcost, which can combine the "budget cost" With WBS to generate Earned Value at any time according to the plan. I personally think it is useless. First, this architecture is oriented to the Project Department. Second, the "budget cost" calculated based on the project budget does not have much to do with the actual cost.

 

Iii. Why is fee management well developed?

 

It is very simple. Cost Management requires more computing, better accuracy, and higher reliability. This is the strength of computers.

 

Iv. possibility of introducing the "Middleware" and "Platform" Concepts in highway engineering project management

 

If I want to build a platform, I will only use the WBS management logic and work Permission Logic, work flow logic, network plan logic, and quality evaluation logic as the middleware of the platform.

 

Why ...... The Metering rules have changed too much, but the calculation is simple and tabulation is troublesome. The core logic of quality management and progress management is relatively fixed.

 

Then, you can plug in the various plug-ins.

 

5. Integrated Management is an inevitable trend

 

In fact, the concept of integrated management is no longer fresh, and the construction and hydropower industries are in full swing. It will sooner or later be the introduction of integrated management into the highway industry.

In the past, the Project Management System was mostly about metering and payment. Indeed, this is too simple. The quality and progress management software is basically in the standalone version.

Integrated management is an inevitable trend. If you don't need to talk about it, you can see the software in the construction field. Of course, there is also a communication language at the underlying layer, which is WBS.

Let's look ahead: Add a pile to the change. after entering the WBS information, the computer will know that this pile is under the pier of Pier X of the X Bridge in the X Contract Section, the number of I and II reinforced bars, the number of C30 reinforced bars, and the number of C30 reinforced bars are fixed, and the progress information is displayed. Click it to view the quality status and even the construction picture. How nice J

6. New opportunities brought about by Project Group Management

 

It was foreseeable for a long time that we met so quickly.

Each path requires a solution, which is too costly. Therefore, a software should be required to be reused as much as possible and used on multiple projects.

The idea is good. Well, it seems like there are some shortcomings.

By the way, isn't it possible? Take the metering of the three projects in Fujian as an example: the metering table cannot be the same, so the view layer is different. The logic layer may also be different, and the data layer will certainly not be the same.

Therefore, three projects are actually implemented. However, if the province is willing to converge the three project management methods, the software reuse degree can be improved as much as possible.

Why? Didn't the owner ask us to perform multi-project management? If the databases are different, in case I want to check how much the three projects have completed this year, I have to set a standard format first, will Project A, Project B, and Project C be converted to a standard format for statistics?

So if there are ten or twenty projects, is this small function not tiring?

Also, how much value will these heterogeneous databases be utilized in the future? It contains everything, the approval process, and the attachment. But as historical data, I only care about the results.

"…… Then we can extract all the project results and convert them into a uniform format. Why not store them in another library ?" Well, the "other database" is the data warehouse. This conversion process is called ETL.

The leader asked me to count Project A and Project B today ~ The amount of measurement in July. I need to count Project B and Project C tomorrow ~ Total amount of major changes in March. My God, which program can predict these "inexplicable needs "? If this is also called a "potential demand", there may not be a few talents to explore.

-- Now, OLAP is on the stage. This is specifically designed to address the changing needs.

The leader saw the report, but after reading it for a long time, he couldn't understand it. "What's worse? Small X. Come on, draw a bar chart ." "The bar chart is coming." "Oh, it seems that using a line chart can better express the meaning ?" "Dear leaders, the program does not provide this function ."

-- It's not slow. There are front-end data display tools, which can only be unexpected and cannot be done.

Haha, after talking about it for a long time, I just want to express the following meaning: Project Group Management should be integrated with Bi technology sooner or later.

VII. System Architecture

 

I'm tired, but I still have to finish writing.

B/S is now popular. In fact, B/S is not very good for project management, especially B/S, which has the largest opinion on the construction unit and has very poor interactivity, obviously cannot meet the requirements of a large amount of data input work.

But the analysis system seems to be quite good with B/S.

Data Collection System: C/S architecture. Data Analysis System: B/S.

But to be honest, Zhengyang helped our pb program to convert B/S and did not know what technology was used. After the transfer, All the operations were the same as C/S, it not only retains the advantages of strong interaction between C/S, but also the advantages of thin clients. Although it is a bit arrogant, I personally think this is quite good.

 

 

This is a part of architecture. Come back if you have time. After a few nights, you can't open your eyes.