Create Vendor or Subcontractor Registration

NREL is always looking for new vendors and subcontractors who can meet the lab's continuing requirements for goods, services, research and development, construction, and other laboratory needs.

NREL has a strong commitment to small business and especially invites participation by small, disadvantaged, women-owned, HUBZone, veteran-owned, and disabled veteran-owned businesses. Also important to the laboratory are partnerships with suppliers that result in creative collaboration.

NREL's supplier management strategy is to work with businesses that improve the laboratory's competitive position and support the laboratory's mission. Part of that mission is to maintain an effective program ensuring diversity in our operations. A comprehensive program of outreach and evaluation maintains diversity in our procurement, employment, and technical transfer efforts. NREL's diversity efforts are further supported by business development efforts through effective use of technical conferences, industry trade fairs, and minority business exchanges.

To register to become an NREL vendor or subcontractor, complete the on-line registration form below. If you've already registered and need to update your information or if you have any questions, please contact:

Rexann Dunn
Small Business Program Manager
National Renewable Energy Laboratory
15013 Denver West Parkway MS 1613
Golden, Colorado 80401-3305
Telephone: 303-275-4322

Business Information

Address

Contact Information

Business Designations
Certification Type(s)

SAM

NAICS Designation

Either type your numeric North American Industry Classification System NAICS code(s) into the appropriate box(es). If you have more than three NAICS codes, please stipulate in the "Comments" box below.

Configure the meta tags below.
To view a summary of the individual meta tags and the pattern for a specific configuration, click on its name below. Use tokens to avoid redundant meta data and search engine penalization. For example, a 'keyword' value of "example" will be shown on all content using this configuration, whereas using the [node:field_keywords] automatically inserts the "keywords" values from the current entity (node, term, etc).

Browse available tokens.
Basic tags

Simple meta tags.

The text to display in the title bar of a visitor's web browser when they view this page. This meta tag may also be used as the title of the page when a visitor bookmarks or favorites this page, or as the page title in a search engine result. It is common to append '[site:name]' to the end of this, so the site's name is automatically added. It is recommended that the title is no greater than 55 - 65 characters long, including spaces.
A brief and concise summary of the page's content, preferably 150 characters or less. Where as the description meta tag may be used by search engines to display a snippet about the page in search results, the abstract tag may be used to archive a summary about the page. This meta tag is no longer supported by major search engines.
Advanced

Meta tags that might not be needed by many sites.

Geo-spatial information in 'latitude; longitude' format, e.g. '50.167958; -97.133185'; see Wikipedia for details.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
Robots
A comma-separated list of keywords about the page. This meta tag is used as an indicator in Google News.
Highlight standout journalism on the web, especially for breaking news; used as an indicator in Google News. Warning: Don't abuse it, to be used a maximum of 7 times per calendar week!
This meta tag communicates with Google. There are currently two directives supported: 'nositelinkssearchbox' to not to show the sitelinks search box, and 'notranslate' to ask Google not to offer a translation of the page. Both options may be added, just separate them with a comma. See meta tags that Google understands for further details.
Indicate to search engines and other page scrapers whether or not links should be followed. See the W3C specifications for further details.
Sets a cookie on the visitor's browser. Can be in either NAME=VALUE format, or a more verbose format including the path and expiration date; see the link for full details on the syntax.

Meta tags used to control the mobile browser experience. Some of these meta tags have been replaced by newer mobile browsers. These meta tags usually only need to be set globally, rather than per-page.

Using the value 'width' tells certain mobile Internet Explorer browsers to display as-is, without being resized. Alternatively a numerical width may be used to indicate the desired page width the page should be rendered in: '240' is the suggested default, '176' for older browsers or '480' for newer devices with high DPI screens. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
Some older mobile browsers will expect this meta tag to be set to 'true' to indicate that the site has been designed with mobile browsers in mind. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
A URL to a manifest.json file that describes the application. The JSON-based manifest provides developers with a centralized place to put metadata associated with a web application.

Custom meta tags used by Apple's software, iOS, Safari, etc.

Custom meta tags used by the Android OS, browser, etc.

A URL to a manifest.json file that describes the application. The JSON-based manifest provides developers with a centralized place to put metadata associated with a web application.

Custom meta tags used by the Windows and Windows Mobile OSes, IE browser, etc.

A semi-colon -separated string that must contain the 'polling-uri=' value with the full URL to a Badge Schema XML file. May also contain 'frequency=' value set to either 30, 60, 360, 720 or 1440 (default) which specifies (in minutes) how often the URL should be polled.
Should contain the full URL to a Browser configuration schema file that further controls tile customizations.
A semi-colon -separated string containing 'polling-uri=' (required), 'polling-uri2=', 'polling-uri3=', 'polling-uri4=' and 'polling-uri5=' to indicate the URLs for notifications. May also contain a 'frequency=' value to specify how often (in minutes) the URLs will be polled; limited to 30, 60, 360, 720 or 1440 (default). May also contain the value 'cycle=' to control the notifications cycle.
A semi-colon -separated string defining the 'jump' list task. Should contain the 'name=' value to specify the task's name, the 'action-uri=' value to set the URL to load when the jump list is clicked, the 'icon-uri=' value to set the URL to an icon file to be displayed, and 'window-type=' set to either 'tab' (default), 'self' or 'window' to control how the link opens in the browser.
Revision information
Reset