You are here: Build > Service Asset and Configuration Management > Service components > Service component workflow
Service component workflow
This section describes the metaphases and subordinate phases in the life cycle of a service component.
The service component workflow relies on business rules. Rules repeat from one phase to another when the end user can make a change to a field affected by a business rule during that phase. For more information about the out-of-the-box business rules defined for the service component workflow, see Service component process - Business rules.
Metaphase: Planning
The service component is in the planning stages.
| Phase | Transition | Description |
|---|---|---|
| Plan | Manual |
This is the starting point for the basic service component workflow. The plan can contain any or all of the following:
Next phase: Build |
Example: a new version (v2.0) of the enterprise email system is available. The organization needs to plan the implementation, decide which features to enable, assess the security impact, and plan the changes to existing protocols.
Metaphase: Construction
When service component plan is final, the component enters into the building and design phase.
| Phase | Transition | Description |
|---|---|---|
| Build | Manual |
The service component is built in this phase. If the built service component matches the design produced in the Plan phase, you can manually transition the service component to the Operate phase, making it available to the end-user community. Alternatively, you can return to the Plan phase to adjust the service component plan. Next phase: Operate or return to Plan |
Example: process and task owners complete their assignments to prepare for rollout of the new version. If the plan missed some details, you can return to the Plan phase to elaborate.
Metaphase: Operation
The service component is operational.
| Phase | Transition | Description |
|---|---|---|
| Operate | Manual |
The service component is operational and available to the end-user community. If there is a replacement service component available, you can manually transition this service component to the Decommission phase. Alternatively, if something in the service component needs to be changed, you can manually transition it back to the Build phase. Next phase:Decommission or return to Build |
| Decommission | Manual |
The service component is still active but ready to be retired or replaced. Alternatively, you can manually transition the service component back to the Operate phase. Next phase: Retired or return to Operate |
Example: the internal user community accepts the rollout of the new version. Problems are prioritized and resolved by the email service support team. When the next version (v3.0) is available, the organization migrates to that version and you want to decommission the current version (v2.0) from service.
Metaphase: Final (End)
The service component reaches retirement.
| Phase | Transition | Description |
|---|---|---|
| Retired | Manual |
The service component is no longer available. Next phase: None, or return to Plan to start the process again, or return to Decommission while waiting for a replacement |
Example: the v2 version of the email system is obsolete.
