Run a concrete pour from request to record
Run the pour card loop end to end: raise the request, clear the pre-pour hold point, release and pour with the delivery tickets and cube samples, then record the test results and the as-built against the element.
작동 방식, 단계별로
플랫폼 전반에 걸친 4단계 - 각 단계에서 무엇을 하는지, 그리고 왜 중요한지.
Raise the pour request
양식 및 체크리스트Raise the pour request with the element, the location, the specified mix and the volume, giving enough notice for the inspection and the concrete order to line up.
이유: A pour called at short notice is a pour that skips checks. Requesting it properly gives the inspection its window and the batching plant its lead time, so nothing is rushed on the day.
Clear the pre-pour hold point
검사Inspect against the checklist before the pour: reinforcement size and spacing, cover, ties, formwork line and cleanliness, and any cast-in items in the right place.
이유: This is the last moment the steel and the formwork are visible. A hold point cleared here catches the error that would otherwise be entombed and only found when the cover meter comes out.
Release and pour
Construction ControlRelease the hold point and pour, logging each delivery ticket, the mix and slump on arrival, and taking the cube samples for testing as the concrete goes in.
이유: The tickets and samples captured during the pour are the proof the right concrete went in. Reconstructed afterwards they are worthless, so they have to be taken as it happens.
Record tests and as-built
Construction ControlRecord the cube test results at seven and twenty-eight days against the pour, and close the as-built record for the element, so the concrete has a verified strength on file.
이유: A pour is not finished when the concrete sets, it is finished when it is proven to strength on record. That record is what the structural sign-off and the eventual handover depend on.