Caser / Kvalitet og sikkerhet
Kvalitet og sikkerhet

Automatiser en kontroll du ellers gjør for hånd

Ta kontrollen du kjører manuelt hver uke, bygg den én gang som en pipeline fra en ferdig mal, valider den slik at ingenting stille kobles til ingenting, og legg den i biblioteket slik at den kjøres på samme måte hver gang.

4 trinn14 minHovedentreprenørKostnadsrådgivning / kalkulasjonBIM- / digital rådgivning

Slik fungerer det, steg for steg

4 trinn gjennom plattformen - hva du gjør i hvert og hvorfor det betyr noe.

1

Start from a template

Pipelines

Open the pipeline builder and take the ready-made graph closest to the check you do by hand: flag positions still at zero, list the costliest items, guard a budget ceiling, or gate an export behind validation. It lands on the canvas already wired and already runnable.

Hvorfor: An empty canvas is where most automation ideas die, because the first hour goes on working out which port feeds which. Starting from a graph that runs on the first click means you begin by reading logic that works, and change it, rather than guessing at logic that does not.

InndataThe check you do by handTemplate galleryResultatA graph that already runsNamed pipeline
2

Point it at your own data

Pipelines

Swap the template's source for your own bill, catalog or validation findings, then set the numbers that matter on this job: the ceiling the budget guard trips at, the figure a threshold gate compares against. Add a computed column, a group and total, a rename or a fan-out where the shape does not quite fit, and a non-empty guard so an empty source stops the run instead of passing it.

Hvorfor: A template carries the logic, never your project's numbers. A ceiling left at the demo figure passes everything you feed it, which is worse than having no guard at all, because the run goes green and everyone believes a check was done.

InndataTemplate graphYour bill or catalogResultatGraph bound to real dataThresholds set for this job
3

Lint it, then run it

Pipelines

Read the issue count before you press run. It flags any step whose required input has no incoming wire, and any node sitting on the canvas as an island with no wire at all. Clear those, run the pipeline, then read what each step actually did rather than just the final total.

Hvorfor: A step wired to nothing does not fail. It simply never runs, and the pipeline reports success while doing less than the canvas makes it look like it does. That is the failure worth hunting, because a green run is precisely what stops anyone looking again.

InndataWired graphRequired inputs per nodeResultatIssue count at zeroA run with findings
4

Act on what it found

Validering

Take the findings through into validation, fix the positions they point at, and save the workflow so it shows up in the picker next month instead of being rebuilt from memory.

Hvorfor: Automation only pays back on the second run. A check that lives in one person's head gets skipped the week they are on leave, and on a long job that is reliably the week it would have caught something expensive.

InndataPipeline findingsThe positions they point atResultatCorrected positionsA check that now runs itself
Moduler

Moduler i denne playbooken

2 / 190 plattformmoduler

Mer innen Kvalitet og sikkerhet

Kvalitet og sikkerhet

Toolbox talk and safety check

Brief the crew on the hazards this shift actually carries, capture who was there, then prov…

2 trinn8 minÅpne
Kvalitet og sikkerhet

Get a material submittal approved

Put the product you plan to buy in front of the designer with its data behind it, get it ch…

3 trinn9 minÅpne