Xây dựng một composição de custo unitário própria

Put the mao de obra, the materiais and the equipamentos into the catalog as priced insumos, each in the unit it is bought or paid in and each typed as labour, material or plant. An hour of pedreiro, a tonne of cimento, a productive hour of retroescavadeira.

Tại sao: Every composicao you write will lean on the same few dozen insumos. Priced once, a change in the steel price moves every composicao that contains steel in a single edit. Priced inside each composicao, the same change is a search through four hundred lines and some of them will be missed.

Decide how much of each insumo one unit of the servico consumes, and take the figure from a measured period on a real job wherever you have one. Where you do not, take it from a published productivity study and say which. Keep the loss and reuse factors separate from the productivity itself.

Tại sao: The coefficient is what the disagreement is actually about, and it is the only part of the composicao that a reader can test against their own experience. Written down with its source it becomes a conversation about how the work is done. Left implicit inside a unit cost, the same disagreement arrives as an accusation that the price is inflated, and there is nothing to point at.

Anything produced on site before it goes into the work is an auxiliar: the argamassa, the concreto feito em obra, the forma you assemble and use several times. Build each as its own assembly, in its own unit, from the insumos you have just priced.

Tại sao: The argamassa turns up in the alvenaria, the reboco and the piso, and it is one mix. Modelled once as an auxiliar it stays one number in three composicoes. Retyped into each of them it becomes three numbers that drift apart the first time the sand price moves, and nobody can tell which of the three is the stale one.

Build the servico as an assembly in the unit the bill measures it in, and give every component the quantity one unit of work consumes. Keep the equipment split between productive and idle hours where the machine waits on the crew, because the two are paid differently and averaging them hides both.

Tại sao: A unit cost that is the total of its components can be checked line by line by somebody who disagrees with only one of them. A unit cost typed in as a single figure has to be accepted or rejected whole, and in public work that means rejected, because there is nothing in it an analyst is able to approve.

Apply the composicao to its position so the unit cost on the bill is the total of the breakdown rather than a number somebody keyed in. Do the same for the positions that share the recipe and differ only in thickness, diameter or class.

Tại sao: A typed cost and its composicao stop agreeing the moment either one changes, and the bill is the copy everybody reads. Linked, the orcamento you submit and the calculation you defend are the same arithmetic, which is the entire reason for writing the composicao in the first place.

For each composicao propria record two things on the basis of estimate: that the reference systems carry no equivalent item, and where each coefficient and each insumo price came from. Name the job or the study, not the person.

Tại sao: Decreto 7.983 of 2013 permits a composicao propria where the reference systems fall short, and the permission is only as strong as the evidence that they do. Without that sentence the composicao reads as a way around the median rather than as an answer to a real gap, and it is the reading, not the arithmetic, that decides the finding.

Move the composicoes you are happy with into the cost database under codes you can search, with the reference month they were priced in. The next orcamento starts from these instead of from a published base you correct in the same three places every time.

Tại sao: A published base is a good place to start and a poor place to finish: its coeficientes are regional averages and its prices belong to a month that has passed. The version your own jobs have corrected is worth more than either, and it only accumulates if somebody puts it somewhere other than the last project folder.