Why Peripherals are under Configuration items?

[Suggy]

ServiceNow has clearly defined what goes as a CI vs Asset.

Then why on earth, the Peripherals [cmdb_ci_peripheral] are created by extending Configuration Item [cmdb_ci] class?

According to me, Peripherals are should be tracked as Assets (higher financial value) or less expensive ones should be considered under Consumables. It should not be created under Configuration Item.

The moment you talk about CI, things like change governance, operational attributes etc would come into picture.

[Suggy]

Agree for Incident, but not problem and change management especially talking about other peripherals like keyboard, mouse etc.

Anyways, after reading a lot on this topic, I just understood that it boils down to HOW an organization wants to track something. Anything can be tracked as CI vs Asset (peripheral, consumables etc)

🙂

[Dr Atul G- LNG]

Just to add @Suggy 

I worked for a client where we had problem on printers and we deployed changes in printer as well ( It was insurance client and their more work on printer)

[Sandeep Rajput]

@Suggy It relates to problem and change too. Let's say an incident is raised for a printer not printing. A problem was created to find the root cause as to why the printer was not printing. The root cause identified as an obsolete firmware on the printer. A change was created to update the firmware on the printer.

This scenario connects the entire cycle of incident, problem and change.

Regarding other peripherals they can also be treated as a CI if the organisation want them too. This will allow them to create incident at a granular level. 

[Dr Atul G- LNG]

printer, Scanner still can be used, but keyboards are not.

[Suggy]

@Sandeep Rajput @Dr Atul G- LNG Thanks for your valuable inputs 🙂