View Source

The newly designed needs assessment form conforms with the RTI standard form that is being used to collect data from customers.

|| \# \\ || Data Element \\ || Type \\ || Required \\
(Y/N) \\ || Value \\ || Description \\ || Note \\ ||
| 1 \\ | Title of Need \\ | Text \\ | Y \\ | \- \\ | A short title that describes the technology need (less than 125 characters including spaces) \\ | Used for keyword extraction \\ |
| 2 \\ | Need Description \\ | Text \\ | Y \\ | \- \\ | Clear, simple and complete one or two-sentence description \\ | Used for keyword extraction \\ |
| 3 \\ | Need Type \\ | Text \\
(Multiple \\
Selection) \\ | Y \\ | * Technology for new product development
* Technology to solve product problem
* Technology to solve process issue
* Technology skills/specialty resource | Scouting need time \\ | Not used for search \\ |
| 4 \\ | Time/Priority of need \\ | Text \\ | Y \\ | \- \\ | Time frame for finding the solution of the need \\ | Not used for search \\ |
| 5 \\ | Technical Challenges \\ | Text \\ | Y \\ | \- \\ | What is the problem/issue and why can't it currently by solved \\ | Not used for search \\ |
| 6 \\ | How solution will be used \\ | Text \\ | Y \\ | \- \\ | What internal (product/process/development) and/or external (supplier/customer/user/partner) factors \\
impact implementation \\ | Not used for search \\ |
| 7 \\ | Supporting Documents \\ | File \\
(Multiple Selection) \\ | N \\ | \- \\ | Supporting documentation or information that will assist in the technology scouting effort. This may include \\
current product/process specifications, standards, documentation on previously tried solutions, etc. \\ | Any file type - drawing, picture, doc file \\
can be uploaded \\ |
| 8 \\ | Permission to post to networks \\ | Enum \\
(Unique \\
Selection) \\ | Y \\ | * Yes
* No | Permission given by client to post a technology need request to networks \\ | Not used for search \\ |
| 9 \\ | Solution Spaces \\ | Text | N | \- \\ | Possible fundamental approaches, analog solutions, parallel industries etc. \\ | Can be multivalued. Each of the texts will map to a new keyword to search \\ |
| 10 \\ | Additional Keywords \\ | Text | N | \- | Known/common industry or technical terminology, synonyms, etc. \\ | Can be multivalued. Each of the texts will map to a new keyword to search \\ |
| 11 \\ | Solutions/Options already tried \\ | Text | N \\ | \- \\ | What are they, why are they unacceptable, and where/how can they be found \\ | Not used for search \\ |
| 12 \\ | Competitive Sensitivities \\ | Text \\ | N | \- | What information is confidential (e.g. company name, end product pricing) or which contacts should be avoided \\
(e.g. competitors, suppliers) \\ | Not used for search \\ |
| 13 \\ | Technology Criteria \\ | Text \\
(Multiple Selection) \\ | N \\ | \- | What are the technical attributes of the solution/source sought: e.g., physical/ chemical etc., properties, performance criteria, material/process type; maturity; registrations/certifications, qualifications/capabilities? \\ | For each of the criteria , \\
"Name" contains the criteria name \\
"Description" contains a short description of criteria \\
"Option" has to be one of these: must, could ,should \\ |
| 14 \\ | Business Criteria \\ | Text \\
(Multiple Selection) | N | \- \\ | What are the business considerations that a solution/source must meet: e.g., cost, time frames, volumes/quantities, market/competitive/geographical factors \\ | For each of the criteria , \\
"Name" contains the criteria name \\
"Description" contains a short description of criteria \\
"Option" has to be one of these: must, could ,should \\ |
| 15 \\ | Adoption Criteria \\ | Text \\
(Multiple Selection) \\ | N | \- \\ | What internal constraints exist for adopting the solution/source sought: e.g. skills, resources, developmental funds, facilities, safety, time frame; or external partner/ user/ application constraints/requirements \\ | For each of the criteria , \\
"Name" contains the criteria name \\
"Description" contains a short description of criteria \\
"Option" has to be one of these: must, could ,should \\ |
| 16 \\ | Preferred Solution Provider/Source Type \\ | Text \\
(Multiple Selection) | N \\ | * Technology provider
* Development partner
* Custom supplier
* Experts/specialist
* Other | Preference for the type of solution provider the company is looking for \\ | Not used for searching \\ |
| 17 \\ | Search Resources \\ | Text \\ | N \\ | \- \\ | Known trade and industry associations, experts, organizations, tools, references, certifications, databases etc. \\ | Not used for search \\ |
| 18 \\ | Technology Abstract \\ | Text \\ | N \\ | \- \\ | A non-disclosing description of the technology sought \\ | Used for keyword extraction \\ |
| 19 \\ | Cause of Challenge \\ | Text \\ | N \\ | \- \\ | How did the technical challenge arise or become apparent \\ | Not used for search \\ |
| 20 \\ | Impact of Challenge to Company \\ | Text \\ | N \\ | \- \\ | How will the company benefit from a solution, source, or new option \\ | Not used for search \\ |
| 21 \\ | Business Opportunity \\ | Text \\ | N \\ | \- \\ | The business motivation for addressing the problem/issue. \\ | Not used for search \\ |
| 22 \\ | Goal of Scouting Project \\ | Text \\ | N \\ | \- \\ | Desired outcome/goal for this scouting project \\ | Not used for search \\ |
| 23 \\ | Scouting Limitations/Boundaries \\ | Text \\ | N \\ | \- \\ | Geographical constraints, bound on the number of solution spaces, sectors, sources, or options not to consider \\ | Not used for search \\ |