Status Concept/State Model for Business Services and Service Offerings

Steven Torok
Mega Contributor

Hello everyone!

do Business Services and Service Offerings have a default/OOB State Model which is configured?

Just to be sure my questions is clear:  a business service might have the following lifecycle:  Planned, In Progress, Active, Retired

  -  What basic concept is OOB?

   - How can such a basic concept be adapted for specific needs?

Many thanks in advance for your support.

Regards,

Steve

 

1 ACCEPTED SOLUTION

David Thigpen
ServiceNow Employee
ServiceNow Employee

Hi Steve - great question.

There is a defined phase and status model on the service and offering records. The two fields are used together to describe where the service is in its lifecycle. Status is dependent on parent phase.

Phases are 

Pipeline - where new service/offerings are being considered and approved

Catalog - where services/offerings are being designed, developed, and deployed

Retired - services that are now longer being provided

Within each phase are statuses:

  • Phase: Pipeline
    • Status: Requirements, definition, analysis, approved, chartered
  • Phase: Catalog: 
    • Status: Design, development, build/test/release, operational, retiring
  • Phase Retired:
    • Status: Retired, obsolete

Only services that are Catalog-Operational and assigned to a portfolio are visible in the Service Owner Workspace. 

Other considerations:

  • A service must have its parent node within a portfolio defined before it can be placed in the Catalog phase.
  • A service must also have at least one defined offering to be placed in the Catalog phase. The offering does not have to be in an operational state.

Thank you,

David

View solution in original post

12 REPLIES 12

David Thigpen
ServiceNow Employee
ServiceNow Employee

Hi Steve - great question.

There is a defined phase and status model on the service and offering records. The two fields are used together to describe where the service is in its lifecycle. Status is dependent on parent phase.

Phases are 

Pipeline - where new service/offerings are being considered and approved

Catalog - where services/offerings are being designed, developed, and deployed

Retired - services that are now longer being provided

Within each phase are statuses:

  • Phase: Pipeline
    • Status: Requirements, definition, analysis, approved, chartered
  • Phase: Catalog: 
    • Status: Design, development, build/test/release, operational, retiring
  • Phase Retired:
    • Status: Retired, obsolete

Only services that are Catalog-Operational and assigned to a portfolio are visible in the Service Owner Workspace. 

Other considerations:

  • A service must have its parent node within a portfolio defined before it can be placed in the Catalog phase.
  • A service must also have at least one defined offering to be placed in the Catalog phase. The offering does not have to be in an operational state.

Thank you,

David

Hello David!

thanks a ton again (you help me about a month ago on a "related topic")!  Your answer is very clear.

As a followup:  Can you also briefly explain the OOB status model of Catalog Items?

Cheers,

Steve

 

 

 

Hi Steve - 

That's a little outside my area.  Maybe ask that question over in the Request topic so that the answer stays in that body of knowledge.

Link

David

Great answer David, Offerings and services with Retiring status (service_status) are also visible in Service Owner Workspace.

Only services that are Catalog-Operational/Retiring and assigned to a portfolio are visible in the Service Owner Workspace.