cmdb_ci_circuit

[salvadormarchan]

All,

Anyone has used this table? What is this table for? Typically,which industry would use it more often?

Any examples is greatly appreciated.

Thanks,

Dor

[robpickering]

Salvador, out-of-box this table is for listing Power Circuits.   This table is extended from cmdb_ci (base) and you'll note there are four fields unique to this class (Type, Max amps, Phase, and Voltage).

The Dictionary Choices look like:

Type:   AC or DC

Voltage:   100V, 120V, 208V, etc.

Max amps:   12A, 16A, 20A, etc.

Phase:   Single-phase, Two-phase, Three-phase

There are several discussions in the community about using this table for network/voice/data circuits, but it would require some custom fields, including something that would trigger the actual type of the circuit (network, voice, data, power).   This is something I'm pursuing in my instance.

[Amy Lind1]

Hi Robert!

I can't seem to find any other discussions on the community pertaining to network/voice/data circuits. We are needing to go down this same road.   Are you still pursuing this in your instance?   I'm interested in hearing your approach.

Many thanks!   Amy

[robpickering]

Amy, yep we implemented it in our instance, it works really well.

It's really nice to be able to pull up a Router CI and see all of the circuits attached to it.   It also then allows you to click on the circuit ID and retrieve the vendor information to submit a trouble ticket.

Happy to talk it more real-time, feel free to drop me a INBOX message here and I'll post some contact details for you.

-Rob

[robpickering]

All, it's been a while since I posted this and I wanted to explain what we ended up doing:

We modified the cmdb_ci_circuit table with the following updates:

Added Fields:

Bandwidth (u_bandwidth), type Integer, 40

Billing Number (u_billing_number), type Phone Number (E164), 40

Sub-type (u_subtype), type String, 40

Type (u_type), type Integer, 40 (default 1) ** note, there is a default "type" field that we removed from the Form View in favor of our custom one, as I did not want to change the choice list for the OOB field).

These had the following choice lists attached:

Bandwidth: 1.5 Mbps (0), 3.0 Mbps (1), 10 Mbps (2), 45 Mbps (3), 100 Mbps (4), 1 Gbps (5), 10 Gbps (6)

Type:   Power (Value 0), Data (Value 1), Network (Value 2), Voice (Value 3) (See Sub-type to understand each usage).

Sub-type (Depended on Type):   AC (0), DC (0),

                                                                                                  DSL (1), Cable (1), VPLS / LAN (1), MPLS (1), Point-to-Point (1),

                                                                                                  Fiber (2), Coaxial (2), Ethernet (2),

                                                                                                  POTS (3), T3 (3) T1 (3), PRI (3), BRI (3), Centrex (3)

Those were the only changes we made to the table, we then added these fields to the default Form View and it's been working well.   You could obviously add more choices based on your needs.

Also, this is not endorsed by SerivceNow just because I'm now working here, this was done during my time at AAA Allied Group.   It may now make more sense to create your own extended table from cmdb_ci_circuit to house telecommunications circuits, but there are pros and cons to that approach.   We weren't planning on using cmdb_ci_circuits to ever house power circuits, but we had a real need to have our data circuits tracked, the above modifications seemed harmless and got us up and running quickly.

-Rob