Function: |
Technology Transfer - Evaluation |
Procedure |
Related Policies and Guidance: SUNY Patents and Inventions Policy; Guidelines for the Administration of Industrial Relationships; |
Contact: |
Office of Innovation and Partnerships (518) 434-7061 |
These Guidelines for the Evaluation of Software are intended to support high-quality, focused and efficient service to the SUNY research community. Technology Transfer (TT) professionals from across the system that have experience in evaluating software technology have collaborated to produce these guidelines. The RF makes these guidelines available to help administrators evaluate software invention disclosures and assess the marketability of the disclosed software technology. These guidelines are a living document that will be modified based on user experience and further aligned to meet best practices adopted by SUNY’s technology transfer professionals.
The initial step to assessing the marketability of any software invention requires a thorough review of the resources utilized to develop the software invention submitted by faculty.
This review can be conducted by employing the following mechanisms based on local preference:
Whichever method above is chosen the following information should be gathered from at least the lead creator or inventor of the software technology by the TT professional to facilitate a thorough assessment of the software technology:
A lists of the grants numbers and copies of any related contracts should be obtained and reviewed.
The responses to the questions and inquiries above will enable TT professionals to understand the extent to the RF’s ownership and control over the software technology that is being disclosed. Further, depending on the information provided by the lead creator or inventor of the software technology, the TT professional will help identify the barriers and constraints, if any, that the RF will have to consider when developing the software technology’s commercialization strategy with the development team.
RF Software Technology Addendum
Date |
Summary of Change |
March 1, 2017 |
New Document |