Multiple ''installation addresses''

[Joshua Chen FX]

Hello,

Use case: Customer can order x routers as part of Managed service offering and require installation at different locations.

• Using OMT only, how can we meet this requirement? 

It looks like location is at the order line level → do we have to create 1 customer order for each unique location?

In the PDI demo data, you have PS SDWAN Edge Devuice + PS SDWAN Controller + PS SDWAN Security → these are all under parent PS SD WAN Service Package → this scenario works when it only has 1 location.

• What if I have 20 devices, that are installed at 20 locations??
  → would you create a separate PS for the MS offering, and another separate PS for the router?
  → submit 1 customer order for the PS MS Offering (PO), and X orders of PS Router (POn+1), one for each unique location?
  
  thoughts?

[ShashankInamdar · Accepted solution]

Hi @Joshua Chen FX ,

There are multiple ways to approach this based on your requirements.

[1] In the Catalog model, you can perhaps have the following structure -

PO = 'Managed Service Offering'.

        Parent PS = 'Managed Service'

                  Child PS = 'Router' (0..n)

This assumes the 'Router' is an orderable entity and not a Resource.

In this case, at the time of order submission you can have as many Order Line Items for the 'Router' PS each with it's location.

[2] An alternative to this is to have a separate PO = 'Router Offering' with 'Router' PS under it. And apply the same principle at order submission. You just need one order with 'n' OLI's, not 'n' Orders.

[3] Also another option is to model the Router location/site as a characteristic on the Router itself. This depends on the significance of the location in the fulfilment and install base context.

Thoughts?

[Joshua Chen FX]

Hello @ShashankInamdar 
*sorry, i meant to say order lines

Your option [2] is exactly what we had in mind.  We tried [1] prior, and it didn't really work.

Could you elaborate on [3], regarding  ''This depends on the significance of the location in the fulfilment and install base context.'' Not sure I understand.

joshua

Thank you,

[ShashankInamdar]

Your option [2] is exactly what we had in mind.  We tried [1] prior, and it didn't really work.

---

I am curious to know why [1] did not work. The principle is same as option [2].

---

Could you elaborate on [3], regarding  ''This depends on the significance of the location in the fulfilment and install base context.'' Not sure I understand.

---

I meant is there a reason you want to model the Router Installation Address as a cmn_location and use it as a RelatedPlace in the Order against that OLI. Why not model it as a characteristic on the Router Spec?

Also is the purpose (significance) of the location just to indicate where to install the router, or is the Address to be treated as a CI that may have an operational status? If latter, you might want to consider modelling the Router as a Resource in the CMDB linked to a Network Site (the Address).

[Joshua Chen FX]

I created a PO using PS Parent (bundles) of PS child_1 & PS child_2

• I was not able to have multiple order lines for PS_child_2 for a same customer order. I could only change the quantity for the single order line (one location).

Also is the purpose (significance) of the location just to indicate where to install the router, or is the Address to be treated as a CI that may have an operational status? If latter, you might want to consider modelling the Router as a Resource in the CMDB linked to a Network Site (the Address).

---

A mix of both. A client (Bank) would submit a customer order to install routers at different locations (branches). We just want to know where it is installed, and the address should be populated on the location field when we create the CI for the router. I don't think the Network Site CI makes sense here, but maybe im wrong.