Technology Acceleration Project

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (36)

View Page History



|| Data Element || Type || Required? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered ||
| Company Name | String | Y | The formal name of the company | This will help us identify every company which is entered into the system. We can also align the field with the company name field from other data sources and readily import / export information as and when needed. This is the only company related mandatory information that the system maintains. \\ | The field is the most basic requirement for the system. The field aligns itself with the company name field in most of the similar other forms by \\



|| Data Element || Type || Required?(Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Street Address \\ | String \\ | N | The formal street address | The field will hold the street address of company location. The field can be aligned with fields like street-address, address-line-1 from other data sources. The information will be primarily used for making any direct contact with the company. | The field aligns with street address field from contact information for company. \\



|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Status | Enum (Unique Selection) \\
\\ | * Private
\\ * Public | Appendix 1 | N | The field holds the value for the IPO status of a company. As of now we have two possible values that a user can select (exclusively). The values are mentioned in Appendix 1. | The field captures the status of the company with respect to it being public or private. It can be a preference bit when companies try to find the solution(s) to their needs. The field can be aligned with the IPO-status field in other databases. | The field was added to keep a track of the status of companies. The status is not captured by the forms like NIM. The field was added as a result of discussion between *ERA people and the TMAC engineers*. |
| Number of Employees \\ | Enum (Unique selection) | * 1-10
* 11-50
* 51-200
* 201-500
* 501-1000
* 1001-5000
* 5001-10000
* 10000\+ | Number of Employees \\ | Enum (Unique selection) | Appendix 2 | N | The field holds the value for the number of employees in the company. The list of value was taken from "Linkedin" after exploring the web for some standard established (which unfortunately there isn't). | The field captures size of the company. It can be a good candidate attribute to classify companies. The field can be aligned with the Company-Size, Number of Employees fields from other similar databases. | The field aligns with fields from  \\
*1) Linkedin* \\
2) www.manta.com \\
| Unique Features | Text | \- | N | The field holds the information about unique features for the company. The features distinguish the company from others (makes it stand out in crowd). | We decided to split the company capabilities into company capabilities by category and unique features. The field unique features will be a tag line for the company and will be given higher weight while matching the needs to solution. | The field aligns with the Unique feature field of the *NIM* form. \\
It was agreed to add the field in the meeting with TMAC engineers as they pointed out that the field had higher significance and should be treated separately. |
| Company Capabilities \\ | String (Multiple Selection) \\ | (Categories)\\
* Core Capability
* Material
* Min/Max dimension
* Tolerance
* Secondary Operation
* Packaging
* Lead Time
* Application/Benefit
* Other | Company Capabilities \\ | String (Multiple Selection) \\ | \- | N | The user could add capabilities (specialties) of a company and arrange according to decreasing priority by dragging and dropping the added capabilities. We aim to use the entered capabilities as features describing a company and possibly giving companies as solutions to needs (from other companies). As a part of this field user will select category of the capability he (or she) wishes to enter and then describe the actual capability in the text box and hit add button. The system will note down the capability as a key-value pair of capability category and capability description arranged in priority. The capability categories could be seen in Appendix 12. \\ | The field captures the strengths (qualities) of company. It can be helpful for creating tags in the company space and analyze how companies cluster based on similarities and differences. It can also be used to align a possible company as a solution to a need by matching the need requirements to the company capabilities. Note: In phase 1 we are only targeting having academia entities as the solution space. Presenting companies as solution will be one of the goal in next phase. The field can be aligned with fields like company-strengths, company-qualities from other databases. | The field was selected as a discussion within the *ERA group and the TMAC engineers*. The purpose to the field is to create a feature matrix for companies that will eventually allow the system to present the matching companies as solutions. |
| Average Annual Sales \\ | Enum&nbsp;(Unique Selection) \\ | * < $500,000
* $500-$1M
* $1M-2.5M
* $2.5M-$5M
* $5M-$10M
* $10M-$20M
* $20M-$50M
* $50M-$100M
* $100M-$500M
* $500M-$1B
* > $1B | Average Annual Sales \\ | Enum&nbsp;(Unique Selection) \\ | Appendix 3 | N | The field describes the values for average annual sales for companies in terms of USD.&nbsp; \\ | The field captures the annual sales of the company and can be used as an estimation into the growth of the company. The values selected for the field are from the website: www.manta.com The website was referred to in the discussion with TMAC engineers about the average annual sales (values) and was used as the baseline. | The field&nbsp;reflects&nbsp;the economic condition (growth) of a company. The values of the field were taken from: \\
*1) www.manta.com* |{table-plus}




