b'A Guide for Authors of Software2017federal regulation to restrict its distribution, or if it may containHow long does the technology transfer information that would identify individuals in a way that mayprocess for software take?adversely affect their privacy.Next, a software specialist will gather information about theFor most software, it takes about six weeks to review the deploy-softwareits scope of applicability, the intent and wishes of thement options. It can take longer if funding sources, developers authors, directorate and funding sourcesto make a recom- and directorates have concerns, or if there are issues in licensing mendation to the Business Evaluation Strategy Team (BEST)arising from third party assets integrated within the software. supporting the directorate.To avoid delays, disclosures should be filed as soon as possible after development is started. This allows the technology transfer BEST (composed of directorate managers, INL patent attorneysprocess to be completed during the development phase and and legal staff, and TD commercialization managers) makesenables the software to be released the day it is completed. recommendations to the Director of Technology Deployment regarding IP for which the contractor should elect title, request the right to assert copyright, publish, disclose, deploy, and/orTips for Authors:invest.BEST can also recommend a deployment strategy to commercialization managers for assigned intellectual property,Complete the SDR as soon as it is known what the software will such as making the software freely available under open-sourcedo or the scope of the data set. Provide as much detail as possible. licenses. Alternatively, they may restrict the distribution inThe development of the software does not need to be nearing order to incubate the technology for further developmentcompletion; only the function of the software needs to be known.without the pressure of competition. In some cases, theList potential interested parties that may wish to use the software or software may be too sensitive or confidential for outside use,data so the software specialist may make a better recommendation and deployment options may be limited. for the release strategy.Once a tentative decision on how to release the software hasRespond to the TD office or legal team promptly when inquiries are been made, TD obtains the necessary concurrences (suchmade to avoid delays.as export control, counterintelligence, security, legal andKeep the TD office apprised of any third party code or other assets, management) and prepares the appropriate license if needed.such as open-source libraries that are included in the software so Depending on the strategy chosen, TD will market and licensethey can catch early open source licensing issues that may not be the software to optimally achieve INLs technology transfercompatible with the chosen release strategy.mission while taking into consideration the recommendations made by BEST and the other reviewers. Identify any additional authors, whether they are INL employees or not, to the TD office as soon as they are selected to work on the software.Inform the TD office if the software deviates from the disclosure, such Defining deployment strategy: the method by whichas adding additional functionality outside the original project scope.INL will deliver the software to third parties. MethodsInform the TD office of any upcoming publications or speaking include exclusive licensing, nonexclusive licensing, openengagements related to the software.source, government use only or publication.Choose the name of the software carefully to avoid potential trademark infringement. Contact TD prior to naming the software; they can perform a trademark search. Authors can also go to USPTO.gov to make a preliminary search.3'