Software BOMs

What are best practices for software BOMs?

We only track hardware BOMs but a new requirement requires we track software BOMs also….

We have release BOM’s rather than sopftware BOM’s which we track in Epicor, using standard functionality functionality.
A new part number is created for each new release, for example

Release 2.002 contains

  • Mobile App V 2.2.2
  • UD Field CAB V17
  • API Verson 24
  • Epicor CAB V16
4 Likes
  • Mobile App V 2.2.2
  • UD Field CAB V17
  • API Verson 24
  • Epicor CAB V16

So these are all part numbers as materials within a part called “Release 2.002”?
or did I misunderstand?

Hi, yes, its nice and simple and works well for us

2 Likes