Planning a service version
This lesson shows you how to use the governance enablement profile to plan a service version.
What you should be able to do
- Propose the service version plan.
- Approve the service version plan.
Roles participating in this task
![]() |
The user in the Development role proposes the service version plan. |
![]() |
The user in the Business role approves the service version plan. |
Introduction
The scoped version, created in the lesson Scoping a service version, is now in the planning phase where the development and owning organizations must work together to define the funding and timeframes for the project. In this phase, architecture sizing and funding decisions are made, including establishing dependencies on other assets or services. As part of this wider process, the decision is made to reuse the Eligibility service (from the Governing an existing service lesson). If you are integrating with Rational Asset Manager (see Integration with Rational Asset Manager), you might want to create a document of understanding (DoU) at this point, to define the details of the service reuse.
Part 1: Proposing the service version plan

The service version must be updated to include proposed availability and termination dates. The plan is then proposed; this makes the plan available for review.
The various lines of business involved in the provision and consumption of the service now have the opportunity to review the details of the service version implementation.
Part 2: Approving the service version plan

After all parties have agreed the details in the plan, the service version plan is approved.
What you did in this lesson
- Proposed the service version plan.
- Approved the service version plan.