This issue, while pretty well-managed here, has taken over my week - just out-of-the-blue questions I've never come across before.... (My belief that PIs have secret meetings where they plan confusing issues to keep us on our toes remains firm! - just kidding- but it does feel like that...)
So, I'm now looking for ways for the Sponsored Programs team to communicate a little better with the Export Controls "team" (it's one person....) Here's my idea. But it's just the idea I've had; I'm not at all tied to it if there's a better idea out there.
I'm thinking of having the pre-award GCOs utilize a flag called something like "Potential Dual Use" if they are concerned that there's a possibility that the work being proposed is going to include an export control issue. I expect that they will over-use this flag - which is actually fine with me. The Export Controls person will be able to see these flags - or maybe he'd get an email when the flag is set. (Will Cayuse do that?) Whatever.... a weekly search for flags would be good enough. He will review and either remove the flag, with a note that he reviewed and there's no problem. Or, he will remove the flag and set a new one that says something equivalent to "Post-Award Staff Take Heed" Or maybe it will just say "Dual Use Expected." I could go either way ;)
And then the Post-Award GCO will know that there's an issue to be addressed. But also, if we flag the issue at pre-award we would have more time to pursue a license assuming the work will move forward in some limited way even if the work isn't funded.
So...what do ya'll do? Feel free to shoot this idea down and tell me your vastly better one. I'm good with that.
Andrea
------------------------------
Andrea Buford
Director, Office of Sponsored Programs
Oakland University
------------------------------