Differences between VIN and Hyperic mapping in vROPs?

VIN identifies and maps applications between VMs,  while Hyperic with vROPs maps relationships of applications to their parent VMs in vROPs.   I also noticed in the vROPS VIN dashobards that the VIN properties (ports and related VMs) is shown,  but cannot figure out how to access those properties in vROPS?

Any comparison charts to show the differences between the two with regard to vROPs?

Thanks,

-MattG