equipment manufacturers

You need to take the following steps before you can initiate a CLEI Coding Request:

1. Common Language Master Agreement: Please fill out this form to provide us with your contact information so we can send you a copy of our Master Agreement. Once you receive the Master Agreement, please email a signed copy of the agreement.
2. Purchase the Common Language NEP Start-up Package: You can purchase the Network Element Provider Start-up Package at the Common Language Store. Once we receive your payment, we will send the package, which includes the purchase of a four-character Vendor Code per ATIS-0300220 to identify your company, the industry Generic Requirement (GR) documentations associated with CLEI coding and the Common Language Job Aids that support Equipment Coding. Please note, a copy of your company’s articles of incorporation will be needed to process the Vendor Code request and there is a $850 fee associated with the NEP Start-up Package.
3. Submit CLEI Coding Request: Once you have returned the signed Master Agreement and purchased the NEP Start-Up Package, you are ready to submit a request for CLEI coding. For more information you can request a copy of JA-485, CLEI Code Request Job Aid, which provides the process used to establish a CLEI Code.

If you have any questions, please call our Customer Support Center at +1 877-699-5577.

There are cases when an equipment manufacturer uses equipment manufactured by another company. In these cases, the items should be coded for ordering and inventory practices. If the manufacturer does not rebrand the product, the item should be CLEI Coded with the original manufacturer’s nomenclature and specifications, including the original manufacturer’s name and product code. If the product is altered in any way, the manufacturer shall rebrand the item with their own logo/product code and request for a CLEI Code.

Equipment manufacturers assign system/product names (identifiers) to an organized assembly of equipment as a common practice. The System Identifier (System ID) has become an important identifier for service providers to track, engineer and assist with provisioning during network deployment. It is critical that each component (card, plug-in, plug-on, SFP, shelf, etc.) be populated with accurate System ID information in the Common Language Equipment Repository so that service providers can aggregate the right components at a system level. The relationship between CLEI Codes and System ID is one to many, supporting a single CLEI Code in multiple System IDs.

Common Language Equipment Codes (CLEI Codes) allows recording for tracking RoHS compliancy and the level of compliance (e.g., 2, 5, or 6) within the Hazardous Material Indictor (HMI) field within the CLEI record.

Product changes that remove hazardous material to meet industry and environmental standards are considered reportable changes. RoHS-compliant changes are strictly removing hazardous substances only. They do not affect functionality or interchangeability of a product. RoHS changes that include other product changes/improvements to an existing product are deemed not interchangeable.

All CLEI Code requests are to be sent via e-mail to the Common Language Production Control Center at clpcc@iconectiv.com.

CLEI Code requests require equipment analysis for proper code development. Be sure to provide sufficient non-proprietary technical information when submitting coding requests. It is preferred that product information (product attributes) be provided along with the CLEI Code request form to assist in the coding process.

A CLEI Code request form is available and is supported by a Job Aid (JA-485). Providing a complete set of attributes will prevent unnecessary delays with the equipment analysis and code development process. It is highly recommended that manufacturers request equipment codes at the beginning of their manufacturing cycle so that the CLEI Codes and CPR codes can be created and be available before products are ready to be labeled and shipped.

Product attributes are product features/characteristics that define an equipment item and are included within the CLEI Code record.

As per GR 485-CORE, iconectiv must collect all applicable attribute data for equipment that supports a CLEI Code. It is preferred that attributes are recorded during the CLEI Code request process. Attributes assist service providers with internal business processes such as purchasing, planning, ordering, maintenance, provisioning and repair.

For service providers that do business with Incumbent Local Exchange Carriers (ILECs) there are requirements for the provider companies to include basic information such as vendor name and equipment description to convey to the ILEC. A common example of this practice is communication companies that colocate within the ILEC Central Office or Data Center locations. The service provider engineer also has to provide heat dissipation, floor loadings, NEBS (Network Equipment-Building System) info and DC Power specifications associated with each piece of equipment to be placed in the leased space.

A MIB (Management Information Base) is a small database stored on devices. The MIB is comprised of data objects, including the CLEI Code, which can be used to identify and manage on-net components within the service provider’s network.