OOB solution for inventory flow when a CI configuration task is required

[stephane9]

As part of inventory workflow, some hardware assets will need to be configured before they are shipped.  ‘Some’ being the KEY word as not all hardware inventory assets have to be configured before they are shipped.  If a hardware inventory asset is configured before it is shipped, depending on the classification of the asset, it may be a different group that does the actual configuration; for example, if it is a Starlink satellite dish, it will be configured by Stockroom however if it is a router, it will be configured by IP Assignment Group.   Our business requirement is to have the ability to create a “Configure task” if required as part of our inventory workflow and if required, assign it to the correct group prior to shipping the device.  The group that is doing the configuration may not be the group that does incident management, change management or data management (i.e., the groups on CI Class).

As this is specific to hardware models ( like some types of routers), we were looking at three main solutions:

1. Extend the hardware model class to add a custom field to track the configure group
2. Create a lookup table to match the hardware class with a configure group
3. Use one of the existing group fields on the CI Class  (approval, change, managed by, support)

There are pros and cons for each of those solution and we’re thinking of using option 2 as has the least risk.

Our main question is that we’re likely not the only organization that requires to have CI configured before being shipped but we don’t see anything OOB that address this needs.

Is there a CSDM aligned solution or OOB solution to address this requirement?  

[Punit S]

Hi Stephane,

While there is no out-of-the-box (OOB) solution in ServiceNow that specifically addresses the requirement of configuring hardware assets before they are shipped, there are several options you can consider. Here are a few:

Create a custom field on the hardware model table to track the configure group: This option would involve extending the hardware model class to add a custom field to track the configure group. This would allow you to easily assign a configure task to the appropriate group based on the hardware model. However, this may require additional development effort and maintenance.

Create a lookup table to match the hardware class with a configure group: This option would involve creating a lookup table that matches the hardware class with a configure group. This would allow you to easily assign a configure task to the appropriate group based on the hardware class. This option may be easier to maintain than option 1.

Use an existing group field on the CI Class: Another option would be to use an existing group field on the CI Class (such as approval, change, managed by, or support) to track the configure group. This would allow you to leverage an existing field and may be easier to maintain. However, you may need to modify the existing field to meet your specific needs.

In terms of a CSDM-aligned solution, you could consider adding a new relationship type to the CSDM data model to track the relationship between the hardware asset and the configure group. This would allow you to easily track and report on the configure task and the group responsible for configuring the asset.

Ultimately, the best solution will depend on your specific requirements and the level of effort you are willing to invest in development and maintenance.

Hope you find this information useful.

Thanks,

Punit

[SusanWinKY]

Hi @stephane9 - we don't have this same situation but we have been asked to create a CI class for Starlink devices. Do you mind letting me know which CI class you put yours into? 

[Fevzi Yerlikaya]

Option 2 sounds like the best choice; a lookup table simplifies tracking and reduces confusion. I've seen it work well in similar setups. As for OOB solutions, they’re usually not a perfect fit for unique workflows, but it’s worth checking with your vendor for any recommendations that align with CSDM.