I am sorry that this is not much help to you but I must say you are trying to use an automation tool as a monitoring tool and I think you will have some pretty major difficulties here.
For the point you have used as an example, BladeLogic is only interested on the properties of memory, not that it is 'working' or not.
Maybe some monitoring information could be captured, but even then you would need to run the job every time you wanted an update.
Yeah, I see what you're saying but if that were the case, why would BMC place hardware information as a part to collect on?
In other words, if you can't use the part just to verify it's existence, why have it? Having the parts listed, and if you can actually use them within the rule you're creating, one would have to change the rule every time you run the final job because the servers may change, one server may have more memory than another server, etc., etc., etc.
I would think if BMC has the part listed, at a minimum you'd be able to check the "amount" of memory, or the existence thereof. Same goes for disk, cpu, and network cards.
Does this make sense?
if you need to see how much memory is in the box there are other places to see this.