Needs Analysis Survey

Version 1 by rmittal
on Mar 12, 2012 23:24.

compared with
Version 2 by rmittal
on Mar 12, 2012 23:27.

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

Changes (17)

View Page History


h3. !NIST-MEP-WheelofStrategicAreas.png|align=left,border=1,width=300!

The Needs Analysis Survey is an online data collection tool that can be used by the engineers int the MEP network to document assessed needs of their customers in a standardized format. Standardization of the Needs Analysis will enable the MEP network to leverage the collected data and tools like the [Collaborative Partnership|http://www.collaborativepartnership.com] to connect needs with solutions. These data standards will be particularly focused on the the five MEP growth areas.

*Aim 1* will be to come up with analytic / reporting mechanism on the need-trend. We also intend to create a bridge between this system and existing resource-discovery tools like collaborative partnership to provide solution(s) in space of academia research. This is a restrictive solution space of what we ultimately desire to achieve but would provide a good starting point to explore the mapping between the needs and the respective solution.This will lead to a better understanding of an appropriate ranking function.

The tool which we are creating for collecting the need information asks the users to enter the company name as well as the need(s) information. We have a consolidated list of attributes both for company as well as the need that we capture as a part of data entry. Some of the attributes are pre-populated and the user has to select one / multiple options. Some of the attributes are free-flowing text fields where user has to manually enter the information. The attributes that we are capturing will create the feature space and help us create better (relevant) mapping between the need and the solution.

The description and insight behind various attributes is listed as follows: Attributes @ Company

Attributes @ Company
Following attributes describe the "Company"

h3. A. Attributes describing primary information about the Company
h3.


h3.


h3.


h3. *A. Attributes describing primary information about the Company*


h6.




|| 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 \\
| Parent Company \\ | String | N | The field holds the name of the parent company (if any) \\ | We aim to capture the name of the parent company. Some companies are child companies of a bigger company. In such cases its better to keep a track of the parent company. It can be helpful in many ways e.g., if there exist a solution to a need by company among one of its siblings (child company of the same parent) then that can be more preferred choice of solution. We can create a hierarchy of companies which can be really useful to analyze the statistics regarding growth / development / separation / mergers etc of existing companies as well as the trend of in which companies interact with each other (this is a stretched goal at-least with respect to phase 1). | The field came up as a discussion within the *ERA* development group. The field allows to capture the hierarchy of the companies. |{table-plus}

h3. {color:#000000}{*}B. {color:#333399}{*}B. Attributes describing location information with respect to the Company{*}{color}

{color:#000000}Intuition: The primary address of correspondence for the company is captured to align the company information based on its location. It also serves as a direct point of communication with the company in case its required. The system can also generate different location based analytics to detect / predict trends (patterns) based on all other fields of data that are being captured. This may turn out as a great utility for the MEPs to monitor the industrial growth and take any actions if and when required.{color}



|| 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) \\



|| 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 particular 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



|| Data Element || Type || Value || Required ? (Y/N) || Description || Purpose || Existing Systems, Tools and Processes Considered \\ ||
| Related Growth Areas \\ | Enum (Multiple  Selection) \\ | * Technology Acceleration



|| 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*: \\