Small wind / Buyer questions
Procurement and engineering handover
Can one software bill of materials cover wind controllers running different firmware builds?
The short answer
Use a software bill of materials, or SBOM, for the firmware builds the issuer identifies as covered. Controllers can share a model name while running different packages. If the supplier lists one SBOM for several builds, ask it to document how the listed components and versions apply to each build.
Record the software identity at handover
For each relevant controller, record the asset identifier, hardware variant where relevant and the installed firmware version or build identifier provided by the supported documentation or readout. Ask which firmware package, bundled software and optional components the SBOM describes. CISA’s guidance on software component transparency uses version information, component relationships and the identified primary component to make an SBOM interpretable.
Keep the supplier’s stated coverage limitations. If the document describes only the main firmware image, separately identify any gateway or supervisory application that the supplier lists outside that scope.
Connect the document to each deployed build
In a hypothetical staged handover, the first group of controllers runs one build and the second group runs a later build. The project can reuse a single SBOM only where the issuer establishes applicability to both. Otherwise keep separate references and identify the build awaiting documentation. A filename that contains the controller family is insufficient to decide the mapping.
Where a supplier identifies a particular package by a verified identifier or hash, preserve the association in the record without replacing the installed asset identity.
Use the map when a component advisory arrives
A later security advisory may name a component and a version range. The maintenance team can consult the mapping to determine which asset builds warrant supplier review. The SBOM records reported component presence and dependency coverage. Whether the advisory affects equipment in its actual operating context is a separate assessment. Agree who updates the inventory after a supported software change and how the previous mapping remains available.
Sources
Examples are illustrative. Confirm product-specific performance, compatibility and supply scope in the applicable documents.