The business question Which contracts should we review? shows the period of validity of the contracts and the lifecycles of the applications and components that are specified as the contract deliverables.
Review contracts with impending end dates in order to make informed decisions about architectural changes based on your contracts with IT suppliers or service providers. Understand which contracts are associated with a particular vendor and ensure that license usage is in line with the contact deliverables. This business question helps you to manage and align your contract library, minimize planning risk, and avoid unnecessary costs.
The license package Contract Management is required to work with this business question. The use case Contract Alignment must be activated.
Navigate to Which contracts should we review?
Use the method that is most convenient for you:
- In the left navigation panel, enter Which contracts should we review? in the Search Navigation field.
- In the left navigation panel, click Home. In the content area, go to the Business Questions page and click the tile for Which contracts should we review?
- In the left navigation panel, expand the sections Business Questions and Transparency and click Which contracts should we review?
What information is displayed in Which contracts should we review?
The Gantt chart Contracts and Contract Deliverables shows the lifecycles of applications, components, business services, and support services and their associated contracts. You can expand and collapse the rows in the first column.
- The first level shows either
applications, 
components, 
, business services, and 
support services, their object state, and highlights conflicts due to the impending end of a contract's period of validity. The timeline shows a colored bar with lifecycle statuses and a red bar visualizes the active period (start date - end date) of the application or component. - The second level shows the
contract. The colored bar shows the period of validity (start date - end date) of the contract. A light blue rectangle on the timeline highlights the contract's review date. - The third level shows the
contract deliverable with the number of used or planned licenses for the application or component. The colored bar shows the time period that the licenses are valid. A red rectangle on the bar will highlight an overuse if more licenses are allocated for the contract deliverable than are permissible. - The blue vertical line indicates the current date.
- A grey vertical line connects the predecessor contract with the successor contract. Point to the grey line to view a tooltip showing the predecessor contract, successor contract, and end date of the predecessor contract.
How can I edit the contracts in Which contracts should we review?
If you have the relevant access permissions, you can edit the contracts in this business question.
- Click the
edit button > Edit Contracts to open the Contracts data workbench. Use the features of the data workbench to slice-and-dice your data to focus on data and do the analyses you are interested in. - Edit the following:
- Release Status: Describes the governance status of the contract over its lifecycle and thus indicates how well users can trust the information.
- Start Date and End Date: The start and end date captures the contract's period of validity.
- Cost: The total cost of the contract deliverable.
- Monthly Cost: The monthly cost of the contract deliverable.
- Review Date: Each contract should have a date defined for when the contract should be reviewed.
- Click the
navigate button to open the content area of a contract and go to the Architecture Context to review the specification of the contract deliverables and make changes if necessary.
What data is required for Which contracts should we review?
Business question: Which contracts should we review?
Purpose: Understand the validity of contracts and the lifecycles of the applications and components that are specified as the contract deliverables.
DATA REQUIREMENTS
Capture the data necessary for the business question. Contracts , applications , and components must be in the repository and well documented. Try to capture as much information as possible about the contracts, applications, and components because complete data considerably improves the results of the business question and your ability to focus on the data that is most important to you.
- Document the contract's attributes including the End Date, Review Date, Vendor/Provider Organization, and Buyer attributes.
- Document the applications and components that are the contract deliverables.
Improve the data and correct data quality issues. Go to the business question's Data Quality > Data Completeness. This visualization helps you to assess whether sufficient data is available to produce meaningful and reliable results for the business question.
- Go to Pending Issues to resolve data quality issues and improve the data that the business question is based on. Only the first 5000 issues are displayed.
- Go to the Data Source page to understand the underlying data relevant to the business question. The data source is a list report and cannot be edited.