Patent Description:
The following relates to a system, method, and non-transitory computer readable medium including instructions for management of equipment and components found in a telecommunications or data center infrastructure.

Datacenters and telecommunication rooms are filled with computing, storage, and networking systems that include physical infrastructure such as server cabinets, telecom racks, patch panels, fiber cassettes and cable managers. Many datacenter managers and telecom operators create digital models of their rooms using DCIM (Data Center Infrastructure Management) solutions (e.g., software applications) to document the components in their rooms to assist in remote management and troubleshooting of issues that may arise. Creating digital representations of physical equipment may require large amounts of data that must be manually entered. This time-consuming process can easily introduce errors and any updates to the physical location requires subsequent manual data entry to update physical changes to the digital copy, which is a significant drain of enterprise resources.

Considering the amount of equipment and cabling that can occupy a datacenter, the amount of manual data entry required to effectively operate a DCIM solution can easily become very time-consuming and overwhelming often resulting in errors or documentation that is out of date. A need therefore exists for a system, method, and application program for improved infrastructure management of telecommunication or data center infrastructure that is more efficient and less consuming of valuable enterprise resources.

<CIT> describes, according to its abstract, a cable management system including multiple cables, each having a unique identifier associated therewith and each including first and second barcodes including the unique identifier, the first barcode located proximate a first end of the cable, the second barcode located proximate a second end of the cable. The system also includes a barcode scanner to scan barcodes of the cables, the barcode scanner including a clip to receive one of the cables. The system also includes a mobile computing device having a processor, data storage medium, communication unit, and user interface including a display. The mobile computing device is configured to receive via the user interface first end location information for a first cable, receive from the barcode scanner the first barcode of the first cable, and save and display the first end location information in association with the unique identifier of the first cable included in the first barcode.

The invention to which the present European patent relates is defined in the appended claims.

According to one non-limiting exemplary embodiment of the present disclosure, a system is provided for management of telecommunication or data center infrastructure including a plurality of components. The system may comprise a scanner which may be configured to scan a unique identifier attached to a component of the infrastructure, and a mobile computing device which may comprise a processor, a data storage medium storing machine readable instructions, a communication unit, and a user interface including a display. The mobile computing device may be configured to execute the machine readable instructions to (i) receive, from the scanner, a component identifier associated with the component obtained via a scan of the unique identifier attached to the component, (ii) associate the component identifier with a location of the component in the infrastructure, (iii) display, on the user interface, the component identifier associated with the location of the component, and (iv) export, via the communication unit, the location of the component to a management solution for use in management of the component in the plurality of components of the infrastructure.

A detailed description of this and other non-limiting exemplary embodiments of a system, method, and non-transitory computer readable storage medium for management of telecommunication or data center infrastructure is set forth below together with the accompanying drawings.

Detailed non-limiting embodiments are disclosed herein. However, it is to be understood that the disclosed embodiments are merely exemplary and may take various and alternative forms. The figures are not necessarily to scale, and features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art.

Datacenter Infrastructure Management (DCIM) solutions are a collection of tools designed to provide proactive failure avoidance, planning capabilities, and cost savings to operators of data centers that include equipment such as fiber cable management equipment, copper cable management equipment, audio/visual equipment, or the like (hereinafter generally referred to as "data centers"). Features provided by a DCIM solution may include monitoring critical infrastructure of a data center such as power and cooling systems for analysis and cost reduction, documenting and managing physical infrastructure such as equipment inventory within a data center, or data and power connectivity to diagnose problems that may arise in a data center, work order creation and processing for physical equipment moves, adds, and changes. The DCIM solution described herein includes software, hardware, and/or circuitry for implementing the features of the DCIM solution described herein.

DCIM solutions documents physical infrastructure systems by creating a digital version or "digital twin" of the physical environment in software to re-create the actual physical environment. This digital version may be created according to downloaded and manually entered data that allows for remote viewing, planning, and analysis to be performed without physically being on-site the physical data center. So while DCIM solutions may rely heavily on data inputs to gather information, unfortunately most physical infrastructure installations require that data be entered manually. In that regard, <FIG> shows a flowchart <NUM> describing an exemplary method of documenting equipment and cable infrastructure locations and inputting product information. As seen therein, such a method includes manually identifying <NUM> cable locations, manually documenting <NUM> cable location information in the field, looking up <NUM> cabling product information at a manufacturer website, manually entering <NUM> cable location information into a DCIM solution, and manually entering <NUM> cable product information into the DCIM solution.

