That was the way my thinking was leaning. I realized that a JobID is not the same as a uniqueid (like the IPAddressN column in the NodeIPAddresses table).
I'll cobble together something that merges the profileid with a homegrown id for the NPM instance.
Thanks for the input.