Just to confirm, @agirona95 is using the term “baseline” in its more generalized meaning, which in this case refers to a set of applications that must be installed on a given machine after it has been received from the vendor.
In BigFix, the term has a much broader meaning:
Baselines are collections of Fixlet messages and Tasks. They provide a powerful way to deploy a group of Actions across an entire network with a single command.
Baselines provide a way to maintain a common operating environment, making sure that all users in any given domain have the same software, patches, and drivers. Baselines are easy to set up, by selecting the Fixlet messages, Tasks, and other Baselines that you want to be a part of the group. To limit the scope of a Baseline, a Relevance expression can be used to target any subset of your network, using IP addresses, computer names, operating systems, and many other qualifiers.
For example, you might make a Baseline named “All critical hotfixes,” and populate it with all the current critical hotfixes available in the Fixlet list. Or you might create one named “Finance department baseline,” to keep that particular group of computers updated with the latest financial programs, financial tables, updates, and patches.
So a BigFix baseline can be used in this scenario, but you will have to manually create a Fixlet for every software product you need to install, which will include Relevance language to check if the software is missing from the machine. Then each Fixlet would be made a part of the BigFix Baseline - each machine’s client will evaluate the Baseline’s component relevance to determine which action of the Baseline to run.
I think you should also consider using Software Distribution module of BigFix Lifecycle: see here for details on using Software Distribution.