UC3: Procurement package · stage: design
From a plain-language specification to structured procurement requirements.
A bid comparison is only as good as its input. Dundir is designing a language layer that turns a written specification into the hard requirements and weights the engine computes with, checked by a buyer before anything is compared.
The problem
Procurement professionals write specifications in plain language, or receive them that way from the project team. "500 m² of tiling, BRL-9010 certified, delivery before week 14" is a perfectly adequate description for a human, but not usable input for a comparison algorithm.
Hamppi's test at Skanska points the same way: the generative AI tool did best on well-structured bids. Uniform input mattered more than the model.
Hamppi's recommendation to Skanska
"Skanska should look into the possibility of demanding suppliers to fill their bids to a standardized bidding template because this would increase the accuracy of GenAI-based comparisons."
Hamppi 2025, p. 69: Aalto University / Skanska Talonrakennus Oy.
The design, in three steps
Read the specification
The language layer is meant to read the specification as written (PDF, ERP export, email) and pick out what matters for buying: quantities, certificates, dates, limits.
Define hard requirements and weighted objectives
It proposes a draft: which certificates are mandatory, the latest delivery date, the budget ceiling. The buyer checks and corrects it; nothing is compared until a person has signed off the list.
Export the structured procurement package
The package becomes the input for bid comparison (UC1) and supplier evaluation (UC2), and can go to suppliers as a uniform bid template, the step Hamppi recommends.
Procurement scan
Calculate your procurement cost
Five minutes. No registration. Straight away, your own estimate of the time and money your organisation loses to manual procurement.