Attribute mappings

Overview

Attribute mappings connect tender requirement specifications to your solution product attributes β€” proving each technical parameter in your offer matches or exceeds what the authority asked for. This is a per-requirement sub-page of Technical offer, not a separate sidebar module.

Final checkup flags incomplete mappings before submission. Exports embed compliance tables from saved mapping sets.

Tip: Before automap, confirm you have:

  • Added all solution parts for the requirement in technical offer

  • Team product specifications uploaded in inventory

  • Parsed requirement attributes visible in left panel (if empty, fix requirement spec text)

  • Saved technical offer changes before opening mappings

  • Planned manual review for safety-critical parameters (automap is assistive, not proof)

Caution: Leaving with unsaved mapping changes drops work β€” watch save status in topbar.


When this module appears

Condition

Accessible?

Supplies or services + technical offer active

Yes

Works pursuit

No β€” technical offer inactive

Requirement with attributes

Workspace loads

From technical offer

Map attributes action


How to open

  1. Your proposal β†’ Technical offer.

  2. Select a requirement with specification attributes.

  3. Click Map attributes.

Header includes Back to technical offer.


Layout

Flow diagram

Requirement attributes panel

Parsed specification fields from tender text β€” name, expected value, unit.

Solution attributes panel

Attributes from solution parts (team product specifications).

Mapping grid

Element

Description

Requirement row

Authority parameter

Mapped solution field

Your product field

Match indicator

Compliance hint

Unmapped warning

Still needs link

Topbar

Element

Description

Completion %

Mapped Γ· total attributes

Automap

AI suggests pairs

Save status

Unsaved changes warning


Key actions

Action

Result

Manual map

Link requirement attribute to solution attribute

Automap

Background AI suggestions

Save

Persist mapping set

Back

Return to technical offer (prompt if dirty)

Automap workflow

```mermaid

sequenceDiagram

participant U as User

participant M as Mapping page

participant AI as Automap service

U->>M: Click Automap

M->>AI: Start task

AI-->>M: Stream suggestions

U->>M: Review and save

```

automatic updates pause while you have unsaved local edits.


Numbered workflow β€” spec-heavy requirement

  1. Add solution parts in technical offer.

  2. Open attribute mappings.

  3. Run Automap.

  4. Sort by unmapped warnings β€” fix manually.

  5. Validate safety-critical rows against datasheet PDF.

  6. Save.

  7. Return to technical offer β€” repeat next requirement.

  8. Re-run Final checkup.


Empty and processing states

State

UI

Loading

Centered loading text

Load error

Red error β€” refresh

No requirement attributes

Empty grid β€” enrich specification

No solution parts

Add parts first

Automap running

Progress banner

Unsaved

live sync skipped


Downstream dependencies

Mapping data

Used by

Completed mappings

Technical export compliance table

Coverage %

Final checkup technical issues

Attribute values

Generated document variables


Multi-part solutions

Map each requirement attribute to the part that actually delivers it β€” not always part A.


Edge cases

Situation

Action

Automap wrong unit

Manual remap

Teammate overwrite

Save often; communicate

Attribute count mismatch

Split requirement in questionnaire

Zero attributes parsed

Improve spec text or manual attributes


FAQ

Is automap mandatory?

No β€” manual mapping always valid.

Does mapping change questionnaire status?

Indirectly via checkup only.

Can I map one requirement attribute to two solution fields?

Typically one-to-one β€” split requirement if needed.

Works pursuits?

Module unavailable β€” BOQ descriptions instead.

Export mapping table?

Part of technical offer document generation.

Retry automap?

Yes β€” replaces suggestions not yet saved.


  • Technical offer

  • Questionnaire

  • Final checkup

  • Team product (entity)

  • Datasheet upload

  • Specifications viewer