Examples of data that may be entered manually into a DCIM solution might be: equipment location in a datacenter rack (e.g., rack unit (RU) location or other location in a rack or cabinet of equipment such as a vertical power distribution unit (PDU) mounted in a cabinet's rear left compartment), type of equipment (e.g., server, network switch, PDU, uninterruptable power supply (UPS)), equipment specific information for each type of equipment (e.g., PDU information might contain the following: number of outlets, outlet type, power rating, plug type), cable end locations for network cables, cable end locations for power cables, cable product information, cable length information, cable connector type information, or other equipment found in the data center.

Considering the amount of equipment and cabling that may occupy a datacenter, the amount of manual data entry required to effectively operate a DCIM solution can easily become very time-consuming and overwhelming, which may result in manual data input errors or reliance on outdated documentation. Thus, as also previously described, a need exists for a system, method, and application program for improved infrastructure management of a datacenter.

It follows that the present disclosure describes a DCIM solution for providing more efficient and resource saving solutions for the management of equipment and components found in a data center. In addition, a cable management solution is disclosed for obtaining data on cable attributes within a data center, where the cabling data is then provided as inputs to the DCIM solution for the DCIM solution to implement the DCIM features disclosed herein. The DCIM solution described herein may include the hardware, software, and/or circuitry for implementing the features attributed to it as described herein.

With reference to <FIG>, a more detailed description of non-limiting exemplary embodiments of a system, method, and non-transitory computer readable storage medium for including instructions for the management of a data center infrastructure according to the DCIM solution will be provided. For ease of illustration and to facilitate understanding, like reference numerals may be used herein for like components and features throughout the drawings.

The present DCIM solution reduces the amount of time spent documenting physical infrastructure and provides product information without manual data entry. In that regard, unique identifiers are placed onto data center equipment, and intelligent software is utilized to provide physical infrastructure documentation without the inconvenience and/or problems associated with manually entering product information. Once a network cabinet or telecom rack has been scanned, the DCIM solution can then reference other saved information to validate equipment or audit installations.

The disclosed equipment management solution includes software, hardware, and/or circuitry for implementing the features for identifying and documenting cables, network cabinets, telecommunication racks, and other data center equipment according to the present disclosure, as well as any other features described herein. As shown in <FIG>, the equipment management solution may be used in a system <NUM> that includes infrastructure equipment <NUM> having a unique identifier <NUM> (e.g., barcode or QR code) attached. For example, the infrastructure equipment <NUM> may include, but not be limited to: cabinets <NUM>, telecom racks, fiber trays, fiber cassettes, copper and fiber patch panels, plug packs, cable managers, power distribution units, or any other equipment found in a data center. The system <NUM> also includes a personal computer or mobile computing device <NUM> having a user interface including a display and executing application software according to the present disclosure. For example, the equipment management solution may include and/or be an extension of the cable management solution for obtaining cable related information described in <CIT> (now <CIT>).

The system <NUM> also includes a common barcode scanner <NUM> configured to communicate via Bluetooth, universal serial bus (USB), serial connection, Wi-Fi, radio-frequency (RF), or other known data communication protocol, to the mobile computing device <NUM> running the application software of the present disclosure. An exemplary use for the barcode scanner <NUM> is provided with reference to <FIG>.

The system <NUM> utilizes an internet connection <NUM> to communicate with an equipment portal (e.g., equipment manufacturer internet portal) to download product information via an appropriate application programming interface (API), which may be a Representational State Transfer (REST) or any other suitable API. The product information may be stored on a database <NUM> operated or in control by the equipment portal. In addition or alternatively, the product information may be stored on a memory storage included on the mobile computing device <NUM>.

According to some embodiments, the system <NUM> may further include a mobile printer <NUM> for printing unique identifier labels, as shown in <FIG> and <FIG>. The mobile printer <NUM> enables a user to print labels with the unique identifier <NUM> while working in the field during an installation or maintenance work job.

<FIG> shows a flowchart <NUM> including steps for implementing an exemplary process for documenting a cabinet, telecommunication rack, or other equipment by the equipment management solution, according to some embodiments. The process described by the flowchart <NUM> may be referred to as a "Scan Mode", and include the following processes implemented by a processor executing instructions stored on a non-transitory memory included on a computing device (e.g., mobile computing device <NUM> as shown, for example, in <FIG>):.

Process <NUM> (<NUM>): Start or begin with an existing server cabinet or telecommunication rack that incorporates physical infrastructure parts with unique identifiers. In that regard, <FIG> illustrates exemplary telecommunication or data center infrastructure having a unique identifier <NUM> (e.g., barcode printed onto a label) according to one non-limiting exemplary embodiment of the present disclosure. As seen therein, a cabinet <NUM> may include infrastructure equipment <NUM>, any or all of which may have a unique identifier <NUM> thereon or attached thereto via a label.

Process <NUM> (<NUM>): A user initiates execution of the application software for the equipment management solution on the mobile computing device <NUM>. For example, <FIG> depicts the mobile computing device <NUM> that may be executing the exemplary application software for the equipment management solution of the present disclosure.

Process <NUM> (<NUM>): The user enters a cabinet/rack name into a graphical user interface (GUI) field, where the name may be used as a file name for a saved file. In that regard, <FIG> illustrates an exemplary user entry of a cabinet/rack name into a field <NUM> of the GUI displayed by the equipment management solution of the present disclosure.

Process <NUM> (<NUM>): The user enters the rack unit number into the "Location" field provided by the GUI of the equipment management solution. In that regard, <FIG> illustrates an exemplary user entry of location/rack unit information into a location field <NUM> of the GUI displayed by the equipment management solution of the present disclosure.

Process <NUM> (<NUM>): The user scans the unique identification (ID) for each rack unit using the barcode scanner <NUM>. In that regard, <FIG> illustrates the barcode scanner <NUM> being utilized by an exemplary user to scan <NUM> a barcode type of unique identifier <NUM> attached to a patch panel equipment. It is noted than any type of barcode scanner or any type of scannable code or other unique identifier may be employed.

Process <NUM> (<NUM>): While the user is scanning unique ID barcodes, the application software of the equipment management solution stores the cable identifier in a database along with cabinet/rack information and the location in the rack via rack unit number. The database may, for example, be stored on a memory storage unit included in the mobile computing device <NUM>, or alternatively, the database may be stored on a remote data storage device that is separate from the mobile computing device <NUM>. After storing the unique identifier <NUM> with the rack unit location information, the application software will then increment to the next rack unit number. If the incremented rack unit number is not correct, the user may enter the next rack unit number to scan. This process may be continued for more equipment until all devices in the cabinet/rack/location are scanned (<NUM>).

Process <NUM> (<NUM>): After devices, equipment, or components have been scanned and entered into the application software of the present disclosure, product information may be downloaded from an API Gateway to be associated with scanned information. This product information may include but is not limited to: Part Number, Module Type, Number of Slots, Panel Style, Height, Number of Outlets, Length, etc. (See, e.g., <FIG>. ) So, by employing an internet connection, the application software of the equipment management solution may enable and control the download and storing of specific product information via the API Gateway that communicates with an offsite portal (e.g., equipment manufacturer portal) that stores the product information (<NUM>). The application software of the present disclosure displays user-selected product information for each unique identifier and its associated location in its results, as shown in <FIG>. In that regard, <FIG> illustrates product information (e.g., product part number) being input into product input fields <NUM> of the GUI displayed by the equipment management solution of the present disclosure. These location results along with product specific information can be saved or exported to an excel spreadsheet or a comma separated values file for import into DCIM systems or other management systems (<NUM>). (See, e.g., <FIG>.

Process <NUM> (<NUM>): The application software of the present disclosure may be utilized to determine when to print custom barcode labels. When the custom barcode labels are printed (<NUM>), a mobile printer <NUM> may be used for applying the custom printed labels to devices that are not supplied with pre-applied barcodes such as other equipment, servers, network switches, or the like type of equipment within a data center covered by the equipment management solution. In that regard, <FIG> depicts the mobile printer <NUM> according to one non-limiting exemplary embodiment of the present disclosure. <FIG> shows an exemplary block diagram of the mobile computing device <NUM> running the application software of the equipment management solution to print an exemplary custom unique identifier <NUM> onto a label via the mobile printer <NUM> according to one non-limiting exemplary embodiment of the present disclosure.

Process <NUM> (<NUM>): When all equipment in the rack has been scanned and API information has been downloaded, the application software of the present disclosure can export and/or save information via comma separated value text file (. csv file) <NUM> or other format to a network management system (NMS) <NUM> or a DCIM system <NUM>, as shown in <FIG>. In that regard, <FIG> depicts the mobile computing device <NUM> running the application software for the equipment management solution to export <NUM> results data to an exemplary csv file <NUM>, a NMS <NUM>, and/or a DCIM system <NUM> according to one non-limiting exemplary embodiment of the present disclosure. For example, the results data may be sent, received, or otherwise utilized by the DCIM system <NUM> to implement the DCIM features described herein.

<FIG> shows a flowchart <NUM> including steps for implementing an exemplary process for validating/verifying an existing installation by the equipment management solution, according to some embodiments. The process described by the flowchart <NUM> may be referred to as a "Verify Mode", and include the following processes implemented by a processor executing instructions stored on a non-transitory memory included on a computing device (e.g., mobile computing device <NUM> as shown, for example, in <FIG>):.

Process <NUM> (<NUM>): After beginning with an existing server cabinet or telecommunication rack that incorporates physical infrastructure parts with unique identifiers, a user opens a previously saved file with existing location information and unique identifiers (<NUM>).

Process <NUM> (<NUM>): The user enters the rack unit location of the device to be verified. In that regard, <FIG> shows a user entering rack unit locations into the location field <NUM> in the GUI displayed by the software application of the equipment management solution.

Process <NUM> (<NUM>): The user scans the unique identifier printed on a label on a device in a selected rack unit. The software application is then configured to compare the current identifier value against the database of the previously scanned results to give a PASS/FAIL notification (<NUM>). If the device information in the current location matches the device information in the database, a PASS status is reported. If the current device information does not match the database record, a FAIL status is reported. Such a FAIL status also reports the last recorded identifier for that location. In that regard, <FIG> illustrates exemplary application software output of results displayed in a GUI of a "verify" mode operation according to one non-limiting exemplary embodiment of the present disclosure, showing a visual indication for PASS status (e.g., rows <NUM>, <NUM>-<NUM>) and a different visual indication for a FAIL status (e.g., row <NUM>).

This process may be continued until all devices in the cabinet/rack are scanned (<NUM>). A user may also determine or decide whether to overwrite the previously saved file with any new results from the verification scan (<NUM>), or alternatively discard any such new results (<NUM>). In the event of an overwrite, the new results along with product specific information can be saved or exported to an excel spreadsheet or a comma separated values file for import into DCIM or other management systems (<NUM>).

<FIG> shows a flowchart <NUM> illustrating an exemplary method of documenting equipment and cable infrastructure locations and inputting product information according to a non-limiting exemplary embodiment of the equipment management solution. <FIG> shows a flowchart <NUM> illustrating another exemplary method of documenting equipment and cable infrastructure locations and inputting product information according to a non-limiting exemplary embodiment of the equipment management solution.

As described by flowchart <NUM> and/or flowchart <NUM>, the software application of the equipment management solution running on the mobile computing device <NUM> may be used in conjunction with unique barcode identifiers attached to physical infrastructure products to identify and record location information (<NUM>, <NUM>). By utilizing these features in the software application, this reduces, or even eliminates, manual data entry into a DCIM system and the software application can further be utilized to look up product specific information from a product manufacturer's public facing API gateway (which may include and/or may also be referred to as a remote database).

API product information from a product manufacturer's API gateway may be downloaded by the application software of the equipment management solution (<NUM>) and exported to the DCIM solution (<NUM>), or exported to the DCIM solution first (<NUM>) and then the DCIM solution will handle downloading the product information from the product manufacturer's API gateway (<NUM>). Both methods described by flowchart <NUM> and flowchart <NUM> may be utilized and/or be interchangeable as they both provide the same result of the DCIM solution having API product information for physical infrastructure products without the need to manually enter the same data. In that regard, it is noted that the mobile computing device <NUM> may include a communication unit (e.g., network interface <NUM>) for transmitting and/or receiving wireless or wired signals for communicating over any suitable communication system or systems with a scanner, API, DCIM, or any other unit, controller, device, component, mechanism, module, system, subsystem, gateway, application, software, solution or the like, which communication system or systems may include Bluetooth, Wi-Fi, RF, cellular, internet, telecommunication, and/or any other wireless or wired communication system or systems.

Once equipment and connection data for a physical location has been collected by the application software of the equipment management solution running on the mobile computing device <NUM>, results data can be exported to the DCIM solution running on the DCIM system for analysis, inventory reporting, and documentation. These application results may include but are not limited to: equipment location, equipment type, equipment specific manufacturing information (e.g., for PDU: number of outlets, outlet type, power rating, plug type, certifications, image of product), cable end locations for network cables, cable end locations for power cables, cable specific manufacturing information (e.g., for network cable: cable type, cable length, connector type, cable color, cable rating, images of product, etc.).

<FIG> shows a flowchart <NUM> describing an exemplary process to dynamically create rack elevation diagrams according to one non-limiting exemplary embodiment of the present disclosure. As described by the flowchart <NUM>, the equipment management solution imports (e.g., downloads) the above-noted results data including the product information (<NUM>), and then exports this results data to the DCIM solution (<NUM>).

Once the results data is received, the DCIM solution is enabled with the information to dynamically build or create rack elevation and connectivity diagrams with detailed product information (<NUM>). This provides a more efficient DCIM solution that does not require the DCIM user to look up and manually enter the same data for creating these diagrams. In this way, the equipment management solution described herein eliminates the need for manual data entry and provides a method to automatically create rack elevation diagrams with detailed product information for documenting data center physical infrastructure installations.

In yet another non-limiting exemplary embodiment of the present disclosure, the DCIM solution can combine individual cable location result files together from the equipment management solution to dynamically create end-to-end network channel and power chain documentation. In that regard, a DCIM solution can correlate product information about individual components downloaded from an API gateway to provide information about end-to-end network channels and power chains such as overall channel length and performance.

<FIG> shows a flowchart <NUM> describing an exemplary process to dynamically create an end-to-end network channel and power chain with product information according to one non-limiting exemplary embodiment of the present disclosure. As seen therein, the equipment management solution identifies and documents network and power connectivity locations and cable information (<NUM>), as well as then exports such cable location information to the DCIM solution (<NUM>).

Upon receiving this information from the equipment management solution, the DCIM solution maps network connections and can join individual connection links to create full network channel or power chain mappings of all connections that make and end-to-end network channel (<NUM>).

Using API product information downloaded from the manufacturer (<NUM>), the DCIM solution may use cable specific information (e.g., lengths or performance of individual cables comprising a channel) to provide lengths or performance of the entire cable channel as a whole (<NUM>). Currently DCIM systems require this connectivity location data and product information to be manually entered. In that regard, <FIG> illustrates an exemplary network channel <NUM> comprised of individual infrastructure components for use with non-limiting exemplary embodiments of the present disclosure, and <FIG> illustrates an exemplary electrical power chain <NUM> comprised individual infrastructure components for use with non-limiting exemplary embodiments of the present disclosure.

In a further non-limiting exemplary embodiment of the present disclosure, a DCIM solution is configured to correlate cable connectivity information and component wiring method information provided by the application software of the cable management solution disclosed herein with product information downloaded from a manufacturer's API gateway to automatically generate cabling diagrams with fiber and channel mapping in advanced network cabling scenarios that consist of one-to-many components. <FIG> shows a flowchart <NUM> describing an exemplary process to dynamically create end-to-end network channels with fiber mapping and wiring method information according to one non-limiting exemplary embodiment of the present disclosure.

In that regard, advanced network cabling scenarios may utilize one-to-many physical cabling solutions which require additional information about the product and the wiring method to provide accurate fiber or channel mapping in a solution. Some examples where one-to-many connectivity products require connection mapping information about a device may include but are not limited to:.

In these advanced cabling scenarios, a DCIM solution must know the wiring method to properly map fibers or channels as they traverse one-to-many network devices. In that regard, <FIG> shows a table illustrating wiring methods <NUM> for a fiber cassette for use with non-limiting exemplary embodiments of the present disclosure, and <FIG> shows an exemplary method <NUM> for wiring a connector to a fiber cassette for use in non-limiting exemplary embodiments of the present disclosure.

According to the present disclosure, the application software of the equipment management solution can scan a unique identifier on a one-to-many type wiring component to document its physical location and can use the unique identifier with a public facing API to download product knowledge of its wiring method. The wiring method information of a component can be combined with a component's associated connections to automatically create end-to-end network channel connectivity maps with fiber mapping and wiring method information. In that regard, <FIG> illustrates dynamically created fiber mapping <NUM> using results of an exemplary software application according to one non-limiting exemplary embodiment of the present disclosure.

As described by the flowchart <NUM> shown in <FIG>, the application software of the equipment management solution identifies and documents cable location information (<NUM>) as well as rack unit location information for fiber cassettes (<NUM>), and exports such location information to the DCIM solution (<NUM>). Using product information for cables and fiber cassettes downloaded via manufacturers API gateways (<NUM>), the DCIM solution combines component information with fiber mapping and wiring methods information to dynamically create an end-to-end network channel (<NUM>).

In another non-limiting exemplary embodiment of the present disclosure, the DCIM solution is configured to calculate a cable routing product's usage percentage or capacity for new cables based on cable assignment information inputted by user, cable and rack location information imported from the application software of the equipment management solution disclosed herein, and product information downloaded from a manufacturers' API. <FIG> shows a flowchart <NUM> illustrating an exemplary process to dynamically calculate cable capacity according to one non-limiting exemplary embodiment of the present disclosure.

In that regard, the application software of the equipment management solution may record location information about cable pathways products such as a cable manager or fiber runner and may download product information to determine a product's capacity for holding cables. <FIG> illustrates a perspective view of an exemplary cable manager <NUM> for use with non-limiting exemplary embodiments of the present disclosure.

As described by the flowchart <NUM> shown in <FIG>, after the application software of the equipment management solution documents rack unit equipment including cable managers <NUM> and cable pathway devices and cabling (<NUM>), and further exports the cable and equipment information with API product information to the DCIM solution (<NUM>).

Following this, a DCIM user may assign individual cables to a cable pathway product in a rack elevation such as a cable manager <NUM> or a fiber runner within the DCIM solution (<NUM>). The DCIM solution may download product information such as cable manager information and cable diameter information from an API for a cable manager's assigned cables to calculate total cable volumes (<NUM>). The DCIM solution is configured to compare these cable volumes to the cable holding capacity of a cable manager <NUM> to dynamically provide a fill percentage of the cable manager <NUM> or its available capacity for new cables (<NUM>). The present DCIM solution thus could replace the need for manual spreadsheet capacity calculators which are difficult to operate and provides a method to document cable capacity without manual data entry. In that regard, <FIG> illustrates a cable capacity calculator <NUM> for manual calculation of cable capacity.

In a further non-limiting exemplary embodiment of the present disclosure, DCIM solutions are configured to import results data from the equipment management solution to build intelligent workflows for mobile devices that include step-by-step installation instructions with installation validation and product information including but not limited to: product photos, product installation guides, and user manuals. In that regard, <FIG> shows a flowchart <NUM> illustrating an exemplary method for work order creation and/or completion according to one non-limiting exemplary embodiment of the present disclosure.

As described by the flowchart <NUM> shown in <FIG>, a DCIM user begins creating an intelligent work order by virtually moving, adding, or changing server/network equipment, cabling components, network/power connections, or other components to a virtual network cabinet/telecom rack/server enclosure represented in the DCIM solution (<NUM>). The DCIM user specifies cable type, products, and equipment to be used and locations to be installed/removed. The DCIM solution combines move/add/change data manually inputted by the user, products specified for use, and product information downloaded via an API gateway to create an intelligent work order with rack elevation diagrams (<NUM>), where these diagrams are created from product images (e.g., front view of telecom rack elevation) that visually display component locations, sequential step-by-step installation instructions with validation using the software relating to the equipment management solution and a barcode scanner <NUM>, and/or other installation support documents like product photos, product installation guides, or user manuals.

According to the present disclosure, these intelligent workflows can be sent or exported by the DCIM system to the mobile computing device <NUM> running the application software of the equipment management solution for installation guidance in the field (<NUM>).

Intelligent workflows may be stored locally on the mobile computing device <NUM> for use when no network access is available. The application software of the equipment management solution running on the mobile computing device <NUM> can display the rack elevation diagrams of a workflow and an on-site technicians can follow the step-by-step instructions for that workflow (<NUM>). Furthermore, before or after each installation step is performed from the intelligent workflow, the application software of the equipment management solution and the barcode scanner <NUM> may be used to validate equipment location, cable location, and/or proper product has been installed by scanning product manufacturer's unique identifiers on products (<NUM>).

When all steps are completed and validated, updated documentation created by validation steps can be sent back to the DCIM to update the DCIM's virtual network cabinet/telecom rack/server enclosure with correct information (<NUM>).

It should be noted that the personal computer, mobile computing device <NUM>, barcode scanner <NUM>, and/or any other unit, module, controller, system, subsystem, mechanism, device, component, gateway, application, solution, software, algorithm, step, function, operation, or the like described herein may comprise and/or be implemented in or by appropriate circuitry, such as one or more appropriately programmed processors (e.g., one or more microprocessors including central processing units (CPU)) and associated memory or data storage medium, which may include stored operating system software and/or application software including computer or machine readable instructions executable by the processor(s) for controlling operation thereof and for performing the particular algorithms represented by the various functions and/or operations described herein, including interaction and/or communication between and/or cooperation with each other. One or more of such processors or several such processors and/or circuitry and/or hardware may also be distributed among several separate computers, units, modules, controllers, systems, subsystems, mechanisms, devices, components, gateways or the like.

For example, <FIG> shows a block diagram of an exemplary computer architecture for a computing device system <NUM>. For example, the computing device system <NUM> may be representative of the components included in the mobile computing device <NUM> or other computing device disclosed herein for implementing one or more of the features relating to the cable management solution and/or the DCIM solution. Although not specifically illustrated, the computing device system <NUM> may additionally include software, hardware, and/or circuitry for implementing attributed features as described herein.

The computing device system <NUM> includes a processor <NUM>, a main memory <NUM>, a static memory <NUM>, an output device <NUM> (e.g., a display or speaker), an input device <NUM>, and a storage device <NUM>, communicating via a bus <NUM>. The bus <NUM> may represent one or more busses, e.g., USB, PCI, ISA (Industry Standard Architecture), X-Bus, EISA (Extended Industry Standard Architecture), or any other appropriate bus and/or bridge (also called a bus controller).

The processor <NUM> represents a central processing unit of any type of architecture, such as a CISC (Complex Instruction Set Computing), RISC (Reduced Instruction Set Computing), VLIW (Very Long Instruction Word), or a hybrid architecture, although any appropriate processor may be used. The processor <NUM> executes instructions <NUM>, <NUM>, <NUM> stored on one or more of the main memory <NUM>, static memory <NUM>, or storage device <NUM>, respectively. The processor <NUM> may also include portions of the computing device system <NUM> that control the operation of the entire computing device system <NUM>. The processor <NUM> may also represent a controller that organizes data and program storage in memory and transfers data and other information between the various parts of the computing device system <NUM>.

The processor <NUM> is configured to receive input data and/or user commands through input device <NUM> or received from a network <NUM> through a network interface <NUM>. Input device <NUM> may be a keyboard, mouse or other pointing device, trackball, scroll, button, touchpad, touch screen, keypad, microphone, speech recognition device, video recognition device, accelerometer, gyroscope, global positioning system (GPS) transceiver, or any other appropriate mechanism for the user to input data to computing device system <NUM> and control operation of computing device system <NUM>. Input device <NUM> as illustrated in <FIG> may be representative of any number and type of input devices.

The processor <NUM> may also communicate with other computer systems via the network <NUM> to receive control commands or instructions <NUM>, <NUM>, <NUM>, where processor <NUM> may control the storage of such control commands or instructions <NUM>, <NUM>, <NUM> into any one or more of the main memory <NUM> (e.g., random access memory (RAM)), static memory <NUM> (e.g., read only memory (ROM)), or the storage device <NUM>. The processor <NUM> may then read and execute the instructions <NUM>, <NUM>, <NUM> from any one or more of the main memory <NUM>, static memory <NUM>, or storage device <NUM>. The instructions <NUM>, <NUM>, <NUM> may also be stored onto any one or more of the main memory <NUM>, static memory <NUM>, or storage device <NUM> through other sources. The instructions <NUM>, <NUM>, <NUM> may correspond to, for example, instructions for implementing the cable management and/or DCIM solution to track and manage the data center equipment within the system <NUM> illustrated in <FIG>.

Although the computing device system <NUM> is represented in <FIG> as a single processor <NUM> and a single bus <NUM>, the disclosed embodiments apply equally to computing device system that may have multiple processors and to computing device system that may have multiple busses with some or all performing different functions in different ways.

The storage device <NUM> represents one or more mechanisms for storing data. For example, the storage device <NUM> may include a computer readable medium <NUM> such as read-only memory (ROM), RAM, non-volatile storage media, optical storage media, flash memory devices, and/or other machine-readable media. In other embodiments, any appropriate type of storage device may be used. Although only one storage device <NUM> is shown, multiple storage devices and multiple types of storage devices may be present. Further, although the computing device system <NUM> is drawn to contain the storage device <NUM>, it may be distributed across other computer systems that are in communication with the computing device system <NUM>, such as a server in communication with the computing device system <NUM>. For example, when the computing device system <NUM> is representative of the mobile computing device <NUM>, the storage device <NUM> may be distributed across to include a remote database (e.g., database <NUM>).

The storage device <NUM> may include a controller (not shown) and a computer readable medium <NUM> storing instructions <NUM> capable of being executed by the processor <NUM> to carry out the cable management and/or DCIM solution, as described herein. In another embodiment some, or all, the functions are carried out via hardware in lieu of a processor-based system. In some embodiments, the included controller is a web application browser, but in other embodiments the controller may be a database system, a file system, an electronic mail system, a media manager, an image manager, or may include any other functions capable of accessing data items.

The output device <NUM> is configured to present information to the user. For example, the output device <NUM> may be a display such as a liquid crystal display (LCD), a gas or plasma-based flat-panel display, or a traditional cathode-ray tube (CRT) display or other well-known type of display that may, or may not, also include a touch screen capability. Accordingly, the output device <NUM> may function to display a graphical user interface (GUI) such as the GUI for enabling a user to implement the cable management and/or DCIM solution, as described herein. In other embodiments, the output device <NUM> may be a speaker configured to output audible information to the user. In still other embodiments, any combination of output devices may be represented by the output device <NUM>.

Computing device system <NUM> also includes the network interface <NUM> that allows communication with other computers via the network <NUM>, where the network <NUM> may be any suitable network and may support any appropriate protocol suitable for communication to/from computing device system <NUM>. In an embodiment, the network <NUM> may support wireless communications. In another embodiment, the network <NUM> may support hard-wired communications, such as a telephone line or cable. In another embodiment, the network <NUM> may support the Ethernet IEEE (Institute of Electrical and Electronics Engineers) <NUM>. 3x specification. In another embodiment, the network <NUM> may be the Internet (e.g., the internet connection <NUM> illustrated in <FIG>) and may support IP (Internet Protocol). In another embodiment, the network <NUM> may be a local area network (LAN) or a wide area network (WAN). In another embodiment, the network <NUM> may be a hotspot service provider network. In another embodiment, network <NUM> may be an intranet. In another embodiment, the network <NUM> may be a GPRS (General Packet Radio Service) network. In another embodiment, the network <NUM> may be any appropriate cellular data network or cell-based radio network technology. In another embodiment, the network <NUM> may be an IEEE <NUM> wireless network. In another embodiment, the network <NUM> may be representative of an Internet of Things (IoT) network. In still another embodiment, the network <NUM> may be any suitable network or combination of networks. Although one network <NUM> is shown in <FIG>, the network <NUM> may be representative of any number of networks (of the same or different types) that may be utilized.

The network interface <NUM> provides the computing device system <NUM> with connectivity to the network <NUM> through any compatible communications protocol. The network interface <NUM> sends and/or receives data from the network <NUM> via a wireless or wired transceiver <NUM>. The transceiver <NUM> may be a cellular frequency, radio frequency (RF), infrared (IR), Bluetooth, or any of a number of known wireless or wired transmission systems capable of communicating with the network <NUM> or other computer device having some or all of the features of the computing device system <NUM>. The network interface <NUM> as illustrated in <FIG> may be representative of a single network interface card configured to communicate with one or more different data sources. Furthermore, the network interface <NUM> may be representative of AV related communication ports such as high-definition multimedia interface (HDMI), DisplayPort, or mini DisplayPort (MDP), as well as data communication ports such as ethernet, universal serial bus (USB), power over ethernet (POE), or single pair ethernet (SPE).

Claim 1:
A method for management of telecommunication or data center infrastructure, the method comprising:
receiving, at a mobile computing device and from a scanner, a component identifier associated with a component obtained via a scan (<NUM>) of a unique identifier attached to the component;
associating, at the mobile computing device, the component identifier with a location of the component in the infrastructure;
displaying, at the mobile computing device, the component identifier associated with the location of the component; and
exporting (<NUM>), from the mobile computing device, the location of the component to a management solution for use in management of the component in the plurality of components of the infrastructure,
wherein the management solution is configured to download component information from a remote database comprising information associated with the component and wherein management of the component comprises:
automatically generating (<NUM>) a diagrammatic representation of the infrastructure based on the location of the component and the downloaded component information;
automatically generating (<NUM>) an intelligent work order for an infrastructure management action based on the diagrammatic representation of the infrastructure and downloaded instruction information and/or user guides, wherein the intelligent work order includes step-by-step instructions to accomplish the infrastructure management action;
exporting (<NUM>) the intelligent work order to the mobile device;
receiving (<NUM>) from the mobile device a completed work order comprising validated results and updated location information for at least one component; and
automatically generating (<NUM>) an updated diagrammatic representation of the infrastructure based on the updated location information.