A Guide for Authors of Software — 2017 1 What is considered software writing or data set compilation? INL employees write many various software codes and data sets. This includes nontrivial spreadsheets, scientific or mathematical models, experiments designed to study data sets, or nontrivial customizations to existing software. This guide applies to all software and data collections that are not specifically exempted. What is technology transfer? For the purposes of this guide, technology transfer is the evalu- ation, protection, marketing, and licensing of software and data sets to various entities, including open source and proprietary licensing. Technology transfer can occur through publication, education and employment, participation in scientific meet- ings, and collaboration with industry through the licensing of innovations. Overview Defining technology transfer: the transfer of knowledge, ideas, discoveries and innovations to the public. Note: Some software is exempt from reporting. If any of the following apply, do not disclose the software in accordance with this guide. • The software is classified, deals with classified information, or disclosure of its existence may be used to infer classified information, or would create an identifiable risk to the detriment of national security, the confidentiality of government information, individual privacy, agency mission, programs or operations. If unsure, please speak to a classification analyst from Security Programs and Services before disclosing. • The software is for a National Security System.This does not imply that the software cannot be disclosed, but the author should speak with a security representative to determine if disclosure is appropriate. • The software is truly exploratory or disposable in nature, such as that written by a developer experimenting with a new language or library. • The software is simple configuration for existing software, trivial in nature and part of the normal configuration of that software. Key takeaways from this guide: • Always file a Software Disclosure Record (SDR) for any software you write for INL unless it is exempt. Do this early in the development process to avoid costly delays.This includes all software, whether or not it is intended to be released for an internal or external customer. • Never give INL software to anyone outside INL unless the laboratory has the rights to distribute the code and the transfer is made under a contract with intellectual property (IP) terms that support INL’s deployment strategy.This includes project collaborators from other DOE labs.Technology Deployment (TD) will assist in getting the proper agreement in place. • Never put third party software, images, fonts or other assets into INL software without recording its purpose and origination. • Software written for INL belongs to the laboratory. This guide outlines the process to make INL’s software legally available outside of INL. • Ownership of software funded by other entities follows rules established in the contracting mechanism. TD can help authors navigate what INL owns and what is owned by somebody else.