|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Company \\ | Enum (Multiple Selection) \\ | \[NAICS Category(ies), NAICS Sub-Category(ies)\] \\ | N | A user can select a category and sub-category (with respect to the category selected). If the user selects multiple values then he can prioritize them in descending order with dragging and dropping the item in the list of selected values.Attributes @ Need \\ | The field aligns itself with the NAICS codes associated with companies to provide better classification information for companies. The usage of NAICS code for classification enable the system to import data from company database that associates companies with the NAICS code. The classification information would help the system to cluster the companies according to the areas in which they work. This will help the mapping of solution space to the problem space. In doing likewise the system will now map the solution categories (discussed further) with the company categories (instead of an individual company) making the system flexible, easier to maintain and more efficient. \\



|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Need Title \\ | String \\ | \- | Y | It is a caption / tag line / a one line description of the need. \\ | The field captures the gist of the need in succinct manner. It can be therefore used as an important feature in need to solution mapping. \\ | The system intends to capture different needs of companies. The need title is the headline (caption) for a&nbsp;particular&nbsp;need. The field was agreed in a meeting between *ERA and TMAC engineers*. The field should align with any field indicating company requirements. The field does not readily align with a field from any of the existing sources (to the best of my knowledge). There is a field on the NIM (planet Eureka web-site) which is more detailed and specific regarding the need description and does align well with our need description field (as stated next). |



|| Data Element || Type || Value || Required ? (Y/N) || Description || Existing Systems, Tools and Processes Considered \\ ||
| Title \\ | Enum (Unique Selection) \\ | * Mr
* Ms | Title \\ | Enum (Unique Selection) \\ | Appendix 4 | N | The field holds the title for primary contact for the need. | The field reflects basic requirement to capture the contact details of a person responsible for a particular need. The field is new in sense all the online sources we analyzed have a company specific contact address but no Need specific contact address. The set of fields were captured as a part of discussion of *ERA and TMAC engineers.* |
| First Name \\ | String | \- | N | The field holds the first name of the primary contact for the need | The field reflects basic requirement to capture the contact details of a person responsible for a particular need. The field is new in sense all the online sources we analyzed have a company specific contact address but no Need specific contact address. The set of fields were captured as a part of discussion of&nbsp;*ERA and TMAC engineers.* \\ |
| Last Name | String | \- | N | The field holds the last name of the primary contact for the need | The field reflects basic requirement to capture the contact details of a person responsible for a particular need. The field is new in sense all the online sources we analyzed have a company specific contact address but no Need specific contact address. The set of fields were captured as a part of discussion of&nbsp;*ERA and TMAC engineers.* \\ |
| City, State | String =>&nbsp;\[String, String (Comma separated)\] | \- | N | The field holds the City and State information of the primary contact for the need \\ | The field reflects basic requirement to capture the contact details of a person responsible for a particular need. The field is new in sense all the online sources we analyzed have a company specific contact address but no Need specific contact address. The set of fields were captured as a part of discussion of&nbsp;*ERA and TMAC engineers.* \\ |
| Zipcode | String | \- | N | The field holds the zipcode of the primary contact for the need | The field reflects basic requirement to capture the contact details of a person responsible for a particular need. The field is new in sense all the online sources we analyzed have a company specific contact address but no Need specific contact address. The set of fields were captured as a part of discussion of&nbsp;*ERA and TMAC engineers.* \\ |
| Country \\ | Enum (Unique Selection) | Appendix 5 * United States | N | The field holds the country information of the primary contact for the need Currently we only have "United States" as the value. | The field reflects basic requirement to capture the contact details of a person responsible for a particular need. The field is new in sense all the online sources we analyzed have a company specific contact address but no Need specific contact address. The set of fields were captured as a part of discussion of&nbsp;*ERA and TMAC engineers.* \\ |{table-plus}

