Common HPCMP Procedures for Compliance with ITAR Restrictions
In October 2009, a CREATE team member expressed to the BC team a need for common HPCMP procedures for compliance with ITAR restrictions. The customer justified his request by pointing out that CREATE projects included a large number of ITAR codes and that the scheduling and tasking carried out by CREATE team will be significantly facilitated if all DSRCs used the same ITAR policy instead of multiplicity of policies, or no policy at all at a given site.
To begin with, the Baseline Configuration team working with an ITAR expert at the HPCMP, adopted Maui High Performance Computing Center's "International Traffic in Arms Regulations (ITAR) Requirements for MHPCC," Version 1.2, 10 June 2009, to produce the first draft of the "Common HPCMP Procedures for Compliance with ITAR Restrictions."
Upon review of the first draft of the policy, the customer proposed expansions based on recommendations made at an HPCMP Security Initiative Group (SIG) meeting held in the second half of 2009. The list of recommendations were then sent by the Lead of the BC project to the Director of Operations at MHPCC, and author of the original MHPCC ITAR Policy.
On March 23, 2010, the BC team received a revision that incorporated a solution for each of the recommendations made at the SIG meeting. On the same day, the Lead of the BC project forwarded a copy of the revision to the BC team and HPCMP.
In the subsequent four months, BC team members brought back from their respective DSRCs many ideas as well as concerns. The HPCMP ITAR expert worked diligently with the Lead of the BC project to incorporate all the applicable ideas and to eliminate all concerns raised by BC team members.
In a BC telecon that took place in the first week of August 2010, the BC team approved the final version of the "Common HPCMP Procedures for Compliance with ITAR Restrictions." A copy of the report was sent to the CREATE team on August 5, 2010.