Operational Statuses for Services descriptions

[Joey9]

Hi,

Could someone please direct me to a description (a one or two liner) for each of the operational statuses associated to services. Some of them seem reasonably self-explanatory (Operational, Retired) but others are less so (Pipeline, Catalog). In addition, I'm looking for information as to when you'd use the one over the other. For example, Repair In Progress vs Non-Operational.

Thanks

[Community Alums · Accepted solution]

Hi @Joey ,

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.

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[Juan Cruz]

Hi! I want to know from where did you take this info?

It was so usefull for me! Thanks a lot

Juan

[Joey9]

Hi Sandeep, thank you very much for the answer. I think this has helped steer me where i need to go. Thanks again for you valuable input.

[Community Alums]

Awesome 🙂