RITM Parent Child Relationships

[mullikinjam]

This post isn't as much of a technical question, more of a process related one.

Our organization has complex business processes where there are multiple service providers required to deliver workstations as an example. 

Historically, we have assigned RITM ownership to the service provider who owns the service/catalog item, but have used SCTASKs to task all of the secondary service providers necessary to deliver said workstation. i.e., network provider, facilities etc. However,  this approach has become less ideal because the organization doesn't wish to  do service provider metrics at the SCTASK level, instead wanting to do them at the RITM level. 

As a result, at a very high level, our proposed solution is to auto generate children RITMs, vice tasks, and assign them to the appropriate service providers for work and ensure that the RITMs are related under the originally requested RITMs REQ. 

Example:

1. User submits RITM 1 for a workstation
2. RITM 1 auto generates RITM 2 (network) and RITM 3 (facilities)
3. RITM 2 and 3 are placed in a "Not yet requested" state, pending RITM 1s approval. 
4. Once approval is obtained, RITM 1, 2 and 3 follow their pre-defined workflows to completion

Of course I've glossed over a lot of important details regarding the relationships of the RITMs and their work order, but does anyone have experience doing something like this? If so, what are some lessons learned in going with this approach?

[Brian Lancaster]

I'm thinking using an Order Guide would be the better way to go.