h6.



|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Related Growth Areas \\ | Enum (Multiple&nbsp; Selection) \\ | * Technology Acceleration
* Continuous Improvement
* Sustainability
* Workforce
* Supplier Development
* Others | Related Growth Areas \\ | Enum (Multiple&nbsp; Selection) \\ | Appendix 6 | N | The field indicates the 5 growth areas indicated by NIST. The values selected will help the system to learn the motivation behind the need and align the need better with the selected growth areas. \\ | The five growth areas are specified by NIST as a part of the initiative. The field captures the association of a need to a particular growth area. A need can actually associate with more than one growth areas. \\ | The field aligns the need to the 5 strategic growth areas as indicated by *NIST*. \\ |
| Capital Needs \\ | Text | \- | N | The field describes any capital requirement for satisfying the need. The field was highlighted in a meeting with engineers of TMAC where it was indicated that this will be one of the important aspects (feature) of the need to capture. The solution search system can use this feature as a constraint to rank the results appropriately. \\ | The field captures the description of any capital needs that (or an estimation). The field can be used to match the need against any funding opportunity information the system may leverage. | The field is a new piece of information captured. It was added to the list of questions after voted important by *TMAC engineers*. |
| Capital Amount \\ | Enum \[Unique Selection\] \\ | * 10K-50K
* 51K-100K
* 101K-500K
* 501K-1M
* 1M\+ | Capital Amount \\ | Enum \[Unique Selection\] \\ | Appendix 7 | N | The field will give an estimated price of the solution. The field was highlighted and quantified in a meeting with TMAC engineers. \\ | The field will capture the dollar amount (estimated) that is needed by a company. Its a quantity and can reflect on financial standing of a company, ability of a company to grow, etc. The values of the same were d \\ | The field was captured in discussion with TMAC engineers. It aligns itself with the "*Estimate of cost for sale*" field in the NIM website for adding innovation. |
| Funding Source of Interest \\ | Enum \[Multiple Selection\] \\ | * Internal Funding
* State Funding
* Federal Funding
* Angel Investors
* Venture Capitalist
* Bank Loan or Financing
* Grants | Funding Source of Interest \\ | Enum \[Multiple Selection\] \\ | Appendix 8 | N | The field will help the system understand the scope to search possible funding opportunities. This information can be aligned with any network of funding sources and a partnership could be created to provide the results of possible funding sources that the companies would like to explore. \\ | The field captures preference for the funding opportunities with respect to the need. \\ | The values of the field were populated as a result of inputs from *TMAC Engineers and ERA people.* The field is new and does not align with the fields from existing sources. |
| Development Status \\ | Enum \[Unique Selection\] \\ | * Pre-Concept
* Solution Analysis
* Technology Development
* Engineering and Manufacturing development
* Production and Development
* Operations and Support | Development Status \\ | Enum \[Unique Selection\] \\ | Appendix 9 | N | The field indicates the phase of the product / process development where the need is required. The field values were extracted from the following presentation shared by Jeremy:{color:#000033}[http://www.dtic.mil/ndia/2008science/Day3/03Morgan.pdf]{color} | The field captures the stage in a product / process development where the need is required. | The field values were captured from:&nbsp;{color:#000033}\[{color}{color:#000033}*[http://www.dtic.mil/ndia/2008science/Day3/03Morgan.pdf]*{color} | \[http://www.dtic.mil/ndia/2008science/Day3/03Morgan.pdf\]\] \\
A source pointed to by Jeremy. \\
1) The field aligns with the "*How developed is your (product/service)?"* field from the NIM form for entering innovation information. | \\ |
| Related Products \\ | String (Multiple Selection) \\ | \- | N | A company can list down its own products related to one which has the need. This can help us create a information network of companies and present their product(s) as solutions to some need(s) that matches their product characteristics. This is used as a implicit feedback from the system. \\ | The field captures other related products that may have similar need. \\ | The field is not aligned with any of the fields from existing sources of reference. |
| Competing Products \\ | String (Multiple Selection) \\ | \- | N | A company can list down its the competing products to one which has the need. This can help the system fetch relevant solutions with help of some more information extracted from the competing products. \\ | The field captures products similar to the one that has the need such that they act as a direct competitors. \\ | The field aligns with the field in *NIM's* form that asks the innovator to enter a competing product. The question NIM asks is to enter the name of an alternative that could be used if the product in consideration was not present. |
| Time already spent (before solution search began) \\ | Enum \[Unique Selection\] \\ | * < 1 Month
* 1-3 Months
* 3-6 Months
* 6-12 Months
* 1-3 Years
* > 3 Years | Time already spent (before solution search began) \\ | Enum \[Unique Selection\] \\ | Appendix 10 | N | The field describes the time that the company has already spent looking for solution. \\ | The field captures the time already spent by the company finding the solution. The field will be an indicator of how much time is saved by the need-analysis framework by comparing this time with the time to find the solution by the need-analysis framework. | The field is new and does not directly align itself to any existing fields. However the value of the fields are aligned with the "*Estimated time*" field on the NIM website for entering the innovation information. |
| Time required for find solution \\ | Enum \[Unique Selection\] \\ | * < 1 Month
* 1-3 Months
* 3-6 Months
* 6-12 Months
* 1-3 Years
* > 3 Years\\ | Time required for find solution \\ | Enum \[Unique Selection\] \\ | Appendix 10 \\ | N | The field describes the time that the company would like to find the solution in. \\ | The field aims at capturing the time limit for finding the solution. | The field is new and does not directly align itself to any existing fields. However the value of the fields are aligned with the "*Estimated time*" field on the NIM website for entering the innovation information. |
| Time to implement solution \\ | Enum \[Unique Selection\] \\ | * < 1 Month
* 1-3 Months
* 3-6 Months
* 6-12 Months
* 1-3 Years
* > 3 Years\\ | Time to implement solution \\ | Enum \[Unique Selection\] \\ | Appendix 10 \\ | N | The field describes the time that the company would like to get the solution implemented. \\ | The field aims at capturing the time limit for implementation of solution once identified. | The field is new and does not directly align itself to any existing fields. However the value of the fields are aligned with the "*Estimated time*" field on the NIM website for entering the innovation information. |{table-plus}

