"This guideline applies to products with CLEI Codes requested after the implementation date of this guideline and does not apply to products in production and with CLEI Codes previously assigned. The original implementation date of this guideline was October 1@ 2003. This guideline recommends processes and procedures for the following issues: ? Determining if a plug-in card has the downloadable software capability that complies with this guideline. ? Determining if the software is downloaded automatically and if additional manual intervention@ other than inserting the plug-in card into the slot@ is required. ? Identification of hardware and the version of software loaded: o Hardware: The existing physical product identification label (e.g.@ GTIN label or CLEI Code label for the hardware as per ATIS-0300038 and the Telcordia document@ GR-383-CORE). o Software: An electronic identifier for identifying the downloadable software version. ?? This identifier will not have a physical label. ?? ATIS-0300040@ Guideline for Data Elements included in the MIB@ defines what data the industry requires in the Management Information Base [MIB] and specifies the software identifier. ?? This guideline provides a process to determine the Software Version without adversely affecting the operating system. ? Determining where in the supply chain the appropriate software is located and how it will be downloaded onto the plug (e.g.@ on new provisioning orders or plug-ins coming out of the spare cabinets). ? For products that have CLEI Codes assigned@ the CLEI-7 for the hardware should not be changed on any plug-in card@ when the only thing that is being changed is the downloadable software@ unless the prior software caused a network outage. ? For all products@ if the supplier would like to track new hardware shipped with the most current software (i.e.@ the version of the software on the plug-in as it leaves the factory)@ the supplier can issue a Class D hardware PCN. The customer has the option of what version of software they load on this hardware. The guideline is limited to: ? Plug-in cards that have the capability to support downloadable software from either a local or remote location AND requires additional intervention by a technician (beyond the act of inserting the card in the slot) to ensure that the correct version of software is loaded on that plug-in card. ? Plug-in cards that have the capability of automatically updating its software when placed in service (""Intelligent Network Cards""). These cards have their software automatically updated by the system when they are inserted in the network element. This will result in NO additional work by the technician (i.e. ""plug and play""). Purpose This guideline provides a method to determine how plug-in cards that are capable of supporting downloadable software should be identified and how to manage plug-in cards that support a downloadable software capability. This includes processes related to provisioning@ installation@ removal and warehousing to ensure high quality network reliability and efficient operational procedures. Downloadable software includes software that can be downloaded from a remote or local location to the plug-in card at the service provider location. Note: Throughout this document the term ""plug-in card"" is used. However@ the term also applies to plug-ons@ Small Formfactor pluggables (SFPs)@ and GigaBit Interface Converters (GBICs)."