7.7. 1 + 1 = 3?
Some NAC solutions may not be a single solution. You may need two or more NAC solutions, in combination, to address your organization's security and access control needs.
So, how do you work with various teams on different NAC solutions that need to, in the end, integrate (or, at least, interoperate) so that you can ensure network access control?
Working with separate teams on separate NAC solutions that you need to intertwine in some way works pretty much the same way as a singular NAC solution:
Try to build consensus for the NAC solutions within the different teams in the organization that you want to test and/or deploy the combined NAC solution.
Work with each team, allowing them to gain a better understanding of each other and their NAC needs.
Make each team comfortable when working with the NAC solution — and with each other.
NOTE
Integrating different NAC solutions requires more development time and interaction than working with a single solution. So, you may want to make the point person from each group that's deploying a NAC solution a representative of, or from development or engineering, someone who can make sure that all the pieces can come together and work. This approach ensures that at least some level of (technical) cross-pollination can occur.
If your organization is really large, then create a separate team geared for and with the goal of integrating the various NAC solutions to ensure that you have one team that can make it all work together seamlessly, and deliver your integrated, multi-vendor NAC solution on time.