COMMON LANGUAGE® Equipment Identification:
Network Element Providers (NEP) FAQs: CLEI™ Codes/CPRs
This page provides concise answers to key questions asked by equipment vendors regarding the COMMON LANGUAGE Equipment Identification product line. To contact us, please fill out our simple information request form or contact the Common Language Production Control Center at 732-699-5470.
Q: What does CLEI Stand for?
A: COMMON LANGUAGE Equipment Identification.
Q: What do CLEI Codes do?
A: CLEI codes are the cornerstone of COMMON LANGUAGE Equipment Identification. Network service providers use CLEI codes for inventory, engineering, spare piece-part ordering, provisioning and maintenance operations.
Most equipment suppliers request codes for switching, transport, loop, power, portable tools, test, video, LAN, and WAN equipment.
CLEI codes precisely identify the specific form, fit and function of equipment items used in circuit-switched, packet-switched, xDSL, IP and emerging wireline and wireless technologies.
To Top of FAQsQ: What is a CPR code?
A: CPR (Continuing Property Record) codes enable service providers to process engineered orders, record assets and track plant investments. Detailed asset records created with CPR codes play an invaluable role in the audit function.
The catalog information for CPR codes, along with ECN and FRC classification data, is known as the property record catalog (PRC). The PRC is a critical part of service providers' network-procurement and billing-verification functions. Without CPR codes, service providers cannot pay their bills.
To Top of FAQsQ: Why do I need CLEI and CPR codes?
A: As an equipment vendor, you will find that many of your potential customers already use COMMON LANGUAGE Equipment Identification, CLEI codes and CPR codes to help them track their assets, manage inventory and provision services.
These prospective clients have discovered that vendor-neutral equipment nomenclature and associated methods and procedures are absolutely essential to helping service providers achieve the process flow-through they need to compete effectively.
To Top of FAQsQ: How much do CLEI and CPR codes cost?
A: Prices of equipment codes vary by equipment type. Feel free to ask for an estimate when you submit your equipment code request. Our experience suggests that you will benefit from economies of scale and that equipment codes will add relatively little to the total production cost in your manufacturing process.
Q: How do I order CLEI and CPR codes?
A: Ordering CLEI codes and CPR codes is simple. Once your company's CLEI Code Coordinator has submitted an equipment code request and supporting manufacturer's documentation via e-mail, mail or fax, our engineers will use this product information to develop a CPR code and develop a globally unique 10-character CLEI code for your equipment.
Q: How long does it take to get CLEI and CPR codes?
A: Coding requests related to equipment analysis and code development of new or updated CLEI codes and CPR codes are handled on a first come, first served basis. Presently, equipment coding services have maintained a turnaround time of 99.5% requests completed within 30 days. Please contact us in advance if you have a special need for a quicker turnaround.
Be sure to provide sufficient technical information when submitting coding requests. This will prevent unnecessary delays in the equipment-analysis and code-development process.
We highly recommend that you contact us at the beginning of your manufacturing cycle so that the CLEI codes and CPR codes you need can be created before your products are ready to be labeled.
To Top of FAQsQ: When will I need more CLEI codes and CPR codes?
A: Any time you change form, fit or function, we will have to analyze the modified equipment item. Not only does this help ensure the accuracy of your customers' inventory, maintenance and ordering processes, but it will also make it easier for them to locate products that must be recalled, updated or retrofitted. CLEI codes can also help you manage your Product Change Notice (PCN) process. CPR codes help manage compatible units.
Q: What are assignment codes and hardwired ECI codes?
A: Assignment codes and hardwired ECI codes describe the operating characteristics of equipment and the associated logical and virtual capabilities. They help service providers identify a provisionable slot, describe the capability it will handle, and capture the ports each slot can handle.
Q: Do I need assignment codes and hardwired ECI codes?
A: A customer may ask you to go through the OSMINE Services Integration Process. If the equipment can be provisioned for facilities or circuits, it will require TIRKS function codes. These, in turn, need assignment codes and hardwired ECI codes. By getting these codes in advance, you can accelerate this critical process by a minimum of 30 days and simplify the provisioning and service-activation processes for your customers.
Q: Do I need HECI codes?
A: Human Equipment Catalog Item (HECI) and Human Equipment Catalog Item Group (HECIG) are generic terms used in many operations support systems to identify ten-character and eight-character assignment codes, respectively. So if you see the terms HECI or HECIG, think CLEI code.
Q: Do I need bar code labels?
A: Bar code labels containing CLEI codes are usually affixed to field-serviceable equipment during the manufacturing process before they are sent to your customers. All service providers using CLEI codes require a label affixed to the product per GR-383-CORE and GR-485-CORE.
In order to help you find a supplier for CLEI code bar code labels, we have published a list of Bar Code Label Suppliers.
We also offer a full menu of Bar Code Lab Services, including verification and environment testing of the labels to meet GR-383-CORE requirements.
To Top of FAQsQ: What is an attribute?
A: Sometimes referred to as product features/characteristics, there are two types of attributes:
Enhanced Attributes:
Physical Attributes - Height, Width, Depth and Weight
- If Frame; hole spacing (vertical distance between each hole)
Electrical Attributes - Input Voltage, Input Wattage, etc.
Environmental Attributes - Operating Temp., Storage Temp., Humidity, Altitude, Heat Dissipation
General Information Attributes - Alarm Capability
Engineering Attributes:
Hardwired equipment (e.g., Shelf/Mounting *, etc.) attributes include the following:
- Shelf/Mounting description
- Number of Slots (total number of slots)
- Slot layout includes; each slot name and predominant use of identified slot
- Slot orientation includes; distance from left, distance from bottom and distance from front
Plug-in/Card/Module information includes the following:
- Plug-in description (e.g., Ethernet Mapper Card, Alarm Module, etc.)
- Type of Plug-in (e.g., Module, Motherboard/Parent Card, Daughter-card, SFF-Device (SFP, GBIC, etc.))
- Downloadable Software (DLSW) (Y/N)
- If DLSW is supported, does the plug-in card require additional intervention by a technician when it has been inserted in a slot, for maintenance or provisioning purposes, to ensure that the correct version of software is loaded on the plug-in card?
- Number of Ports
- Number of Sub-cards (typically furnished for support of SFF type devices)
- Port Details includes**
- Port Name
- Port type (e.g., Ethernet, SONET/SDH, FICON, etc)
- Reach Factor
- Bandwidth/Bit Rate
- Wavelength/frequency (when port is optical)
- Frequency (for wireless transmission)
- Connector Type
- Number of Connectors
* Shelves/Mountings/Sealed Assembled Units, which support specific network functions such as an OC-48/STM-16, OC-3/STM1, OC-192/STM-64, 100Base-T, etc. may require CLEI assignment codes in order for the shelf/mounting or sealed assembled unit to be provisioned within a carrier’s network. CLEI assignment codes are additional codes in support of a given hardwired entity for service providers that use TIRKS®.
** Port details are required to be broken down to the physical aspect, not logical. Therefore each port must be identified as is and not grouped in a logical aspect. As an example; DS3 are typically paired ports and are always understood as transmit/receive, however DS3 physical connectivity includes two separate ports; one transmit, one receive. Therefore we would break out a DS3 as follows:
- Port Name: DS3 Transmit
- Port type: DS3
- Bit Rate: 44.736Mb/s
- Connector Type: BNC
- Number of Connectors: 1
- Port Name: DS3 Receive
- Port type: DS3
- Bit Rate: 44.736Mb/s
- Connector Type: BNC
- Number of Connectors: 1
Downloadable Software:
In support of an ATIS (Alliance for Telecommunications Industry Solutions) proposal the CLEI Code was selected as the preferred means of identifying a network element that can support
downloadable software. The following is what is required to provide proper information
for industry use:
- Identify if the plug-in card has the ability to have software downloaded from either a local or remote location (Yes/No). GR-485-CORE R4-5 requirement.
- Downloadable Software Technician Assistance If requirement R4-5 is yes, then does the plug-in card require additional intervention by a technician when it is inserted or in the process of being inserted in a slot, for maintenance or provisioning purposes, to ensure that the correct version of software is loaded on the plug-in card? (Yes/No), GR-485-CORE R4-6 requirement.
For more details about attributes, please refer to GR-485-CORE.
To Top of FAQsQ: Why do I need to provide attributes data for my equipment?
A: Due to our mutual customer’s requirements, Telcordia, the CLEI Code maintenance agent, must collect all applicable attribute data for every piece of equipment submitted for CLEI coding. These attributes are needed to help our mutual customers with Purchasing, Planning, Ordering, Maintenance, Provisioning and Repair.
Q: What will happen if the CLEI request form is incomplete? (What if some enhanced attribute data missing?)
A: If the form is not complete, or the request submittal lacks required attributes (see GR-485-CORE),
a Telcordia Equipment Coding Engineer will contact the requestor by email to obtain the missing data.
All acronyms/abbreviations that are used in the request should be explained/spelled out.
Incomplete requests will lead to delays with turn-around service.
If enhanced attributes are missing and are not subsequently provided, the CLEI Code request will continue to be processed and completed CLEI Code products will be returned via email. Records which do not have a full accompaniment of attributes are collected and will be sent back to the requestor in a monthly report titled ‘Missing Attribute Report’ (see CSB NEP-08-11-2008.1).
Missing Engineering Attributes have a direct impact on the CLEI Code and will cause delays with the request and/or lead to withdrawal of an item due to lack of documentation.
To Top of FAQsQ: How can I update the enhanced attribute data?
A: There are 3 ways to update the Attribute data.
- Send updates directly to the engineer that is working on your CLEI Code request.
- If the request has been completed and you received a "missing attributes" form, populate the form with the required data and send back to the designated email address.
- To correct and update records for your company, request a Login to enter enhanced attribute data. Training is required before a login is issued. Requests for logins can be sent to the Production Control Manager at clpcc@telcordia.com. Log-ins are issued on an as need basis.
Q: What are System Identifiers (IDs)? How are they used?
A: Vendors assign system 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 for actual 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 Telcordia catalog so
that service providers can aggregate right components at a system level.
Examples for system IDs may be as simple as a stand-alone unit (e.g., Access30), or as complex as a digital switch (e.g., 5ESS, DMS-100, etc.) which consists of many various components. Also, some vendors identify their product lines by a product family (and/or series), and multiple model numbers (or sub-systems). In this case, the System ID field in the catalog is populated with system identifiers at the lowest level, that are the model numbers (e.g. 7603, 7604, 7606, 7609, etc.) and NOT the product family (e.g. 7600 Series).
It is the vendor’s responsibility to provide detailed system identifiers as well as keeping this information current within the CLEI Code record in the Telcordia equipment catalog. If a product that has already been CLEI coded is used on a new system identifier, the vendor must notify Telcordia clpcc@telcordia.com to update the existing CLEI Code(s) to include this new system identifier. The system identifier updates must take place before the products are sold under the new system. Keeping this information current is also true if a System Identifier is changed to another System Identifier (e.g., re-branding) or a System Identifier becomes obsolete (or discontinued).
To Top of FAQsQ: How is RoHS compliancy reflected within the CLEI Code Set?
A: COMMON LANGUAGE Equipment Codes (CLEI Codes) will allow for recording and tracking RoHS compliancy
and the level of compliance within the Hazardous Material Indictor (HMI) field. The data will be displayed to the
end user as found appropriate for each record, manufacturer’s product that supports RoHS as either RoHS-5 or RoHS-6.
Q: How do I treat a change in RoHS compliancy?
A: Suppliers have made changes to their products to remove Hazardous material to meet the new European
Community mandate. This enhancement is also called Restriction of Hazardous Substances (RoHS).
RoHS compliant changes are incorporating “design improvements that do not affect the existing
functionality or interchangeability of a product”. RoHS compliant changes are NOT incorporating
“improvements in the design of existing products that result in better operation, improved testing
and maintenance, longer life, service improvements, cost reductions to a customer, and/or addition
of new features”. For these reasons, Telcordia and the GR-209-CORE committee consider this a Class D change.
Q: What are the guidelines for creating CLEI codes for OEM equipment?
A: There are two scenarios that are identifed with OEM equipment as follows:
- If you are not stenciling anything on the equipment, you can use the OEM’s CLEI Code and label that is on the equipment. If there is no CLEI Code label found on the equipment, please contact Common Language for assistance.
-
If you are re-stenciling the equipment with your company’s name or logo
(thus removing the OEM’s name or logo and Product Code), a new CLEI Code
must be assigned (See NOTE).
If there is no CLEI Code assigned to the OEM equipment, your company can
request a CLEI Code. In this case, your company has two options:
- You can request for the OEM item to be coded to the OEM's brand.
- Or you can re-stencil and request a CLEI Code with your branding.
NOTE: If this equipment has a MIB, or MIB type device,
you must ensure that the CLEI Code in the MIB, or MIB
type device, matches the CLEI Code that is on the label.The Invoice, which you send to your customers, should list and match the CLEI Codes of the equipment that is being delivered. If you are using the OEM CLEI Codes, it is recommended that your invoice also state the OEM name along with the CLEI Code and CPR being delivered.
To Top of FAQs