Intuition for fields (8,9,10): For the timing related fields we are trying to separate three different time frames that relate the need with the solution required with respect to time. It aims at capturing time spend that has already been spent searching for solution (w/o our framework), time estimate in which the company wants the solution to be identified, the time estimate the company expects the solution to be implemented. The timing values can act as very good features when assigning need priorities and optimizing the supply of solution to the right need at right time so as to maximize productivity.



|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Need Classification | Enum (Multiple Selections) | Solution Categories - Solution Subcategories | N | The field capture the classification of the solution. Currently we restrict the solution space to only academia entities. | The field enables the system to do things as follows: \\



|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Application(s) \\ | Text | \- | N | The field describes the application of the product / process the need forms a part of. \\ | The field describes the application of the product / process that has the need. \\ | The field aligns with multiple fields to forms like *NIM*: \\
2) Application |
| Benefit(s)&nbsp; \\ | Text | \- | N | The field describes how the solution to the need will benefit the product / service it is being used for. | A product / service (bigger picture) might have several needs. We are capturing the importance of the need (in terms of benefits) with respect to the product / service being designed (/implemented)&nbsp; \\ | The field indicates how beneficial a solution to the need would be to the end product. The field is new and does not align itself with fields in existing form. |
| Expected Company Involvement in Solution Development \\ | Enum \[Multiple Selection\] \\ | * None
* Provide Infrastructure
* Co-Development | Expected Company Involvement in Solution Development \\ | Enum \[Multiple Selection\] \\ | Appendix 11 | N | The field describes how much the company wants to be involved when the solution is implemented. As in if they want to outsource it and want the final solution returned or they want to take part in the solution development or just provide infrastructure and let the solution provider do the work by itself. \\ | The field describes level of involvement the company wishes to have in developing the resolution for the need. \\ | The field was an outcome of a meeting with TMAC engineers. The field is a new field and does not align with fields from existing forms. |{table-plus}