Physical Server Request

[mikecline83]

Hello,

I've been tasked with creating a catalog item/Service Request for ordering a new physical server (we are also working on VM Ware automation separately). Have any of you done this in your environments? How did you end up designing it? I've seen suggestions to use a Wizard, but we haven't used that before. Just looking for ideas before I start creating it and then find that there was a better way to do it.

Thanks in advance for any input,

--Mike

[Cary5 · Accepted solution]

It has been some time ago now (4 years or so) but I had built something similar for two different clients.

1) A test bed server request that would build a server used for a specific project. I used an order guide that ordered the individual components as requested items that all fell under the parent request. This might be the most common approach, sticking to out-of-box.

2) A similar request was needed to order various packages or bundles of servers. Each server might have a service package (silver/gold/platinum) that was attached to it. The total order needed to be split among various departments (charge codes). The catalog was modified to allow these requested items to be packaged into "bundles" that were grouped together on the order summary page (i.e. you could order 3 different servers, each had their own bundle, and all components were individual requested items, all under 1 parent request).

As far as a wizard is concerned, I don't see those used often and believe they're more of a legacy feature. I wouldn't recommend that approach. I don't focus on service catalog as much as I used to but would suggest looking into an order guide and bundling these components together (especially if there is the possibility of the individual components being ordered separately).

[mikecline83]

After a bit more research, I believe that an Order Guide is the way to go. Thanks for the reply